[sisve]

A microservice architecture is a good way to solve the problem with the monolith. The problem is the word mikro. It should have a better name. If it was called "boundary architecture" or similar it would make people stop creating to small pieces. One team should not manage 15 services.

[jamesfinlayson]

This - I worked with a guy that had been to a conference where someone from Atlassian said that S3 was made up of over 500 microservices, so this guy made it has mission to create as many microservices as possible in a 100 person company.

[tdeck]

I agree, the precise granularity of "micro" isn't well-defined and I've seen teams (usually ones without prior practical experience) try to implement an "every database table is a new service" approach that ends up being ridiculous. I suppose the term Service Oriented Architecture avoids this problem, but it sounds a little too "Oracle enterprise" for my taste.