Capstone: Integration Delivery
12 hours · 5 preparation lessons
Deliver an end-to-end integration with reconciliation, error reporting, and a runbook, against a deliberately messy two-source scenario.
Read the scenario
A mid-size distributor, Meridyen Logistics (fictional), receives purchase orders through two channels: an EDI feed that delivers JSON with occasional duplicate event IDs, and a supplier portal exporting CSV weekly with inconsistent column headers and timezone-naive timestamps. Order volume is 900 per week, with a 1.5 percent duplicate or malformed rate observed in the EDI feed.
Your job: design and implement (against fixtures you create from this description) a sync service that loads both channels into one canonical order model, deduplicates, quarantines failures, and produces an honest weekly report the operations team can read. The scenario is fictional; the engineering bar is real.
Deliverables
- Design document: canonical model, sync strategy, dedup and quarantine design
- Working code (language of your choice) with fixtures for both sources and the malformed cases
- Test suite covering dedup, quarantine, and the ambiguous 'write may have landed' case
- Weekly report template populated with plausible numbers labeled fictional
- Runbook: top three symptoms with checks and actions
Self-review rubric
| Canonical model is explicit and both mappers are complete | %15 |
| Idempotency and dedup are correct under at-least-once delivery | %20 |
| Quarantine preserves payloads and supports reprocessing | %15 |
| Report is honest: numbers reconcile with the fixture data | %15 |
| Tests cover the failure cases, not just the happy path | %20 |
| Runbook is runnable by someone who did not write the code | %15 |
The whole scenario, including company names, is fictional.