DDD & BDD Then and Now: Unpacking Similarities and Differences
summary
Two projects compare: a 20-year legacy invoicing monolith that is partly rewritten to reduce technical risk and a 2021 greenfield trading system built with event sourcing and per-UI read models. Both use DDD aggregates plus BDD scenarios as the shaping tool and automated tests; the legacy rewrite keeps heavy calculations inside aggregates while the new system pushes history and cross-cutting reactions into events and reactors, protected by anti-corruption layer. Result: modular monolith that is distribute ready.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:42Project backgrounds
- 7:25Domain modeling basics
- 15:14Event sourcing explained
- 24:01Behavior-driven development
- 36:36Modularization approaches
- 44:30Similarities and differences
- 48:44Q&A
related talks
24mFighting against technical debt with BDD, DevOps and Sustainability
48mBDD - It’s More Than Acceptance Tests
20mBDD: You’re doing it wrong!
16mBDD with cucumber.js
30m20 Years of BDD
51mDoes BDD Adds Additional Architectural Limitations on Solutions for Testing?
43mBDD vs TDD vs TDD vs TDD
32mTesting in Software Development Process: TDD And BDD