4 ms·
Having extra code in the binary is not a serious scaling issue. You can reserve capacity for specific endpoints with an L7 load balancer, and flip config flags
by closeparen 8y ago
Having extra code in the binary is not a serious scaling issue. You can reserve capacity for specific endpoints with an L7 load balancer, and flip config flags to run different worker processes on different instances.
Microservices are not about scaling the runtime, they’re about scaling the engineering organization and deployment processes so that teams can iterate and ship independently. With thousands of engineers committing to the same artifact, the probability that at least one commit is bad (blocking rollout of all others) approaches 1.
- threeseed 8y agoIt is a massive scaling issue. Most enterprise JVM apps for example are running with 8GB+ of RAM. Adding 10x the capacity which is only needed for say sending emails can be hugely expensive or sometimes impossible if you are running on-premise. And scaling different parts of the application is just one of many benefits of microservices.
- guntars 8y agoI would think that the point of writing a single process monolith with components communicating via a bus like this is that it’s a small step to break out one of those components into a separate process and scale it horizontally.