2 ms·
You should actually try microservices in a larger team before dismissing all these. Having large feature sets behind a load balancer and having the rest of the
by jayd16 7y ago
You should actually try microservices in a larger team before dismissing all these. Having large feature sets behind a load balancer and having the rest of the app fail gracefully when a feature goes down, means you can have worry free deployments. You can deploy a single feature, you can do a tiered role out on a feature, without impacting any other service. You can also easily deploy more instances of a service. As long as you've done the work to make your internal requests stateless then you should be able to maintain high perf by scaling instances.
Beyond Polygot, I would instead phrase it as new features can roll out without dealing a large legacy tier of code. Most of your code can be Java with a single high performance service written in C++, lets say. If you're compressing video in an async manner, do you really want to throw that in your RESTful Spring service?