Demo: an anti-corruption layer around a carrier API
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
decide whether and how to isolate a carrier integration; prepares SRA-003-LAB1.
Draft outline details
Step by step
- Review the carrier API: statuses, error codes, rate limits, and its change history.
- Name the domain concepts we own: shipment, delivery attempt, delivery exception.
- Design the ACL: a domain-facing interface, a translator, and contract tests against the carrier sandbox.
- Decide the ownership and cost: who maintains it and how a second carrier would plug in.
- Planned mistake: pass carrier status strings straight into domain code. Fix: translate at the boundary and test the mapping, including unknown statuses.
- Record the decision in the context map as a conformist relationship softened by an ACL.
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.