Integrating systems you can't change
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
choose integration approaches when legacy code is off limits.
Planned topics
- Options: database triggers, polling, file exports, API wrappers, and log-based CDC.
- Constraints: no code changes, load on the legacy database, data ownership.
- Pick the least invasive approach that meets latency needs.
- Always keep a path to reconcile.
Draft outline details
Demonstration
a comparison table of polling, triggers, and log-based CDC with latency, load, risk, and the need to change legacy code.
Check your understanding
Why prefer CDC for legacy databases?
Show answer
It reads the log without changing application code.
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.