Demo: an anti-corruption layer between the platform and the ERP
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 a worked design of an ACL that keeps ERP models out of the platform; prepares ARC-032-LAB1.
Draft outline details
Step by step
- Show the ERP's model: item master with 40 fields, cryptic status codes, customer and ship-to as separate entities.
- Define the platform's own domain model: Product, Price, Availability, Order.
- Design the ACL: translator mapping ERP structures to domain objects, status code dictionary, error translation, and a stable internal contract.
- Planned mistake: reuse the ERP's field names and status codes directly in the platform API. Fix: translate at the boundary so an ERP upgrade changes one adapter only.
- Add contract tests against the adapter and monitoring of translation failures.
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.