Coupling, latency, and failure
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
compare the styles on coupling, latency, and what happens when the other side is down.
Planned topics
- Temporal coupling: with a synchronous call both systems must be up at the same moment.
- Data coupling: a shared file format or event schema ties both sides to the same fields.
- Latency range: API in milliseconds, events in seconds, batch in hours.
- Failure: a down API fails the caller now; a down consumer of events catches up later; a failed batch leaves yesterday's data in use.
Draft outline details
Demonstration
a table of styles against "if the other side is down for one hour", with Larkspur results (checkout cannot price; stock events queue; nightly file waits).
Check your understanding
Which style survives an ERP outage best for stock updates?
Show answer
Asynchronous events or batch, since they queue and catch up.
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.