TrackFTS0062

Shared Database Coupling

Medium

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.

Current Production Metrics
Snapshot of the system before any changes.
Traffic
800 RPS
Monthly cost
$1,020

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.