[geodel]

> One of the problems is that people assume that Microservices "should be as small as possible" when they should be "Small enough that a small team can own them"

I don't know what people should do. It is named as micro service after all.

It is same with Agile cult with endless sprints, stories, epics, sagas, daily scrums, scrum of scrums, scrum master of ceremonies, and what not, people are then told "Do what works in your situation, silly." I mean yeah, it is so simple and straightforward now why didn't everyone think of it before.

[MetaWhirledPeas]

I think the failure of most group processes is the leadership's failings. They need the wisdom and technical knowledge to make the right choices, the organizational skill to implement those choices, the authority to implement those choices, and the charisma to bring the team along with them.

I know a lot of people get mad and lash out at Agile in particular, but I don't think the alternative is any more straightforward. Group work is hard.

[corpMaverick]

> I don't know what people should do. It is named as micro service after all.

Totally agree.

They are "micro" only from the point of view of a company that has an application with millions of LOCs and thousands of developers working on it.