Demo: replacing a nightly stock file with near-real-time CDC
On This Lesson 3 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
redesign one interface step by step and prove the benefit with numbers.
Draft outline details
Step by step
- State the problem: the nightly ERP stock file means the web shop oversells items sold in stores during the day.
- Quantify: count oversold orders per week and the cost of cancellations, with the business owner.
- Design: capture stock-table changes in the ERP database, publish stock-changed events, and update the platform's stock cache; keep the nightly file as a reconciliation check.
- Planned mistake: publish raw table-row changes as events. Fix: add a translator that emits a business event (StockChanged: item, location, quantity) so consumers do not depend on ERP columns.
- Plan failure modes: lag alarm, replay from the log position, and a fallback to the nightly file.
- Agree success measures with the store-ops lead: oversells down, lag under the agreed seconds, reconciliation differences near zero.
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.