My problem with the Microservices movement is that people are applying the lessons of micro-services without having first learned the lessons of service-oriented architecture. This leads to confusion and accidental complexity.
A redditor asks:
two micro service depend[ing] on the same data storage ... is a "No No" as it can introduce lots of other complexity.
But what happens if one of the micro-service is only read only?
So here is the situation, one micro service will be an internal tool which is doing some heavy lifting and then persisting the data in the data base. And another micro-service will