The funny thing is that this is probably the best strategy for the devs. The people who have chosen to stick with monolith for good reasons will get no respect from the next employer. Whereas the Microservices guys will be hotshots.
Hadoop+Hive are in the same category for our IT department. Instead of putting stuff into a SQL DB they are pushing to put all company diagnostics data into Hadoop and run SQL queries against Hive. Now we have minimum query latency of of over 1 second even for the most trivial of queries.
In my experience, this is by far the largest group. Then they build a distributed monolith and cause a giant mess, like the OP was describing. I really wish people would jump off of the microservices bandwagon, because so very few on it actually understand microservices at all, or have the skill set to make them work.
Well, one issue is that everyone seems to have a different picture about what a microservice is and everyone also thinks they have the correct understanding.
And the fourth which is haphazardly ending up on them due to the way the organisation is laid out and not invented here syndrome. Its mostly an organisation pattern not a technical one.
