Domain teams want local data copies for autonomy, while the enterprise architecture board wants one centralized store for consistency. What is the sound response?
Select an answer to reveal the explanation.
Short Explanation
Autonomy and consistency pull like two dogs on one leash. Say the trade-off out loud, then add contracts, lineage, and shared definitions so neither side pretends the tension vanished.
Full Explanation
Architecture frequently balances team autonomy (local stores, faster delivery) against enterprise consistency (shared masters, uniform metrics). Explicit trade-off analysis documents chosen defaults and compensating controls—interface contracts, lineage, quality gates, and semantic alignment. Unexamined extremes either choke delivery or explode duplication and conflicting truth.