Compliance as an architecture driver
On This Lesson 4 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
treat regulation as a design input from the start.
Planned topics
- Marketplace, payouts, and new countries bring privacy, payment, tax, and consumer rules.
- Late compliance fixes are expensive: data copies and flows are hard to find afterward.
- Compliance is a result of controls built into the system plus evidence that they work.
- Work with compliance partners; they define obligations, you design how to meet them.
Draft outline details
Demonstration
a table: obligation (verify with compliance), affected data and systems, architecture response, evidence produced.
Check your understanding
Who defines the obligation and who designs the response?
Show answer
Compliance and legal define it; engineering designs how to meet it and produce evidence.
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.