Problem
Paradox Shop needs its orders service and its fulfillment service to never read and write directly to the same database tables: if they shared a schema, neither team could change a column without coordinating with the other, and a migration on one side could break the other's queries in production. Design the data ownership boundary from scratch: exactly one service owns each database directly, and any other service that needs that data 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.