Even Amazon Can't Make Sense of Serverless or Microservices

First, most of the customers I meet think they have a technology adoption problem, when in reality they have an org-chart problem. The most successful orgs are made up of many small independent business teams communicating via clear APIs. If that’s your org chart, you will inevitably build a microservices architecture, a trick known as the Reverse

Each year, it took longer and longer to ship features to customers, and the risk of even small changes causing major problems kept growing. In 1998, developers could make changes and deploy them immediately. By 2004, pushing code changes into production required hours, even days, to be deployed.39 Teams were no longer able to solve Layer 1 problems

IT’S EASY TO recognize the transformative impact of network-based businesses on society without understanding just how differently they are organized inside their walls.

The book, though dense and challenging, was widely discussed in the book clubs of Amazon executives at the time and it helped to crystallize the debate over the problems with the company’s own infrastructure. If Amazon wanted to stimulate creativity among its developers, it shouldn’t try to guess what kind of services they might want; such guesses

Functional decomposition, therefore, tends to make services either too big and too few or too small and too many. You often see both afflictions side by side in the same system.