Ownership and event catalogs
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
make every event findable and owned.
Planned topics
- One owning team per event type; the owner approves changes.
- A catalog lists name, owner, purpose, schema, topic, retention, sensitivity, and consumers.
- Naming follows business language and past tense.
- Catalog entries are reviewed like code, kept in a repository.
Draft outline details
Demonstration
an event catalog YAML entry: name ShipmentDispatched, owner FulfillCo-shipping, topic, schema ref, contains personal data: yes, replay-safe: no.
Check your understanding
Who owns an event type?
Show answer
The publishing team that produces the business fact.
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.