In this video, we are going to do Hands on lab, which is the pen out service architectures using SAS,
ESCs and Lambda.
So let me show you the architecture and the architecture that we are going to do together and we will
use, publish, subscribe, fan art design pattern when developing these hands on lab.
So basically we are following the ecommerce architecture and our use case is order processing order
fulfillment process.
First of all, we will start from the client application.
Think about that.
We are a customer and we are using web or mobile application and we are placing an order or checkout
an order.
So the client application sent this request to Amazon API Gateway endpoint, and this endpoint is the
front door of our application after that API Gateway sent to order request to the first microservices,
which is the order acknowledgement microservice.
So these microservices is using a lambda as a microservices for computing and we will develop these
lambda function to perform some actions.
So order acknowledgements.
Microservice does four thing.
The first thing is it verifies the incoming request and generates the order ID and after that it is
insert item into the order dynamo DB table to store the incoming event.
And after that Lambda sends a confirmation message back to the API gateway with order ID for the synchronous
response.
And of course lastly, these microservices publish a message to the Amazon sans Amazon SMS which will
be sent to downstream to different microservices.
So this message will be pop up messaging using the Amazon Psns and these order acknowledgment microservices
will be the publisher of the message.
So in the DOM State, in microservices we have notification microservices and these will be sent email
and SMS notification to the customer.
And we have also invented Microsoft in microservices.
It is for the deducting products from the warehouse and we have shipment microservices for the shipping
products to the customer.
And we can also add additional microservices which will be data lake ingest in microservice to ingest
all data generated from the any process into their data lake for arbitrary analytics.
So the important thing is we will use Amazon SAS and as queries in order to apply, publish, subscribe
panel design pattern.
So we will put individual SKUs in front of the all downstream microservices and use SNS to fan out the
message to these queues.
Once the order data reached the queues from the SAS, a lambda downstream microservices automatically
post the queues and extract message in a batch and invoke lambda functions to process them.
So we will also use Amazon SAS Filter feature.
You can see in here one sending the message to SKUs because in distributed architectures, not every
message is required to be sent evidence through microservices.
So we will conditionally send the message based on some attributes in the message body.
We will use filter criteria in SAS filter feature before sending message to the excuse.
So in this section we will learn how panel design pattern apply with using the SAS and the case that
enables asynchronous message communication.
Then we will link distributed microservice architectures as we know that when we develop any architecture
on a yes, we have two main steps.
The first step is create infrastructure on a cloud and the second step is develop lambda code for interacting
SNS.
So we will start with the first step and create these architecture and infrastructure into our ID,
which is called environment.
But before that, let's start to remember and learn, publish, subscribe, fanart and topic, chaining
design pattern and best practices.