3 ms·
microservices: let's take the hardest problem in software construction, factoring the system properly, and introduce network connections and deployment complexi
by recursivedoubts 5y ago
microservices: let's take the hardest problem in software construction, factoring the system properly, and introduce network connections and deployment complexity into it.
yeah, there's a place for monoliths, and developers who are willing to ignore the industries ludicrous fads and faang-chasing have the advantage.
- kawsper 5y agoDon't forget things like routing, authentication, certificates, logging, deployments, error-tracking, monitoring, error-handling and service-meshing. Sure, it probably gets easier when you're booting your third or fourth microservice, but there's a lot of overhead.
- Veuxdo 5y agoFor some, the overhead is the point.
- fourseventy 5y agoexactly, thank you
- UglyToad 5y agoI feel like the hype made a lot of people (not you) forget there's a middle ground, like you can't just have "services". I therefore propose a new hype cycle "mesoservices", i.e. only split out a service from the monolith when needed and it just does as much as is necessary.