Why should you care?

ShopNest Catalog and Orders can evolve schemas and deploy independently.

See it live — copy this example

Paste into a C# console or class library project and run dotnet run.

// OrdersDb <- only OrderService
// CatalogDb <- only CatalogService
// Need product name in order email? call Catalog API or denormalize on write
Console.WriteLine("OrderService SELECT * FROM OrdersDb.Orders");
Console.WriteLine("NO: OrderService SELECT CatalogDb.Products");

What happened?

• Data ownership enables autonomy.
• Cross-service data goes through APIs/events.
• Duplication is sometimes intentional.

Practice next

1. Assign ShopNest DBs per service.
2. Remove cross-db joins from code reviews.
3. Publish product snapshot on order if needed.
4. List foreign data OrderService needs.
5. Choose API vs event denormalization.

Remember

Own your data store. Integrate via API/events. Autonomy over shared SQL.

ShopNest isolated order DB

Orders schema changes without Catalog deploys.

Outcome: Teams ship on separate clocks.