Amazon's technologies are almost exclusively implemented as services with hardened interfaces as the only access to functionality.

Judged as of 2011. The claim is qualitative: 'almost exclusively' means that nearly all of Amazon's technology was built as services reached through service interfaces/APIs (a service-oriented architecture). True: credible descriptions from around 2011 (Amazon engineering accounts, CTO talks, technical papers, documented internal mandates) show that Amazon's systems were overwhelmingly structured as services reached only through interfaces. Mostly true: a services architecture predominated, with notable but limited exceptions. Mixed: services were a major part, but much of the technology stayed monolithic or was reached directly. Mostly false: services were a minority approach. False: Amazon did not use a service-oriented architecture.

Set before the research began.

1. E1 Amazon Architecture - High Scalability High Scalability · 18 September 2007

   “The databases were split into small parts and around each part and created a services interface that was the only way to access the data.”

2. E2 Amazon Architecture - High Scalability High Scalability · 18 September 2007

   “Internally it's a service oriented architecture. You can only access the data via the interface.”

3. E3 I was at Amazon for about six and a half years, and now I' ... sriramk.com (hosted copy of a former Amazon engineer's essay) · 9 August 2026

   “Over the next couple of years, Amazon transformed internally into a serviceoriented architecture.”

4. E4 Modern applications at AWS All Things Distributed (Werner Vogels, Amazon CTO) · 28 August 2019 Own record

   “With this manifesto, we began restructuring our application into smaller pieces called "services" that enabled us to scale Amazon dramatically.”

A 2007 independent article on Amazon's architecture describes Amazon's internal architecture as service-oriented [E1][E2]. It says databases were split up, with a services interface that was the only way to access the data (E1, E2). A former Amazon engineer's essay says the company transformed internally into a service-oriented architecture over a couple of years (E3). The CTO's own later account of restructuring the application into services (E4) agrees with this. Together these sources describe Amazon's internal architecture as service-oriented, with data reached only through service interfaces, though none of them gives a figure for how much of its technology was built this way.