Demo: choosing a style for each Larkspur 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
walk the interface list and choose a style for each, with reasons; prepares ARC-024-LAB1.
Draft outline details
Step by step
- List interfaces from the context diagram: ERP, CRM, payment gateway, carriers, stores, marketing platform.
- For each, write the latency need, volume, and what happens if it is down.
- Choose: payment authorization as a synchronous API; order and stock changes as events; finance posting as nightly batch; carrier labels as API with a file fallback; marketing audiences as a daily file.
- Planned mistake: choose real-time events for the marketing export "to be modern". Fix: show that the campaign tool refreshes once a day, so a daily file costs less and is easier to reconcile.
- Add owner, frequency, volume, and SLA columns; flag interfaces with no owner.
- Present three decisions and their trade-offs to a role-played integration lead.
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.