Governance Principles: Outcomes, DDD, Conway's Law

Building Evolutionary Architectures: Automated Software Governance - Rebecca Parsons

Topic 7 of 10

Published Jan 13, 2025 · Clip 29:55–39:43 (9:48)

Discussing governance, Parsons acknowledges governance is often a dirty word but is unavoidable at scale, and fitness functions add enormous value by automating checks so architectural reviews become unnecessary for rote concerns. Governance should focus on outcomes, not implementations, allowing delivery teams creative freedom within guardrails. She explains domain-driven design helps align system boundaries with business domain chunks, which she believes explains microservices' success over early SOA, whose boundaries were drawn around systems like SAP. She then covers Postel's Law (be generous in what you receive, stingy in what you produce) with an example of 87 reports tied to a database schema that blocked an upgrade, and Conway's Law: systems reflect the communication dysfunction of the organization, enabling the inverse Conway maneuver of reorganizing teams to shape architecture.