DDD & Event Sourcing to the Rescue for Implementing the GDPR?
summary
Introduces the GDPR’s key requirements — explicit consent, data portability, anonymization/pseudonymization, retention periods — and other standards for compliance. Shows how applying Domain-Driven Design and Event Sourcing patterns can help information systems handle the major changes imposed by GDPR.
AI-written summary · about
chapters (6)
- 0:00Start
- 13:13GDPR and the Company: The Needs
- 23:04Domain-Driven Design
- 24:52Exploring Our Business Domain: Event Storming
- 28:14Cleaning the Core Domain: Example
- 46:53Questions?
related talks
42mDesign Principles for an Event-Driven Architecture
58mIntroduction to Event Sourcing
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
56mAn Abridged Guide to Event Sourcing
42mThe Only Thing That Matters
39mThe Promise of Event Driven Programming with Fast Data
46mState or events? Which shall I keep?
22mGovernance of event-driven distributed systems