Serverless Architecture for Global Applications
Publication date: October 15, 2020 (Diagram history)
This architecture shows how to improve customer experience on your global services by deploying into multiple AWS Regions. You can apply event-driven architectural patterns such as event sourcing, saga orchestration, and CQRS to reduce latency and increase performance.
Serverless Architecture for Global Applications
The following steps describe the architecture:
-
Route traffic from edge locations based on the request path using Amazon CloudFront, allowing gradual migration of single-CNAME legacy API operations. Then route requests to the Region with the least latency using Route 53.
-
Front each Region with an entry API using Amazon API Gateway implementing the CQRS pattern. For query requests, read from the data layer. For synchronous write commands, invoke the logic layer.
-
Process asynchronous commands by adding them to the event bus using Amazon EventBridge. Source additional events from external systems.
-
Process transactional logic with AWS Lambda functions and run long-running tasks with containers on AWS Fargate. Use the Saga pattern to orchestrate distributed transactions with AWS Step Functions for eventual consistency.
-
Store data for access patterns using Amazon DynamoDB for key-value stores, Amazon Aurora for relational queries, and Amazon Simple Storage Service for data lake analytics and AI/ML.
-
Raise logic events from the logic layer to run event-driven workflow steps following the Transformation pattern.
-
Raise data events after changes to the canonical data model on the data layer, reducing redundancy in the logic layer.
-
Propagate changes across Regions with active-active data replication using DynamoDB Global Tables, Amazon S3 Cross-Region Replication, and Amazon Aurora Global Database.
-
For heavy reading scenarios on other Regions, send write requests to primary Regions. For fast global writes, replicate the event and command logic on all Regions.
Further reading
For additional information, refer to the following resources:
Diagram history
To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Initial publication | Reference architecture diagram first published. | October 15, 2020 |
Note
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.
