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.
Category
6 articles
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 uses cell-based architecture and shuffle sharding to keep one customer's or one partition's failure from taking down everyone else.
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.