AWS
Lambda and
Serverless
Computing
Introduction
Basic Concepts
Advanced Concepts
We need to The best approach to build Serverless
understand Serverless applications is to use frameworks like AWS
Workflow patterns SAM and Serverless Frameworks
using Step Functions
We need to understand how to automate and streamline our Serverless delivery
and deployment with CI/CD Tools like CodeCommit, CodeBuild and CodePipeline
Many end-to-end
full stack
applications can
be built using
Serverless
Architectural
Patterns
• Computing technology has evolved
phenomenally
• Data storage has become very
affordable
• Computing has increased with
widespread speed
• Currently applications are built to
leverage these advancements in the
Computing Technology
• Cloud Computing has made it possible to
build cutting-edge applications at a
fraction of cost not just for big
companies but also for individual use
Public cloud providers like Amazon AWS, Microsoft
Azure, Google Cloud Platform have removed the
entry barriers and made computing very easy and
affordable for common people
The modern-day applications demand high level of
power... high level of compute powers well as speed
For example, if the Facebook app doesn’t show us
what we need to see as soon as we open the
Facebook app, most of us might simply close the app
and move on
So, the application has to be fast and responsive and
Serverless Computing is this
new trend in cloud computing
which attempts to solve many of
these challenges.
Serverless computing will help
us build the next generation of
systems that can handle
demanding workloads and scale
indefinitely without having to
provision or manage any servers
Now, if we look at the traditional architecture,
there are several activities and tasks that we
must perform in order to run any particular
application
First, we got to create and setup servers, install
operating systems, install and setup databases,
manage software patches and hardware updates,
manage capacity and scaling, Manage High-
availability through load-balancing and so on
And of course, this server infrastructure and the
computing power has its own costs, which are
often substantial
On the other hand, with Serverless Architecture, all
these mundane tasks of managing the underlying
infrastructure are abstracted away from us So in a
way when we use serverless architecture, we won’t
really feel like you are using any high-end servers,
because we’re not the one who is actually taking
care of it That’s the reason this approach is called as
Serverless
That means, Serverless Computing still uses servers, but
we no longer have to worry about managing them or
worry about the uptime or availability or anything that has
to do with the infrastructure part
With Serverless, we kind of get to be
more productive
We can completely focus on writing
our code without having to worry
about the underlying support system
So we simply upload our code to the
cloud provider and it can be run on-
demand as and when needed
With Serverless, we write our code in the
form of functions, just like we would write
a function in any programming language
And these functions then run in the cloud
So, we segregate our application logic in to
small independent functions or
microservices and upload them to the
cloud provider
These functions are stateless and can be invoked in
response to different events
These events could be file uploads, database
updates, in-app activity, API calls, website clicks, or
sensor outputs just like those from IoT devices and
so on And all this can be accomplished without
having to manage any infrastructure or having to
size, provision or scale a bunch of servers, and
without having to worry about performance
and availability
This seriously allows us to laser focus on our
application code and not get caught up in multitude
of infrastructure issues
AWS Serverless Platform
The two key pieces of the AWS Serverless platform are:-
AWS Lambda
Facilitates to run our CODE without thinking about SERVERS
With Lambda, code for virtually any type of application or backend
service can be run, all with zero administration
API Gateway
Facilitates to create and manage APIs to back-end systems running
on Amazon EC2, AWS Lambda, or any publicly addressable web
service
Amazon API Gateway, can generate custom client SDKs for APIs, to
connect back-end systems to mobile, web, and server
applications or services
First Serverless API
Sign in to the AWS Console at https://aws.amazon.com/console
First Serverless API
First Serverless API
This landing page
after Sign-in is the
AWS Dashboard
First Serverless API
Search for the Service API Gateway in the Service Search Bar Simply typing API in the
search box will navigate us to API Gateway
First Serverless API
If there exists NO previously created APIs before, in the Signed-in account, then the screen we
are most likely to see is as below ( at least as shown in the VIDEO )
First Serverless API
AWS does change its GUI often, so we might see a different UI, but more or less, it should
provide us the similar functionality
Creating HTTP API in the API Gateway
Section
In the Landing Page of Amazon API
Gateway we should get the option
to choose an API Type
(HTTP/REST/WebSocket) but if we
do not see this screen then we can
click on the APIs keyword in the
Left- Hand-Side pane to reach this
page
First Serverless API
We are attempting to create an
HTTP API and so accordingly we
The first need to click on the Orange Tab
specification to be
given here is what Build so that we get to Launch the
do we intend to First part of the Wizard for
INTEGRATE the API
with : An End-point, Creating an API
A Lambda Function,
or Some other kind
of Service
First Serverless API
Select Lambda for
Click on thesince
INTEGRATION Tab we
Add
are going to create a
Integration to get a
Lambda Function
drop-down
First Serverless API
The next step is to provide some
details regarding the Lambda
Function like
1) What is the Region where the
Lambda Function is located
2) What is the Name of the
Lambda Function
First Serverless API
So now we have two options here to move in further as follows:-
1) Create the End-point First and then Later INTEGRATE the Lambda Function
2) PAUSE the API creation process, create the Lambda Function First and then
RESUME the API creation continuing with the INTEGRATION process
( Suppose we take METHOD 2 – Go create a BASIC Lambda
Function and then come back here)
First Serverless API
Right-click on the Tab Bar and
choose Duplicate
First Serverless API
Type in Lambda in the Search Bar so
that we navigate to the section
where we page
Landing can create our Lambda
for creating our
Function
Lambda Function and now click on
Create Function Tab as shown
First Serverless API
Choose the option as shown, keep all other
things Default and just key-in the name of
the function say DemoAppFunction
First Serverless API
Choose Python 3.8 and keep other things pretty much default
settings Now we can select tab Create Function Since we have left
all other things with the default settings it is going to create an IAM
Role and a few other things behind the screen for us….
