3 ms·
One advantage of a microservice architecture not mentioned in the article is the ability to scale services independently of other services. Being able to fire
by patrickmay 11y ago
One advantage of a microservice architecture not mentioned in the article is the ability to scale services independently of other services. Being able to fire up more instances to address a bottleneck is often much simpler than managing threads in a monolith.
- bozho 11y agothat is true in some very rare cases. CPU-intensive bits of the application should definitely be separated, so that they can scale independently. But that's not the main point of microservices.
- acdha 11y agoI don't think I've ever seen a piece selling the benefits of microservices which didn't mention the scaling or reliability benefits as a primary motivation.
- abritishguy 11y agoI would concede that it only happens at scale but I would contest that it is rare.
- deleted 11y ago[deleted]
- beberlei 11y agoyou can often as easily deploy a monolith to multiple servers and grant different subtasks different cpu and memory for their work. for me its just a matter of adjust with the supervisord config for each server, how many of which workers start and run on that machine.
- ap22213 11y agoThis is an important point. If you have a system that processes billions of inputs a day along a fairly complex pipeline, you're constantly scaling up and down. It would suck pretty bad if you had to scale mostly vertically.