Implementation of AWS Lambda in Business Arena

Diksha Mishra
CS & IT
BBAU Satellite Campus,
Amethi.
mdiksha40@gmail.com

Abstract—
II. THE MODELS OF CLOUD COMPUTING
In the emergence of traditional microservices for There are three major components of cloud computing.
browsing over the internet, cloud computing is a major Those three models are PAAS-(Platform as a Service),
acquiring service nowadays, as it provides function-as-a- SAAS-(Software as a Service) and IAAS-(Infrastructure as
service. For the new business implementations where web
a Service).
applications are required to run the business, the planning of
required infrastructure as well as their maintenances and
management is a hectic concern to the businessmen. Instead
of using traditional microservices, cloud computing services
provided by cloud vendors are the major relieve for their
concerns.AWS in a major cloud vendor that provides over
165 web services including AWs lambda, AWS API gateway
which are required services to build the infrastructure
regarding web services for the business implementations.
Serverless is a cost-effective with pay-as-go pricing technique
as well as the security and compliances of the related to web
services are fully managed by cloud vendors.

In this paper, we will discuss the evolution of web

services, advantages of cloud computing over the traditional
services and the level of usage of cloud computing over in
comparison to traditional services, AWS services and
architectures regarding business aspects for the new
startups.

Keywords—Cloud computing, AWS, Serverless, AWS

Lambda.

I. INTRODUCTION Figure 1. Components of cloud computing.

Amazon has launched its AWS- Amazon Web Services
in 2006 since Amazon has become a major cloud vendor in
the arena of cloud computing web services. Back in time,
when timesharing systems are used for scientific purposes
or for the organizations, which provides a common
resource pool, it proposes a paradigm of computing
systems which is known as cloud computing nowadays.
With this computing technique inflation in assembling of
data capacity and computing resources or power is
available to share among many users, to the general public
as function-as-a-service. Cloud computing introduces a
new trending word ‘Serverless’. Serverless refers to the
function-as-a-service platform which promises end-users
to reduced hosting cost, high availability of resources,
dynamic elasticity, fault tolerance. Comparatively, owing
to their own hardware infrastructures, client or
organization uses the services on the rent basis provided by
the cloud vendor. Almost all those services where the
client doesn’t need to be present physically to the
computing hardware can be easily conveyed by the
vendors.
SAAS offers the most elevated level of scaling. At last,
IaaS offers access to processing assets, as a rule by renting.
Virtual Machines (VMs) and extra room. The Serverless
figuring, which was evaluated in this paper can be
remembered for PaaS as in both of these models there is no
server the executives and engineers should just think about
composing the code.
III. SERVERLESS COMPUTING
Serverless registering is a distributed computing model
where the cloud supplier progressively deals with the
portion and provisioning of the servers. At the end of the
day, applications are facilitated by third-get-together
assistance, which causes a designer not to be locked in
with equipment and programming the board. The term
itself can make a bogus impression that there are no
administrations off-camera, in any case, the servers are
not disposed of, they have simply avoided the purchasers.

1
 In Figure 2, you can see the case of Serverless engineering
with the Amazon Web Services supplier.
In Figure 2, a client calls a post demand with a JSON
body and the parameters ought to be placed into a
DynamoDB table. The API is given by means of the API
Gateway administration and the asset should trigger a
Lambda work. The Lambda work gets the parameters and
put them into the database. The majority of the PaaS, or
Platform as a Service, items offer similar focal points,
where the engineers likewise don't have to stress over the
backend servers yet at the same time, there exists the
critical contrast between these two advancements. The
essential distinction is standing out how to form and
convey the application to the cloud.
Figure 2. AWS Serverless Architecture.
Interestingly, in a conventional 'server' design, the
engineers should conjecture, how a lot of limits is required
for his application and buy it, regardless of whether they
wind up utilizing it or not.
At long last, the client has an advantage of snappy
organization and updates. As there is no need for backend
design from the designer's side, it is conceivable to rapidly
transfer the code and discharge another item. Likewise, as
the application is isolated into little capacities, it isn't
important to make changes to the entire application; rather
can refresh each capacity in turn.
IV. TRADITIONAL ARCHITECHURE VS SERVERLESS
COMPUTING
Netizens make some assumptions like serverless
computing means no servers are there used during the
computing. These assumptions are erroneous. To
demonstrate this, below give example is showed, which
shows the discrepancy between traditional service
architecture with n-tier server logic and the architecture of
serverless computing.
Figure3. A traditional architecture where the server and
database are managed by the developers.
Here, the traditional architecture, we have spoken yet is
refers to the client-server architecture. The client-server
2
model makes the communication between the client and
the user by exchanging the protocols between server and
database. This traditional architecture is comprised of two
components, where the client makes always request and
the server responds according to the request is make. But
there are some issues related to this architecture like the
required network setup is difficult to manage also it
requires a lot of servers. Also, to maintain up these servers
to deliver efficient services, it becomes quite expensive in
terms of capital.
In serverless architecture, as shown in figure 2, some
changes are done including server and database; new
components are added like API Gateway, Lambda
functions. Instead of having one server for each type of
functionalities, our FAAS has now each piece of
functionality for each type of function. For example, if we
could have a function for searching for a product, then
there does also exist a function for buying that product.
In the cloud arena, the application is used to run in
stateless compute, which is brought up and bring down
according to the trigger. Triggers are simply coded events,
the service according to the HTTP request that is requested
by the client. AWS Lambda is also a trigger that is created
within the function console, command-line interface and
within the same cloud provider’s environment. There are
three types of triggers majorly exist in the cloud computing
arena:
 HTTP Trigger: It gives the function call
according to the content with the rich features. On
the contrary, a file, text, JSON, PUT, POST and
DELETE HTTP methods.
 Database Trigger: It performs all those functions
which are used to alter the existing database like
insertion, deletion, updating and modification
queries of records in the table.
 Storage Object Trigger: it is used for tracking
objects that exist in cloud storage like database
and some metadata about the events calls and
objects.
In AWS, a trigger function can be an HTTP request or
it can also be a request for another service. The AWS
cloud provides so many different types of serverless
computing. These include capacities are [1]:
 Compute - AWS Lambda
 APIs -Amazon API Gateway
 Storage - Amazon Simple Storage Service(S3)
 Databases- Amazon DynamoDB
 Interprocess messaging- Amazon Simple
Notification Service (Amazon SNS) and
Amazon Simple Queue Service (Amazon
SQS).
 Orchestration: AWS Step Functions and AWS
Cloud Watch Events.
V. AWS LAMBDA
Amazon Lambda was launched by Amazon Web services
in 2014 and it was the first serverless computing platform.
AWS lambda defines a few key aspects like cost,
programming model, deploy, security and monitoring.
That supports many languages, for example, Node.Js,
Python, Java, GoLang, .Net[2]. AWS lambda assists the
progress of the functions which get automatically scaled
up or unable parallel computation and also those
functional applications can easily be deployed. AWS
Lambda provides the logic layer for the architecture.
VII. REFERENCES
When the scaling of function calls like event-driven
function increased simultaneously too many requests are
demanded, lambda creates multiple containers by creating
too many copies of existing functions to respond to each
request and run them parallel. That is why any
possibilities are minimal for the idle stage of the container
or the server. Deployment applications that use this
architecture which includes lambda functions can be cost-
effective and also they get designed in a way to reduce the
wasting capacity of the resources and capacities.
AWS Lambda is a type of FAAS service. FAAS
approaches to the event-driven computing system.
Figure 4: Relationship among event-driven, FaaS and
Serverless FaaS.
Serverless FaaS relies on a function where the unit of
deployment and execution [1]. Serverless FAAS is a type
of FaaS where no virtual machines and Dockers or
containers are present in the programming model [1]. We
can run any type of backend service or application’s code
virtually in the Lambda environment and also they can run
this code with the high inflation of scalability and
capacity. Users don’t have to write extra code to integrate
their event source functions and also no management to
match the scalability of the requests for a response. Users
can focus on their logic layer, not on the infrastructure
that is required for the deployment of the application.
VI. FUTURE SCOPE WITH AWS LAMBDA
By using AWS services for business start-ups as well as
running businesses, it relies the customer or owner to let
them only focus on their business growth strategy besides
focusing on technical infrastructures for maintaining the
servers, capital cost as perusing or pay-as-you-go and
also it provides high scalabilities to integrate or the
sudden inflations for multiple requests simultaneously
responses. Also, AWS provides 9.9999% of data recovery
and disaster recovery guarantee to the users in any case.
Also, Amazon services are working on deploying services
that work with AWS Lambda for fields like Artificial
Intelligence and the Internet of Things.
[1] Serverless Architectures with AWS Lambda-
whitepapers by AWS.
[2] Yan M., Castro P., Cheng P., Ishakian V., Building a Chatbot
with
Serverless Computing. In Proceedings of the 1st International
ACM Workshop on Mashups of Things and APIs, Trento, Italy,
Dec 2016, 5 p.
[3] Hendrickson S., Sturdevant S., Harter T., Venkataramani V.,
Arpaci-Dusseau A.C., Arpaci-Dusseau R.H., Serverless
computation with open lambda. In Proceedings of the 8th
USENIX
Conference on Hot Topics in Cloud Computing (Hot Cloud '16),
Denver, CO, June 2016, 7p.
[4] Baldini I., Castro P., Chang K., Cheng P., Fink S., Ishakian
V.,
Mitchell N., Muthusamy V., Rabbah R., Slominski A., Suter P.,
Serverless Computing: Current Trends and Open Problems.,
arXiv preprint arXiv:1706.03178. June 2017, 20 p.
[5] Sill A. The design and architecture of microservices. IEEE
Cloud
Computing. 2016 Sep;3(5):76-80.
[6] H. Liu, A Measurement Study of Server Utilization in Public
Clouds, Proc. 9th IEEE International Conference on Cloud and
Green Computing (CAG’11), Sydney, Australia, Dec 2011,
pp.435-442.
[7] M. Rehman, M. Sakr, Initial Findings for Provisioning
Variation
in Cloud Computing, Proc. of the IEEE 2nd Intl. Conf. on Cloud
Computing Technology and Science (CloudCom '10),
Indianapolis, IN, USA, Nov 30 - Dec 3, 2010, pp. 473-479.
[8] R. Buyya, “Cloud computing: The next revolution in
information technology,”
in Parallel Distributed and Grid Computing (PDGC), 2010 1st
International Conference on, pp. 2–3, Oct 2010.
[9] J. Lewis and M. Fowler, “Microservices,” 2014.
[10] A. W. Services, “Aws lambda,” 2015.
[11] GIGAOM, “The biggest thing amazon got right: The
platform,” 2011.
[12]Nginx, “Adopting microservices at Netflix: Lessons for
architectural
design,” 2015.
[13] InfoQ, “From a monolith to microservices + rest: the
evolution of
Linkedin's service architecture,” 2015.