Is there a process for figuring out how to do microservices “correctly” by your definition? It seems incredibly difficult to stay correct while requirements are being added.
I think most companies do this pretty well when deciding what projects different teams are responsible for. Those are usually pretty good business joints to cleave the domain.
People just lose their mind when you say the microservice.
Yeah - start with a monolith as Martin Fowler (the guy who popularized microservices) suggests. Split out services as you understand more about how the business is developing and stabilising.
So basically don’t do micro services unless there is a real need :-). I am on board with that but I am old and don’t understand how modern software gets done.
The fact that people like Prof. Leymann are writing whitepapers on how to do microservice "incorrectly" the best way, speaks to this.