undefined | Better HN

0 pointsJamesBarney6y ago0 comments

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".

0 comments

2 comments · 1 top-level

rumanator6y ago· 1 in thread

The 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

JamesBarneyOP6y ago

Is 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.

j / k navigate · click thread line to collapse