A project proposes a new “integration database” so every department can dump and query shared tables freely, with no named owner or quality controls. What is the main architecture risk?
Select an answer to reveal the explanation.
Short Explanation
A communal drawer with no name on it turns into a junk drawer fast. Without ownership and quality rules, that “integration database” becomes accidental architecture nobody trusts.
Full Explanation
Ownerless integration databases are a classic anti-pattern: many writers, unclear stewards, weak quality rules, and ambiguous system-of-record status. They accumulate conflicting schemas and silent dependencies that break consumers during change. Sound architecture requires ownership, interface contracts, and quality controls—or intentional mediated patterns—rather than an unmanaged shared dump.