Building Modern Distributed Systems with AWS
summary
Catalog runs as a Lambda serving images from S3 cached in ElastiCache behind CloudFront and API Gateway, while orders use DynamoDB with DynamoDB strong consistency for deduplicated writes; fulfillment and notifications move via queues and topics using SQS / SNS / EventBridge and streaming for high-throughput telemetry; returns use Step Functions for coordinated retries. Capital One reports decade-long migration since 2014 with full cloud by 2016, 14,000 engineers, two GenAI use cases in 2025, and measurable cost, scaling and deployment-speed improvements using CloudFront + API Gateway + Lambda.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03Capital One’s cloud journey
- 6:43Monolithic limitations
- 9:13Why distributed systems
- 13:56Advantages of distributed systems
- 14:58E-commerce case study
- 18:59Synchronous AWS patterns
- 22:06Asynchronous AWS patterns
- 27:47AWS Step Functions
- 29:50Best practices
- 33:22Q&A
related talks
56mArchitectural Patterns in the Serverless Journey of shop.LEGO.com
49mBuilding Next-Generation Applications with EDA
35mBuilding Systems that Last
17mHow do we use Serverless Architectures on AWS Lambda
24mModernise using Event-Driven Architectures
23mSimplifying design complexities using Serverless Architecture on AWS
40mEDA in Practice: Building an eCommerce Platform at
58mFaster, Cheaper, Greener: Pick Three
