What’s the Point of Microservices?
They were initially created with one objective, but nowadays most of the software developer teams do not know.
I don’t know you or what you know about microservices, but it’s more likely that you know the following: it consists of splitting services into several smaller ones to create a more flexible and maintainable environment. Although it is one of its benefits, it was not the objective for which microservices were designed in the first place.
If you are one of the few who are lucky enough, you probably know that microservices are very closely related to the creation of DDD (Domain-Driven Design). Under this working methodology, each microservice corresponds to one specific domain.
So, for example, if you are a clothing shop, you may have one domain for product design, another for warehouses, and another for shops; that would make three domains and three different microservices. Well, we are closer, but it is still not the objective.
The main point of microservices is to be able to make several teams work independently. In fact, it is also the objective of DDD. And it is one of the most complex problems that big developments face.
