Decoupling AWS Infrastructure (Part 2)

Part 1, Part 2

Introduction

In my last article, we learnt what is decoupling and why we use it. Also, we know some strategies to decouple the architecture. And we introduce AWS SQS and SNS can help us in decoupling. This time we will talk about loose coupling with DynamoDB, API Gateway, AWS Lambda and show some examples.

Loose Coupling With DynamoDB

Let’s review the characteristic of of DynamoDB. It has high availability, fault-tolerant and fully managed service. Therefore, DynamoDB is a great solution for storing and retrieving our processing output with high throughput. Loosely coupled systems can work very well with a managed NoSQL database solution like DyanmoDB.

Below is an example of a mobile voting platform.

Amazon API Gateway

API Gateway allows us to create APIs that act as front doors for our applications to access data, business logic, or functionality from our back-end services. It is fully managed and can handle workloads running on EC2, AWS Lambda and any web application.

In my previous article, we have a demonstration as above solution.

AWS Lambda

AWS Lambda is a great solution for processing data with high availability and a limited cost footprint. It allows us to further decouple our infrastructure by replacing traditional servers with simple microprocesses.

Above services can trigger for AWS Lambda Functions.

However, there are some limitations of AWS Lambda. AWS provides the memory range is 128MB to 1.5GB with 23 different levels.

Decoupling Examples

Conclusion

From these two articles, we learnt the benefits of decoupling. In fact, this is a trend for developing an application. Without servers, we could pay much more effort on development.

Leave a Reply