Serverless Architecture Patterns in AWS

Serverless Architecture Pattern 1 — Backend API Service
Serverless Architecture Pattern for Hosting Microservices
  1. Each Team manages and owns end to end service deployment — API Gateway, Lambda functions and DynamoDB.
  2. Each service gets deployed in a different AWS account (managed by the service team). It inherently increases the TPS of the overall product because API Gateway and Lambda functions concurrency limit are at the Account level. These limits are off-course soft limits and can be increased by raising a case via AWS Console, if you plan to host the services in the same AWS account
  3. Each service can have a custom domain attached to it. Something like — OR
Serverless Architecture Pattern for Backend and Frontend Service
  1. The SPA static frontend application is hosted on a private S3 bucket and proxied via AWS CloudFront service. This allows you to give a custom domain to the web application. Apart from that CDN capabilities of the CloudFront can also be leveraged to have low latency while serving the content.
  2. Backend Service is hosted using the API Gateway + Lambda + DynamoDB stack, coming from Pattern #1.
Serverless Architecture Pattern — CloudFront with Regional API Gateway
Serverless Architecture Pattern for Backend and Frontend Service using Single CloudFront Distribution
Serverless Architecture Pattern — Storage First
Serverless Architecture Pattern 7
  1. Secure static site
  2. Enhanced Origin Failover
  3. Add Security Headers for the static site
  4. A/B Testing
  5. Progressive rollout for static site



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Naresh Waswani

Naresh Waswani

#AWS #CloudArchitect #CloudMigration #Microservices #Mobility #IoT