Data ownership
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
give each service exclusive ownership of its data.
Planned topics
- Each service owns its tables or database; no other service reads or writes them.
- Others get data only through the owner's API or events.
- Shared databases create hidden coupling: a schema change breaks other teams.
- One owner per fact: for example stock levels belong to Inventory, prices to Catalog.
- Separate databases can start as separate schemas; enforce with separate credentials.
Draft outline details
Demonstration
a table: data item, owning service, how others read it.
Check your understanding
How may orders read stock levels?
Show answer
Through inventory's API or events, never its tables.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.