Materialized views across services
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
build a local, query-friendly copy of another service's data and manage how stale it is.
Planned topics
- Consume events from the owner and keep only the fields you need.
- Staleness is a product decision: state the acceptable lag and show timestamps if needed.
- Handle missing or out-of-order events by versioning and periodic reconciliation.
- The owner stays the source of truth; the view is disposable.
Draft outline details
Demonstration
Shop order page view: order id, status, last carrier event and its time, built from ShipmentDispatched events; a nightly reconciliation compares counts with FulfillCo's API.
Check your understanding
Who owns the data in a materialized view?
Show answer
The source service; the view is a disposable copy.
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.