Canonical models: when and when not
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
decide when a shared data model helps.
Planned topics
- Canonical model: one agreed format for a business concept (order, customer) used between many systems.
- Helps when many systems exchange the same entity and you want N-to-one instead of N-to-N mappings.
- Hurts when it becomes a slow, committee-owned lowest common denominator.
- Use it for a few stable core entities; otherwise map pairwise with clear contracts.
Draft outline details
Demonstration
for Larkspur: canonical Order and Customer events for the platform; pairwise mapping for the carrier API, owned by an adapter.
Check your understanding
What is a sign a canonical model has gone wrong?
Show answer
It is slow to change, owned by a committee, and satisfies nobody.
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.