Re:Developers Are the Problem, Not Monoliths
by mbrodersen on Tuesday February 12, 2019 @07:00PM
(#19149001)
Change "micro-service" to "library" and you have a technology that scales equally well without introducing the additional failure modes and complexities of micro-services. That's how pretty much all open source software works. Open source software consists of thousands of libraries that people reuse for all kinds of purposes.
Re:Developers Are the Problem, Not Monoliths
by tracker1 on Monday February 11, 2019 @07:52PM
(#19140030)
I'm not against smaller services... but I've seen people use them, "because" and break their data models into separate services where coordinating data then becomes weird to say the least.
I'm not against micro-services, I'm against making everything a microservice because one can.
I can say this based on four years working on a large multi-tenant service platform composed of several hundred microservices, held against a background of 24 years building software systems, including multi-million-line monoliths (good and bad).
If you're a small company, should you start with a microservices architecture? No. It is much harder to operate. Should you factor your monolith so it is easy to transition to microservices later? Yes. Your monolith will be of higher quality for doing so.