Microservices

Microservices is an article written by James Lewis and Martin Fowler in 2014 and the main objective of this article is mainly to describe what they are, how they work, what they are for and describe the capabilities that use this type of architecture. First of all, it is important to answer. What does the term Microservice Architecture refer to? According to the article, this term is intended to describe a way of designing software applications in which the software responds to certain functions, which are managed as independent suites. To achieve a better understanding of how this type of architecture works, the authors in their article make a good comparison between Microservice Architecture and the monolithic application, in summary, this comparison is based on the fact that the monolithic application groups all the functions within the same suite or a simple process and to scale it what is done is to multiply these monoliths in different servers, while for its part the Microservice Architecture separates each function as different elements and scales it by distributing these elements through the servers as they need it. I think that the main problem that we must consider, since it is something that we face when using this microservice architecture, is that when designing applications, it must be taken into account that they must be capable of tolerating service failures. Unfortunately, flaws in the system of an application using the microservice architecture are fully reflected in the user experience, subtracting points from the good experience that the client may have when using it. It happens that this architecture can look like is the one that anyone (any service, or business) needs, but as the authors emphasize there hasn't been enough time to define if we should consider microservices as the future of software.