> "All service interfaces, without exception, must be designed from the ground up to be externalizable." **Source**: Jeff Bezos internal memo at Amazon, circa 2002 — made public by Steve Yegge's "Stevey's Google Platforms Rant" (Oct 2011), accidentally posted to public Google+. Verbatim text retrieved from [GitHub gist archive](https://gist.github.com/chitchcock/1281611). Research notes: [[20260415 Steve Yegge Platforms Rant + Bezos API Mandate]]. ## The Mandate (verbatim from Yegge's Rant) > 1. All teams will henceforth expose their data and functionality through service interfaces. > 2. Teams must communicate with each other through these interfaces. > 3. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. > 4. It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols — doesn't matter. > 5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. > 6. Anyone who doesn't do this will be fired. ## Why It Mattered - **Forced architectural discipline**: removed back-door integrations that make microservices fail in other companies. If the only way to talk is through APIs, the APIs must actually work. - **Made AWS possible**: you cannot sell EC2/S3/DynamoDB externally if your internal services were built with shared-memory shortcuts, colocated databases, or implicit coupling. The mandate's rule #5 (externalizable from day one) is what made productization feasible a few years later. - **Organizational, not technical**: Bezos didn't mandate a technology stack; he mandated a *communication topology*. Technology choice was delegated; the rule was the shape. ## Connection to Vitillo's Framework Bezos mandated the **shape** of the architecture: services behind APIs, no side channels, externally consumable. [[Ports and Adapters for Distributed Services]] is the **implementation discipline** that keeps that shape working: business logic independent of transport, adapters as the only path in and out. Vitillo's [[Five-Challenge Frame of Distributed Systems]] is the set of problems you inherit once you operate that shape at scale (communication, coordination, scalability, resiliency, maintainability). Read in sequence, the Bezos mandate is *what* to build and Vitillo's book is *how* to keep it alive. ## Lessons That Generalize - **Ban the side channel**: a single exception to "everything through the API" makes the API a lie. Discipline comes from having no legal alternative. - **Design for external consumption first**: the forcing function for a clean interface is "someone outside the company must be able to use this." Internal-only APIs decay. - **Mandate shape, delegate technology**: the durable rule is the communication topology, not the protocol of the month. ## Related Concepts - [[Ports and Adapters for Distributed Services]] - [[Five-Challenge Frame of Distributed Systems]] - [[Software as Decision Artifact]] ## Tags #software-architecture #organizational-design #microservices #amazon #api-design #bezos