Why Amazon Bet Early on Queues: The Philosophy Behind SQS
How Amazon's early commitment to asynchronous, queue-based decoupling shaped SQS and became a default pattern across its service architecture.
Engineering at scale
12 articles · 51 min of reading
How Amazon's early commitment to asynchronous, queue-based decoupling shaped SQS and became a default pattern across its service architecture.
How Amazon's two-pizza teams, operational readiness reviews, and correction-of-error documents work together as an operating system, not just slogans.
How Amazon Aurora separates database compute from a purpose-built, log-structured distributed storage layer to cut replication network traffic.
How AWS engineering teams adopted Leslie Lamport's TLA+ specification language to catch distributed-systems bugs that testing alone couldn't find.
Inside Amazon's PR/FAQ process, where teams write a mock press release and FAQ before writing code, and why engineers treat it as a real design tool.
How AWS's EBS team solved a control-plane consistency problem by giving every volume its own small, independently placed replicated database.
How AWS uses cell-based architecture and shuffle sharding to keep one customer's or one partition's failure from taking down everyone else.
How AWS built Firecracker, a minimal virtual machine monitor, to give Lambda functions strong isolation without paying the cost of a full VM.
How an internal Bezos mandate requiring all Amazon teams to expose functionality only through service interfaces set up the conditions for AWS.
How Amazon's shopping cart problem led to the 2007 Dynamo paper and reshaped how the industry thinks about availability versus consistency.
DynamoDB borrowed its name and core ideas from the 2007 Dynamo paper, but the managed service that shipped in 2012 made very different tradeoffs.
What Amazon S3's famous '99.999999999% durability' figure actually means statistically, and the engineering that backs the promise.