Microservices
I want to start with a popular phrase that’s being quoted in the article: “ not every problem is a nail and not every solution a hammer ”. The reason to start with it is because when people know something, we tend to find a solution that fits into something we know or recently learned. So, quoting Martin Fowler on a later article 1 he wrote in 2015: “ So my primary guideline would be don't even consider microservices unless you have a system that's too complex to manage as a monolith .” Also, Fowler says on that same article 1 “ is a microservice architecture a good choice for the system you're working on? It depends… ” Throughout the original article, Fowler mentions the cases that would be the appropriate to adopt the microservices model. For many years, a lot of systems were developed and envisioned as monolithic structures that were hard to deploy, especially in large enterprise systems, that often had the problem of intertwined code, that when modified