My microservices hurt

Humor me for a second and let me know if this works:

• Open your favorite IDE, go to the menu and try the sequence “File → New Microservice” (or similar commands). With luck, if you installed possessed plugins or use high tech tools, you will have some options available. In any case, if you get a result, tell me what you see in front of your eyes. Did any type of editor for typing code open or was an element of software called “Microservice” created?
• Go to your favorite internet browser and try installing a microservice… any microservice is useful as an example, whichever you want. Simply install a microservice. Did you? Tell me what you see in front of your eyes. Was any file installed that can be opened with an application or that can be executed to “do something”?

I have to confess that I would be surprised if I had answered, “Yes,” to any of the questions that I asked. And it makes a lot of sense that you answered, “No,” since everyone knows that a “microservice” isn’t even a software element (class, function, procedure, component, routine), nor is it an application or a software tool.

What I’m going to ask you next uncovers a disease that is killing me: Why do we go around proposing magical solutions based on making a microservice (as if it were a software element) or using a microservice (as if it were a tool)? I felt sick the day I heard: “Hey, we have to microservice this.” It seems it’s a verb now!! An action!! Please pardon me for a minute, I need to take my medicine.

Microservices is the name of an architecture style (or architectonic patron, if you like taxonomies). Either way, it represents a combination of design decisions conveniently grouped to build a solution that favors specific quality attributes when they present some solid problems in a determined context. Therefore, the sequence of thinking is: given a context in which certain problems are evident, it is convenient to base the solution (or one part) on a certain architectonic style to favor determined quality attributes.

Microservices aren’t made. They aren’t used. They are built solutions based on the style of Microservices. Regarding solid software, I recommend speaking in terms of the modules or components, depending on whether it refers to the programming code or what the computer executes.

To summarize:

• Context: I have a medium-large cache of software for which I accumulate very often a handful of changes based on the needs of various types of users, and I am unable to apply them in a timely manner in order to release the new versions as soon as possible. What ends up happening to me is that new releases are delayed because I always have a change in progress, and in the meantime, users continue to use an old or defective version. 
• Problems: How can I update and release different parts of software in an independent way depending on where the changes are made? How can I release new versions of all the parts modified as fast as possible, so the users don’t have to wait so long for the changes? How can I deploy the different parts of my software if each one has different versions?

Microservices solve a problem of Release and Deployment that favors, mostly, the modification of the system. That is to say, they satisfy the expectation of the business that the system assimilates fast changes (read: to the least cost possible). It is an intrinsic economic expectation of the business.

You likely know the recipes for implementing solutions to these problems because they aren’t new. What is happening is that technology enables us, increasingly, to reduce the costs of change.