3 ms·
I feel like the debate between the microservices evangelists and the contrarians are "Microservices are a best practice you should almost always use" and "Micro
by JamesBarney 6y ago
I feel like the debate between the microservices evangelists and the contrarians are "Microservices are a best practice you should almost always use" and "Microservices are a tool for primarily splitting up development teams when they get too large to manage, i.e. a technical solution to an organization problem".
- rumanator 6y agoThe organizational part is just one of the many advantages, and arguably the least relevant of the bunch as it's only relevant for huge projects requiring dozens of developers working concurrently
- JamesBarney 6y agoIs modularity a huge benefit when most languages allow you to compose applications into modules which have keywords to enforce encapsulation? And scalability seems like an incremental benefit at best. If you're cpu bound you can load balance without microservices. And if you're database bound (and have already cached, optimized, and scaled up your db) you can scale up your db to multiple instances. Even Stackoverflow runs their entire infrastructure on just 4 db machines.