Hacker News new | ask | show | jobs
by satyrnein 1663 days ago
At a previous company. I had a team that chose to rebuild a feature from the monolith as a microservice to "contain" the complexity. They built the service off to the side, had automated tests validating its inputs and outputs, and they were quite proud of it. Then came integration, and it became clear they had not put any thought into how to migrate the data, what would happen if the service was unavailable when the monolith called it, how to generate reports across the monolith and microservice, etc etc.

In this case, using microservices was like getting drunk: a way to briefly push all your problems out of your mind and just focus on what's in front of you. But your problems didn't really go away, and in fact you just made them worse.