3 ms·
Microservices really shine when your setup requires HA everywhere. If you're running multiple copies of everything and need your overall product to still run wh
by athenot 8y ago
Microservices really shine when your setup requires HA everywhere. If you're running multiple copies of everything and need your overall product to still run while parts fail, then it's a lot easier when the individual parts are small microservices that do one thing with predictable operating conditions.
If you're not running in High Availability, and can tolerate one copy of everything, then monolithic probably makes more sense. Glue it all together and roll out improvements across all the parts at once.
- eropple 8y agoThis is not a real distinction, though. You can have N instances of a monolith if it's written smartly (generally speaking, where "smart" equals "is a twelve-factor app"). And frankly, for the 95% and probably the 99% case, running a copy of each monolithic application its own auto-scaling group is probably significantly less work and less hair-pulling than the chasing the microservice dragon.