3 ms·
If I learned one thing in Software Engineering it's "modularization matters most". And microservices seem to be the epitome of this concept. If you have to wor
by k__ 11y ago
If I learned one thing in Software Engineering it's "modularization matters most". And microservices seem to be the epitome of this concept.
If you have to work with different people, you need a way to minimize dependencies between them.
Also, the more encapsulated things are, the less the starting skill of a person matters. You just need people who get things done. Later you can switch out the bad modules easily. Which is a huge economic factor.
I can't count the hours I spent with fixing horrible monoliths and the years it took to replace them.
But if there is a horrible microservice, you can do this in a fraction of time.
- jasonkester 11y agoSadly, often the reason you need to work with different people is that you've architected your product to be so complicated that it needs lots of guys working on it. It's amazing how much a team of one can do if you don't saddle said team with arbitrary complexity such as a microservices architecture. Maybe you'll need to scale to that level one day. But you'll definitely want to ship. One guy and a sane architecture can do that.