Demo: Larkspur's integration landscape, interface by interface
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
build the interface catalog and target diagram. Prepares ARC-009-LAB1.
Draft outline details
Step by step
- List systems: web and mobile front ends, commerce platform, ERP, CRM, payment provider, store POS and handhelds, carriers.
- Enumerate interfaces: direction, data, volume, latency need, owner.
- Choose a style per interface with justification: payments synchronous API; orders to ERP as events with ERP adapter; carriers via API with polling fallback; store sales via batch.
- Define failure handling for each.
- Planned mistake: every interface is designed as a synchronous API because "APIs are modern". Fix: re-check latency and volume needs and apply batch or events where fit.
- Draw the target integration diagram and verify the ERP's real API limits before committing.
Check your understanding
What decides the style for an interface?
Show answer
Latency, volume, coupling, ownership, and the capabilities of the systems.
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.