Legacy Architecture Migration Patterns with DDD
summary
Shows concrete migration choices at PayFit: splits employee data across three legacy systems, migrates some features by moving writes first and others by publishing translated events, and spends 1.5 years stabilizing those events while wrestling with model mismatches and null-string quirks. Compares CDC vs events and outbox/batch syncs, and reports AI helps more with project orchestration than code — a git-backed markdown + YAML tool plus Claude/Anthropic and Datadog cuts current-state mapping from weeks to ~30 minutes.
AI-written summary · about
chapters (6)
- 0:00Legacy migration and AI
- 13:10Common migration patterns
- 27:39Payit’s employee migration case
- 44:45Contract migration patterns
- 52:59AI in project management
- 1:00:25Q&A
related talks
43mLegacy Architecture Migration Patterns
43mPatterns of Legacy Displacement
45mHitchhiker’s Guide for Software Architects: Legacy Migration
02mAtomic Migration Patterns
47mLegacy Software: Really a Problem?
44mLegacy Software Really a Problem
58mLegacy modernization made practical: A live coding example of modernization patterns
25mData-Driven Migration from Monoliths to Event-Driven Microservices
