Resilient Cloud Architecture Design Patterns
summary
Nine concrete patterns and AWS tools for surviving failures: a 500 ms UX target and 99.99% availability (~6 minutes/month) drive choices; deploy behind CloudFront and ELBs with autoscaling, use S3/EFS for shared files, multi‑region read replicas and DynamoDB/Redis caches, offload work with SQS with dead‑letter queues or Kafka for replayable events, adopt CQRS/commit‑log replay, and protect with circuit breaker and exponential backoff plus chaos experiments and Trusted Advisor checks.
AI-written summary · about
chapters (18)
- 0:00Introduction to resilient cloud
- 1:02Nine critical resiliency areas
- 2:06Defining failure points
- 6:15Resiliency principles
- 8:04Evolutionary cloud architecture
- 11:34Scaling and caching strategies
- 18:21Cell-based architecture
- 22:22Autoscaling fundamentals
- 23:05Reactive architecture basics
- 25:14Message queues and SQS
- 31:41CQRS and event sourcing
- 36:19Recovery point objectives
- 42:07Asynchronous communication
- 43:09Timeouts and circuit breakers
- 47:23Eventual consistency
- 51:02Caching importance
- 53:08Chaos engineering
- 54:57Q&A and resources
related talks
49mPatterns for resilient, highly available cloud architectures
48mResiliency and Availability Design Patterns for the Cloud
35mBuilding Resilient Workloads on AWS: Tools and Techniques
10mDesigning for Failure using AWS: Resilient Systems
16mResilient by Design: Architectures for Crisis Response & Recovery
25mChaos Engineering for Cloud native Apps
39mCloud Native Architectures
30mArchitecting for Active-Active Resiliency in the Cloud