[wlll]

That's ~12 people per microservice. I understand that it might be hard to boot and coordinate all that on each developers machine, and that local docker images/vms/whatever might not suit you, but is it possible that this is a problem of your companies own creation?

[0xCMP]

It's very likely not their decisions that lead to this, but their responsibility to improve velocity.

Imagine the goal is to fix the problems (e.g. make it possible to run less of the services or something like that): How do you do that without first running all the services, making the proper changes, and then testing those changes? You need to be able to run all the services in that interim period.

So, wouldn't it be nice if there were a solution for this in-general? And, maybe, it would lead to better conditions later on. But in the meantime there is really no way around the existing design/decisions/etc. You simply have to deal with that reality and engineer around it.

[chipdart]

> How do you do that without first running all the services (...)

Why do you need to run all services in isolation to be able to troubleshoot and isolate a problem?

[0xCMP]

I think it's a fair to assume OP would have tried to run only some of the services and has seen or experienced problems with doing that.

[wlll]

> It's very likely not their decisions that lead to this

Yeah, I get that, I was deliberate about the phrasing of "your company" rather than just "your".

Obviously we don't know anything about the parent commenters company and situation, perhaps 12 people per microservice genuinely is the right solution for them, but it seems like it would be better not to get into this situation in the first place, though once there you obviously have to tackle the problem as it presents itself.

[0xCMP]

Agreed that it may be the right solution, but it smells bad. If I was there I would be trying to reduce the complexity where I could.