AWS Serverless Microservices with Patterns & Best Practices (Udemy.com)

This course comes from a live GitHub aws-microservices repository which verified from community with 250+ stars and 100+ forks.

In this course, we will learn AWS Event-driven Serverless Microservices with using

• AWS Lambda,

• AWS DynamoDB,

• AWS API Gateway,

• AWS EventBridge,

• AWS SQS which stands for Simple Queue Service,

• AWS CDK stands for Cloud Development Kit for IaC - Infrastructure as Code tool and

• AWS CloudWatch for monitoring.

This course will be 100% hands-on, and you will be developing a real-world application which includes;

• REST API and CRUD endpoints with using (AWS Lambda, API Gateway)

• Data persistence with using (AWS DynamoDB)

• Decouple microservices with events using (AWS EventBridge)

• Message Queues for cross-service communication using (AWS SQS)

• Cloud stack development with IaC using (AWS CloudFormation CDK)

By the end of the course, you will learn how to develop reliable and scalable Serverless applications, following the microservices architecture. We will develop event-driven microservices with AWS Serverless services which comes with power of cloud high availability and high scalability by nature. Of course we will follow the Serverless Design Patterns and Best Practices when developing our e-commerce event-driven microservices application.

There is a couple of microservices which implemented e-commerce modules over Product, Basket and Ordering microservices. We will use AWS Lambda service as a microservices and use power of lambda functions. And this microservices databases will store NoSQL AWS DynamoDB databases.

And also we have followed communication patterns and best practices when designing Serverless microservice communications for synchronous and asynchronous communications with using AWS API Gateway, AWS EventBridge as a Eventbus and AWS SQS as a queue service. That means we design our architecture rely on asynchronous connections that gives us much more flexible and resilient application.

We will use

• AWS API Gateway -for- Restful API-Driven Development and Synchronous Event Sources

• AWS EventBridge -for- Event-Driven asynchronous Communication between Microservices

• AWS SQS -for- Decouple Microservices and processing events asynchronously using queues

The course proposes a microservice oriented architecture implementation with AWS Serverless world using event-driven patterns and best practices. So the project will be the e-commerce application that will be totally Serverless components.

Let me try to introduce Serverless components one by one;

Api Gateway

• This is entry point of our microservices.

• API Gateway provides Restful API-Driven Development and Synchronous Event Sources.

• Synchronous commands are request/response.

• API Gateway is a synchronous event source and provides a Serverless API proxy to AWS Lambda.

• API Gateway Redirects to CRUD request to internal microservices.

Product Lambda microservices which performs;

• CRUD operations using DynamoDB table over the AWS API Gateway

• This will cover product table operations fully Serverless in microservices architecture.

• Synchronous requests will manage by AWS API Gateway and routing requests to Product Lambda Microservices that perform CRUD operations.

• We will write Lambda functions with using AWS SDK for interacting other AWS resources for example in Product case we will interact with AWS Serverless DynamoDB to perform all crud operations.

Basket Lambda microservices which performs;

• Add-Remove synchronous basket operations with using AWS API Gateway and DynamoDB

• Again synchronous requests will manage by AWS API Gateway and routing requests to Basket Lambda Microservices that perform CRUD operations.

• We will write Lambda functions with using AWS SDK for interacting other AWS resources. For example in Basket case we interact with AWS Serverless DynamoDB to perform all crud operations.

But also,

• Basket microservice triggers to Event-driven use case which is the Checkout Basket.

• When checkout basket, this will publish and create event to Serverless Eventbus which is AWS EventBridge.

• So this asynchronous communication will held by Basket Lambda Microservice and AWS EventBridge and consumed by Ordering microservices over the AWS SQS.

AWS Event Bridge

So asynchronous communication held by AWS Serverless Eventbus service which is AWS EventBridge.

We will create Rules and Target definitions for AWS EventBridge from Basket Lambda microservices.

That means we will develop Basket Lambda Microservices when publishing checkout message to AWS EventBridge with using AWS SDK for development purpose.

AWS SQS and Ordering Lambda microservices