Problem
Paradox Shop's orders service and its fulfillment service both read and write directly to the same database tables, shown below as two separate service pools each wired straight into the one database. Neither team can change a column without coordinating with the other, and a botched migration from one side has twice broken the other's queries in production. Fix the data ownership boundary: exactly one service owns the database directly, and the other goes through the owner instead of touching its tables itself.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.