> scaling up to handle more concurrent requests, hitting your SLA uptime, reducing defects or memory usage by avoiding statefulness, reducing latency, separatio

> scaling up to handle more concurrent requests, hitting your SLA uptime, reducing defects or memory usage by avoiding statefulness, reducing latency, separation of concerns to improve maintainability, etc. > Are these not immediately obvious impacts to the business? Depends; for b2b loads all those concerns but the final one can be be met with a single beefy server for DB writes, with multiple read only replicas. Run multiple instances of your monolith app behind a load balancer and you should be good for maybe 100k users working on that app at mostly the same time. With care (redis serving session data) this is fine for even very high loads. Once you start doing b2c and have millions of users logged in and doing stuff at the same time then those concerns are valid.