I’ve worked on projects where microservices are a godsend. I’ve also worked on a 12-endpoint REST API atop a SQL database and an Elasticsearch instance serving 500 internal users that somebody had engineered into 8 microservices because management thought microservices were the future. Real mixed bag.
That’s fair. I think they’re are definitely systems where micro services are the best choice, but also that they are way over used or implemented too early. Too often it seems service boundaries follow the organization and not the domain model, because they only exist so multiple teams don’t have to talk to each other as often. I guess I’m saying there are more incorrect ways of doing micro services than correct ways.
The worst I’ve seen though have been a single developer over engineering a system because they thought it was cool, but we replaced it with a simple batch script.
I’ve worked on projects where microservices are a godsend. I’ve also worked on a 12-endpoint REST API atop a SQL database and an Elasticsearch instance serving 500 internal users that somebody had engineered into 8 microservices because management thought microservices were the future. Real mixed bag.
That’s fair. I think they’re are definitely systems where micro services are the best choice, but also that they are way over used or implemented too early. Too often it seems service boundaries follow the organization and not the domain model, because they only exist so multiple teams don’t have to talk to each other as often. I guess I’m saying there are more incorrect ways of doing micro services than correct ways.
The worst I’ve seen though have been a single developer over engineering a system because they thought it was cool, but we replaced it with a simple batch script.