4 ms·
My thought is that this comparison between a monolithic code base vs a microservices code base is a bit subjective. If you're starting out chances are your code
by josh_carterPDX 10y ago
My thought is that this comparison between a monolithic code base vs a microservices code base is a bit subjective. If you're starting out chances are your code base hasn't even gotten to the level of being monolithic. So those thinking about how they're going to architect their platform may begin to think that a microservice setup could help for future changes to their code. It really depends on each team, their background, and how they want to think about their platform in the future. To list out the pros and cons of both to draw a conclusion that one is better than the other is certainly setting a bias that I believe to be a bit unfair. Just look at Netflix and their container services. It's a platform adopted by a ton of companies including Nike. So for some a microservices approach makes a lot of sense.
- StabbyCutyou 10y agoYou have a good point in that in the early stages, any app is likely not to be a "monolith", but it's less about size/LOC and more about the design ethic of the architecture itself. If you build your codebase internally with service level abstractions in mind, you can gain a lot of benefit without the cost of the network or the additional errors it can introduce. Thanks for reading!
- josh_carterPDX 10y agoI guess, in my head it's also eliminating a lot of code bloat using microservices. Just my opinion though.