Design Time Coupling and Shared Libraries

#53 - Principles for Adopting Microservices Successfully - Chris Richardson

Topic 7 of 10

Published Aug 30, 2021 · Clip 26:40–33:24 (6:44)

Chris defines design-time coupling as the likelihood two modules must change in lockstep, and why minimizing it matters: cross-team changes require meetings, coordination, and aligned priorities. ThoughtWorks found cross-team decision-making takes 10 times longer than within a team. He discusses shared libraries: utility libraries with independent versioning are fine, but shared business-logic libraries force lockstep upgrades and can create the distributed monolith anti-pattern (citing Segment's failed microservices adoption). Lockstep changes are an architectural smell indicating a needed refactoring.