> There is more than one way to achieve scalability. Microservices is just one of the possible choices. It annoys me that developers increasingly see it as the

> There is more than one way to achieve scalability. Microservices is just one of the possible choices. It annoys me that developers increasingly see it as the only one. Agreed. You can ensure a monolith is written such that it only performs expensive operations just in time. Then sit behind a load balancer and enjoy. For example say you have 12 machines serving your REST API. If one particular service/route is impacting other services it is straightforward to deploy the entire application onto a dozen more machines and have the load balancer route the problematic service through to the new machines. That won't get you google/facebook level scaling.... but neither will a basic microservices architecture.