If you have been in the business for the last 5-6 years you have been indefinitely forced to hear some buzzwords like microservices, modularization, loosely coupled, split or independence popping up in every single company, but are those concepts even in context? With the proliferation of tech companies and the increase of code lines, pairs of hands has grown in an exponential way and, just to let you know, the ratio between the number of developers and code efficiency in a single code base forms a perfect gauss bell.
Having that in mind, is easy to realize that large companies will have serious constrains building and deploying big products and hotfixing or continuous deployment will be even harder objectives (sometimes impossible).
With that problem in game, there’s the need of a solution, and it’s urgent. Here’s exactly where microservices architecture enters the scene.
This is a farely new architectural style that structures the application as a collection of modules called services. Services have to be error-proof, loosely coupled and must have a clear, easy to interact with I/O interface in a lightweight non blocker protocol.
Microservices must be fine-grained,