Building scalable systems in a complex compliance world
summary
Shows concrete patterns that work: state machines and shared compliance libraries model multi-step onboarding and reuse salary or payroll rules across services, using tools like Temporal Camunda Spring State Machine and npm/maven artifacts. Presents a decision matrix for when to pick each pattern, reports Personio experience that reduced international expansion from months to weeks, and explains tradeoffs, test and versioning strategies, and when duplication or service-specific logic still wins.
AI-written summary · about
chapters (8)
- 0:00Scalable compliance systems
- 1:03Speaker background and compliance challenges
- 3:13Compliance complexity early
- 6:42State machines for workflows
- 13:03Compliance libraries
- 16:57Compliance design patterns
- 19:26Compliance implementation keys
- 20:50Key takeaways and next steps for compliance
related talks
18mDesign Patterns For Efficient DevOps Processes
37mCompliance & Regulatory Standards Are NOT Incompatible with Modern Development..
30mBuilding a Cloud-Native Compliance Culture - CeeCee O'Connor (Boston Scientific), Chuck D'Antonio
05mHow To Automate Compliance If You Aren't Chuck Norris
33mCompliance as Code - Lessons Learned From Regulated Organizations
18mTurning Policies, Standards, and Governance Into Enablers for Open-Source Innovation
36mApplication Architecture Patterns
29mAutomating Continuous Compliance for Scalable SaaS Delivery