Microservices: maybe not
Microservices have been gathering some attraction for the past several years for a reason. Microservice-based architecture proved its efficiency and won the hearts of many developers.
But as with any other thing under the sky, microservices is not a silver bullet, it’s a tradeoff. And as with any tradeoff, it’s good to know what you gain and what you lose.
So before you sell your soul to the devil, let’s at least take a quick glimpse into the contract.
The downsides of the microservices
Here the most evident arguments for why forcing the microservices architecture may be a bad thing.
The overall complexity is gonna rise
Compared to a monolith, where you have a single repo and a single database, now imagine you have over 20 repos and you need to make sense of them, like how they interact with each other, what APIs they provide and consume, messaging and so on.
Development time is...
Continue reading →