> mostly at the same time

Mostly? If you can update A one week and B the next week with no breakage in between, that seems pretty independent.

This was also the case for the micro-service situation described in the article. From the FA:

> Over time, the versions of these shared libraries began to diverge across the different destination codebases.

I don't see the problem?

There's at least one employee per micro service so there should be zero problems preventing just bumping the version of the library.

	▲	sethammons 2 hours ago \| parent [-]
		This Segment team was 3 people and 140 services. Microservices are best at solving org coordination issues where teams step on each other. This is a case of a team stepping on itself.