What are monoliths?
You know that gigantic project that you already work on, that does everything and has everything inside you. So, this is the famous monolith project, a bloated project, with a low life expectancy and that just gives you a headache.
In what situations is the monolith necessary?
Here I will expose my opinion, which is never and I will explain why I think so.
To some who will say that very small and simple projects should be in monoliths and that later on with the growth of the project it will be migrated to microservices, and what a problem with that! The problem with this is that it almost never happens. I only see one possibility for projects to be done in monoliths, which is school and college projects.
But it's not all lost
The experience in projects made in monoliths, despite being traumatic, is very important for the maturation of developers, because there you will see, in practice, what should not be done, and the chaos that this generates.
What are microservices?
Here you should already imagine that microservices are the complete opposite of what I mentioned above, but not and there. Microservices have to be well planned and architected. The delegation of functions must be strategically divided. As the name implies, microservices and dividing an application into small services, similar to a circuit board in a computer, looking at it, we see that each chip has a specific function, as it should be done in microservices.
When building a microservice, good programming practices, Design Patterns and SOLID patterns must be considered, otherwise our entire proposal will be lost.
So summarizing about microservices. Microservices and you strategically fractionate a project into small pieces and hierarchies in an organized and independent way, a special focus on this keyword here "independent" which is the basis of the concept.
)
Top comments (0)