Amazon Architecture

From a monolith to the service-oriented template for modern commerce.

On the roadmap:Software Architect · step 5: Learn from the giants

Overview

Amazon pioneered service-oriented architecture and 'you build it, you run it' teams. Dynamo, its highly available key-value store, shaped the NoSQL movement.

Architecture highlights

  • Two-pizza teams owning services end to end
  • Dynamo: eventual consistency for availability
  • Cell-based architecture to limit blast radius
  • Extensive use of timeouts, retries and backoff

Architecture diagram

Key components

  • Service mesh of APIs

    Every capability exposed via a service interface

  • Dynamo / DynamoDB

    Always-writable key-value storage

  • SQS / SNS

    Asynchronous messaging between services

  • Cart & checkout

    Availability-critical shopping flow

Challenges and trade-offs

  • Availability over consistency

    A cart must accept writes even during partitions; conflicts are reconciled later.

  • Peak events

    Prime Day demands capacity planning and load shedding.

  • Org-scale coordination

    Thousands of services need strict API contracts.

Study: Amazon

Learn how Amazon is built from the people who explain it. Watch first for the picture, then read for the detail.