In this video, we are going to learn how we can use a lambda as a microservices.
In the last video we understand that lambda function URL feature added to add is in order to adopting
organizations.
Microservice requirements organizations are adopting microservice architecture to breed resilient and
scalable applications using ADA lambda.
These applications are composed of multiple serverless functions that implement the business logic.
So let's evaluate the microservices and a lambda.
Let's remember what are the microservices?
Microservices are small business services that can work together and can be deployed autonomously and
independently.
These services communicate with each other by talking over the network and building many advantage with
them.
One of the biggest advantage is that they can be deployed independently.
Also, it offers the opportunity to work with many different technologies.
So we can say that microservices have their own technology stack, including the database and data management
model communicate to each other over a combination of rest APIs and event streaming and message blockers
and microservices organized by business capability, with the line of separating services often referred
as a bounded context.
So when it comes to a slam dunk, a slam dunk for greater agility.
It is clear that microservices can help companies be more agile and develop software faster.
So where does a slumdog come into the picture?
A place LAMDA is a service that allows you to run your function in the cloud, complete the service,
and eliminates the operational complexity.
You upload your code to the lambda and it takes care of everything needed to run and scale its execution
and fulfill conditions and high availability requirements.
Lambda supports several programming languages so you can choose the most suitable one.
It integrates with the API.
Gateway allows you to invoke functions with the API calls and make your architecture complete the service
serverless.
There are several ways to invoke a function we can invoke by event, or we can invoke another add services
or another application so we can put a number as a microservices in our applications.
You can see the image on the slide that shows the architecture of serverless microservices with a lambda
where the entire service is built from the managed services which removing the architectural overhead
of designing for scaling and high availability and eliminating the operational efforts of operating
and monitoring the microservices underlying infrastructures.
In microservice architecture, each of the application components is decoupled and deployed and run
independently.
An API creates with the Amazon API gateway and then a lambda initiated function is all we need to build
as a microservices.
Team can use these services to decouple and segment your environment to the desired level of details.
In general, in general, a microservice environment can introduce any difficulties, for example,
repeated overhead for create each new microservices and also problem optimising server density and usage
and complexity of running multiple versions of multiple Microsofts at the same time, and client side
code requirements to integrate with many services.
When you create microservices using serverless resources, these problems become less difficult to resolve
and in some cases simply disappear.
So the serverless microservice pattern reduces the barrier for the creation of each subsequent microservices
API gateway, even allow for the cloning the existing APIs and using the lambda functions in other accounts.
Optimizing server utilization is no longer relevant with this pattern.
Finally, Amazon API Gateway provides the programmatically generates the client case that are programmatically
a number of popular languages in order to reduce the integration overhead.
We can see the image on the slide that shows the architecture of serverless microservices with using
Amazon API Gateway and a Lambda.
So API Gateway API is proxy to individual microservices backed by the lambda functions.
You can see the microservices one, two, three and four.
That proxy by the ADA is Amazon API Gateway and all the microservices handled with the ADA Lambda functions.
So as you can see that we have understood that we can use a lambda as a microservices in serverless
architecture and we understood that the importance of the function URLs in a lambda as a microservices.