3 ms·
"Monolith" is not a problem. It's just a description of an architectural approach. Often switching to alternatives, like microservices, is a terrible idea: http
by dwheeler 5y ago
"Monolith" is not a problem. It's just a description of an architectural approach. Often switching to alternatives, like microservices, is a terrible idea: https://medium.com/swlh/stop-you-dont-need-microservices-dc732d70b3e0 https://medium.com/swlh/stop-you-dont-need-microservices-dc7...
The question is: What do you actually need to do? I.e., what are your requirements?
It's all about trade-offs. If you can't identify at least one pro & one con to an approach you're considering, you don't adequately understand the approach you're considering.
- Sohcahtoa82 5y agoYou know what's worse than microservices? What I've dubbed "nanoservices". Basically, a service that hosts a single function. At a previous role I had, the dev team decided that account registration, login, and password recovery each needed to be a separate microservice. When they first described it to me, I thought they meant that maybe each was a separate AWS Lambda function behind a single API gateway or something, but no...each was in its own repo, and each was a separate container deployed into Kubernetes. I can't imagine the amount of overhead creates to manage that.