Member-only story
Microservices Are Not a Silver Bullet. Learn Why.
To microservice or not to microservice?
In the last few years we were bombed by a mantra: using microservices, the monolith is the evil. Since then, those who are maintaining an old codebase, or are implementing a simple MVC website, have to fight with the sense of inadequacy for not following the microservice pattern. Did you ever get that feeling? Well, I suppose most of us do.
Microservice is an architectural principle that improves maintainability and speeds up development. Probably, it is the only way for delivering complex projects without falling into architectural problems. But what if you do it in the wrong way? Microservices is a pattern that doesn't allow compromises: or you do it right or it’s better don't do it. That’s another mantra we heard so many times that we think it’s true.
In this article, I will explain what are microservices and how they can be useful for keeping a clean architecture and getting the best from your software. Then, I will explore all the criticalities you can find during the path so that you will be able to adopt it consciously.
Why Do We Need Microservices?
Microservice is the evolution of best-practice architectural principles for delivering software solutions.