DDD Europe 2025
| title | author | length |
|---|---|---|
| Domain driven redesign | Davy Landman | 47m |
A 40‑year‑old in‑house 4GL with ~100,000 forms and 30 million lines of code moves from a proprietary binary DB to a Git-friendly JSON layout by adding a driver… | ||
| DDD for Mergers and Acquisitions | Henning Schwentner | 43m |
Two decades‑old systems from Alporn Autoleasing and Cosmo Cars are compared, not by topic but by exact process: use collaborative modeling (eventstorming… | ||
| Breaking conventions for more performant models | Cyrille Martraire | 40m |
Argues that intentionally breaking domain conventions simplifies models and boosts performance, with concrete patterns: treat day boundaries as… | ||
| The Unbearable Weight of Architecture | David Whitney | 50m |
Argues that software complexity comes from surface area over size and that architecture must contain breadth not byte counts, using a real credit‑card platform… | ||
| Modernising in Healthcare: a case study in decision making | Leander Vanderbijl | 47m |
A healthcare monolith with PHP, Delphi and Java is migrated by doing a lift-and-shift then rewrite: EC2 hosts for immediate cloud delivery while a cloud-native… | ||
| Living Domain Model | Younès Zeriahi | 47m |
A team refactors a scattered, largely anemic domain model into a cohesive aggregate, uses Mikado technique and ensemble programming to safely delete a legacy… | ||
| DDD & BDD Then and Now: Unpacking Similarities and Differences | Anita Kvamme | 54m |
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… | ||
| Tobias Goeschel at DDD Europe 2025 | Tobias Goeschel | 01m |
Agents (conversational LLMs) enable rapid prototyping of domain logic by letting teams start an agent and interactively explore behavior when domain knowledge… | ||
| How to Train Your Domain Model | Tobias Goeschel | 50m |
Shows a one-day prototype that retrieves terms and products, generates a recommendation and verifies it with a second LLM (handles a Romanian dialect)… | ||
| Omphile Matheolane at DDD Europe 2025 | Omphile Matheolane | 02m |
Claims that a modular monolith runs as a single deployable unit while internally using feature-aligned modules that expose only defined interfaces or events… | ||
| Omphile Matheolane at DDD Europe 2025 | Omphile Matheolane | 02m |
Uses a bank example to show bounded contexts as separate modules — accounts, payments, loans, CRM — each with its own domain model and rules and deployed… | ||
| Omphile Matheolane speaking at DDD Europe | Omphile Matheolane | 01m |
Argues that a monolithic bank codebase becomes manageable by carving out accounts as its own bounded context and loans as its own bounded context, wiring them… | ||
| Omphile Matheolane speaking at DDD Europe 2025 | Omphile Matheolane | 01m |
Argues that the real problem with monoliths is not choosing them but the unmanaged complexity inside them and that teams confuse essential complexity (inherent… | ||
| Modular Monoliths: The Architecture That Scales w Your Domain | Omphile Matheolane | 43m |
Argues that a single deployable modular monolith scales with the domain by using DDD: explicit bounded contexts, aggregates as transactional roots, and… | ||
| Łukasz Reszke speaking at DDD Europe 2025 | Łukasz Reszke | 01m |
Covers two stories and one antipattern that cause practical trouble with aggregates, describes concrete problems encountered with aggregate boundaries and… | ||
| Łukasz Reszke speaking at DDD Europe | Łukasz Reszke | 02m |
Argues that adding one more if feels cheap but causes compounding conditionals that make files, classes and functions balloon; shows that tests’ arrange… | ||
| The Anatomy of Business Conditions | Łukasz Reszke | 50m |
Argues that many brittle systems come from feature-driven aggregates and scattered if statements, and shows concrete refactor steps using DDD, event sourcing… | ||
| Thomas Coopman at DDD Europe | Thomas Coopman | 01m |
Claims that Domain-Driven Design is not a standalone solution and only pays off when core engineering and org practices are present; recommends verifying… | ||
| Scaling Teams with Ownership | Thomas Coopman | 16m |
Company moves from 3→12 teams and ends up owning 40+ services, which explodes complexity and slows delivery. Workshops reveal feature teams touched many… | ||
| Andrew Harmel Law at DDD Europe 2025 | Andrew Harmel-Law | 01m |
Claims that humans are the source of variability and that that variability shows up as shifting requirements, mismatched mental models, and repeated… | ||
| Variability, The Second Hardest Problem ... | Andrew Harmel-Law | 49m |
Variability is inevitable and lives in the messy design “squiggle,” driven by choices of language, framework, platform, APIs and integrations, and it creates… | ||
| Through the Looking Glass | Dr. Jabe Bloom | 01h 02m |
Conway’s law becomes a dynamic claim: architecture and org structure undergo a continuous homomorphic fitness transformation with measurable drift and sudden… | ||
| Jabe Bloom at DDD Europe 2025 | Jabe Bloom | 01m |
Claims that the everyday doorway effect explains memory slips: walking into a new room triggers the brain to drop prior goals because context cues change. Uses… | ||
| John Phamvan at DDD Europe 2025 | John Phamvan | 01m |
A cross functional team modernizes parts of the US health‑care claims system that processes 4 million claims per night and runs on three million lines of… | ||
| John Phamvan at DDD Europe 2025 | John Phamvan | 01m |
Domain-Driven Design creates a shared understanding via ubiquitous language and drives decomposition of a government agency monolith into… | ||
| DDD Surrounded by Legacy, Govt Edition | John Phamvan | 55m |
A cross-functional team prototypes a cloud adjudication path that processes four million claims per night without touching the legacy core of three million… | ||
| Alberto Brandolini at DDD Europe 2025 | Alberto Brandolini | 01m |
Core claim: stop expecting certainty and avoid waiting for precise requirements or a fixed roadmap because by the time they exist it's already too late… | ||
| Alberto Brandolini at DDD Europe 2025 | Alberto Brandolini | 01m |
Explains how modeling with many models shifts from fast, isolated iterations in a small team into coordination overhead in a growing team and compliance… | ||
| Growing and Thriving in a Multi Model World | Alberto Brandolini | 53m |
Small teams keep a small beautiful model by enforcing visible context maps and a 7-step recipe (visualize problem, list alternatives, highlight scenarios, pick… | ||
| Barry O'Reilly at DDD Europe 2025 | Barry O'Reilly | 01m |
Argues that architecture should prioritize model drift and software attractors instead of classic pillars like coupling and cohesion, defines model drift as… | ||
| Barry O'Reilly at DDD Europe 2025 | Barry O'Reilly | 01m |
Argues that model drift—the gap between the mental/domain model and the implemented code—drives regressions and slows delivery, and demonstrates a lightweight… | ||
| Model Drift and Software Attractors | Barry O'Reilly | 39m |
Argues that architecture is emergent: business model drift forces software into a handful of software attractors, so up‑front optimization for cohesion or… | ||
| Eric Evans speaking at DDD Europe 2025 | Eric Evans | 01m |
A personal account of an AI learning journey that organizes months of study into three categories and notes hands-on time with AI development tools without… | ||
| Eric Evans at DDD Europe 2025 | Eric Evans | 01m |
A personal account of an ongoing AI learning journey that outlines what was studied, the three categories used to structure those studies and practical… | ||
| My AI Learning Journey | Eric Evans | 56m |
Built a prototype Domain Navigator that queries LLMs via API to label code and finds reliability improves when responses are forced into a known taxonomy… | ||
| The power of diverse teams | Samantha Dellaert | 10m |
Teams that share the same background miss practical blind spots; concrete failures include face recognition failing for non‑white people, a signup form that… | ||
| Lightening Talk about the power of diverse teams | Samantha Dallaert | 01m |
A facial‑recognition system is built by feeding many pictures into a machine‑learning pipeline that creates a neural map trained on a homogeneous dataset, and… | ||
| Lightning talk about Event Modelling | Tom de Vroomen | 01m |
Shows event modelling by wiring a UIUX sketch to produce a concrete ShipVisitDeclared event, demonstrating how a minimal form maps to an event payload… | ||
| Event Modelling | Tom de Vroomen | 11m |
Event modeling is a compact workflow of five elements — command, event, read model, gear, UX/UI — and seven steps that turn sticky-note brainstorms into a… | ||
| Mike Wojtyna's Lightning talk about Domain Archetypes at DDD Europe | Mike Wojtyna | 01m |
Claims a repeatable method to produce strategic context boundaries and context maps by applying business-model heuristics and a layer of psychological personal… | ||
| Domain Archetypes | Mike Wojtyna | 12m |
Claims a lightweight method called the archetypes funnel that maps business models to strategic context maps using heuristics and two artifacts: the Product… | ||
| Martin Durmeier's Lightning talk about Obsidian at DDD Europe | Martin Durmeier | 01m |
Uses Obsidian for long term knowledge management and structured notes, but prefers a small paper Dina 7 pocket notebook for quick thoughts and meeting agendas… | ||
| Obsidian | Martin Dürrmeier | 12m |
Obsidian serves as a long‑term thinking vault built from plain Markdown files: a home note links to an inbox and a daily note, a DataView.js script shows five… | ||
| Mark Richards at DDD Europe | Mark Richards | 02m |
Argues that copying a monolith across servers just duplicates capacity limits and blocks growth, using a glass-and-water demo that shows state filling CPU… | ||
| Mark Richards at DDD Europe | Mark Richards | 01m |
Defines modularity = partitioning of systems into parts and granularity = size of those parts, then argues the central claim: modularity helps but incorrect… | ||
| Mark Richards at DDD Europe | Mark Richards | 02m |
Argues that a single VM or server hits resource limits as traffic grows, showing with a glass and water demo that duplicating the VM just duplicates the… | ||
| Realizing Domain Design Through Architectural Modularity ... | Mark Richards | 49m |
Argues that domains must map to architectural modules and that service granularity is justified by measurable trade-offs, not handwaving. Demonstrates five… | ||
| Chris Richardson at DDD Europe 2025 | Chris Richardson | 01m |
Argues that microservices and Team Topologies form a synergistic two-way relationship that still works: microservice architecture creates clear, deployable… | ||
| Team topologies and the microservice architecture | Chris Richardson | 49m |
Argues that fast flow requires loose design‑time coupling and a fast automated pipeline; microservices scale teams of about five to nine by giving each service… | ||
| Mike Wojtynac at DDD Europe 2025 | Mike Wojtynac | 01m |
Claim: inviting business people to design-level storming already loses them because sessions are too high level of detail, leaving mostly engineers and tax… | ||
| Mike Wojtynac at DDD Europe 2025 | Mike Wojtynac | 01m |
Combines domain experiments with example mapping, mob programming and test-driven development to surface where bounded contexts should sit and which rules are… | ||
| Mike Wojtynac at DDD Europe 2025 | Mike Wojtynac | 02m |
Prototypes cost time and hide domain depth; after a couple of years of daily practice the claim is to stop building full UI mocks and instead run domain model… | ||
| Domain Experiments | Mike Wojtyna | 41m |
Argues for running rapid experiments directly on the domain model by combining example mapping, mob programming (3–4 engineers sweet spot) and… | ||
| "I ran the code for you and I think the problem is X" ... | Chelsea Troy | 01m |
A large language model outputs I ran the code for you while no execution happens because there is no compiler or VM generated, only token prediction. The model… | ||
| The model can give a sequence of outputs that resemble an answer .. | Chelsea Troy | 01m |
Claims that modern generative models take a sequence of inputs and produce a sequence of outputs that resemble an answer while often lacking grounding, shows… | ||
| Evaluating Patterns in Gen AI Outputs | Chelsea Troy | 46m |
Shows why LLMs fail on tiny factual tasks (the strawberry gate counting bug) and why context matters: trained on Common Crawl-like text, transformers use… | ||
| on the C4 model | Simon Brown | 01m |
C4 evolves from hands‑on teaching to over 200+ clients across 40 countries, offering concrete rules for when to use component versus container diagrams, how to… | ||
| The C4 model: misconceptions, misuses and mistakes | Simon Brown | 51m |
C4 defines four abstractions — system, container, component, code — and claims that the real value is the shared vocabulary rather than diagrams alone; common… | ||
| We have learned how to design a modernisation facory | Fabrice Bernhard | 01m |
Describes a working pipeline that turns legacy code slices into validated modern slices by identifying atomic migration patterns, mapping them to target… | ||
| Atomic Migration Patterns | Fabrice Bernhard | 02m |
Describes atomic migration patterns as reusable steps that map a legacy vertical slice to a target architecture, then implements them with automated… | ||
| Migrating an app from native to React-Native 3x faster using AI | Fabrice Bernhard | 01m |
Claims a migration runs three times faster by using prompts that execute scripts across the codebase to produce a JSON dependency dump, then create a… | ||
| AI accelerated legacy modernisation | Fabrice Bernhard | 43m |
Claims AI-driven transpilation and automation cut migration effort roughly 4x speedup in practice by iterating prompts and agents; concrete pipeline builds a… | ||
| Software doesn't tolerate ambiguity | Xin Yao, John Cutler | 01m |
Argues that collaborative working sessions combined with meaningful inquiry and storytelling and sense making become practical modelling tools rather than… | ||
| Modelling Stories of the Beautiful Mess | Xin Yao, John Cutler | 02m |
Argues that organizational complexity is a “beautiful mess” to navigate rather than a problem to eliminate, and gives concrete practices: build individual… | ||
| Modelling Stories of the Beautiful Mess | Xin Yao, John Cutler | 02m |
Argues that true change is not disruption but transformation as reconstitution and that futures must be present in the room now, not implemented later from a… | ||
| If I could just ... | John Cutler | 02m |
Claim: stop chasing perfect visualization and alignment and instead pick a few concrete levers to reduce entropy. It recommends three moves: hold constants… | ||
| Software doesn't tolerate ambiguity | Xin Yao, John Cutler | 01m |
Claim: software doesn't tolerate ambiguity and Domain-Driven Design techniques are the way to make messy human communication executable. Shows how turning… | ||
| Modelling Stories of the Beautiful Mess | Xin Yao, John Cutler | 59m |
Claim: treat complexity as a navigable, generative “beautiful mess” by modeling conversations and belonging before collaboration, not by imposing fixed… | ||
| Model Tension Heuristics | Julien Topçu, Josian Chevalier | 50m |
Argues that lingering design debt shows as concrete, named tensions — spork effect, model fragmentation, model sclerosis — and gives heuristics to find them in… | ||
| Prem Chandrasekaran at DDD Europe 2025 | Prem Chandrasekaran | 01m |
A corporate memo mandates an enterprise party model that claims to unify identities but defines a single party object with 275 attributes, including date of… | ||
| Prem Chandrasekaran at DDD Europe 2025 | Prem Chandrasekaran | 01m |
Compares three decomposition patterns: one-to-one mapping where a subdomain neatly matches a bounded context, multiple bounded contexts when a subdomain splits… | ||
| Prem Chandrasekaran at DDD Europe 2025 | Prem Chandrasekaran | 01m |
DDD is framed as a Superman that will turn a big ball of yarn into neat strands, and the talk calls out that this metaphor hides real tradeoffs: mismatched… | ||
| Charting the uncharted: Discovering and evolving bounded contexts | Prem Chandrasekaran | 55m |
Argues that bounded context boundaries are often an art not a science and that real progress comes from specific practices: forge a ubiquitous language, draw… | ||
| Chris Simon at DDD Europe 2025 | Chris Simon | 01m |
Characterizes confusion using Peter Now's concept as the absence of a theory of a system or an incomplete or inaccurate theory that breaks reasoning about… | ||
| Chris Simon at DDD Europe 2025 | Chris Simon | 01m |
Argues that defending technical excellence means actively protecting internal quality by surfacing the informal theory developers hold about the system and… | ||
| Chris Simon at DDD Europe 2025 | Chris Simon | 01m |
The talk maps how combining a new croft reinforcing feedback loop with low impact bugs and high impact bugs feedback loops creates a system where the… | ||
| A Defence of Technical Excellence | Chris Simon | 41m |
Claim: the usual good fast cheap, pick two trade-off is a fallacy for software because hidden reinforcing feedback loops (bugs + technical debt → confusion →… | ||
| Dorra Bartaguiz at DDD Europe 2025 | Dorra Bartaguiz | 01m |
Reports systematic use of a feature flag for every user story, recounts client projects where flags are added by habit rather than necessity, and shows that… | ||
| Improving feature flag implementation to achieve flow | Dorra Bartaguiz | 41m |
Feature flags are often misapplied and create invasive if/else clutter, hidden dependencies and extra on/off test permutations; a French survey finds 29% of… | ||
| Kyle Kotowick at DDD Europe 2025 | Kyle Kotowick | 01m |
Management suppresses safety issues and shove that under the rug, even penalizing engineers—docked your pay from bonuses—for persistent reporting. Reported… | ||
| Kyle Kotowick at DDD Europe 2025 | Kyle Kotowick | 01m |
An internal FAA risk analysis completed a month after the Lion Air crash and before the second crash estimates one crash every three years across the Max… | ||
| The Boeing 737 MAX: When Humans and Technology Don't Mix | Kyle Kotowick | 51m |
Detailed timeline traces design choices: Boeing fits larger high-bypass engines forward on an old 737 airframe, introduces MCAS that reads one faulty angle of… | ||
| Jacqui Reed at DDD Europe 2025 | Jacqui Reed | 01m |
Diagrams with boxes and colors often fail because lines lack meaning and arrows are missing, so people cannot recall or explain them. The concrete remedy is to… | ||
| Jacqui Reed at DDD Europe 2025 | Jacqui Reed | 01m |
A live demo applies color-vision filters — a simulated protanopia round and a simulated tritanopia round — to eight chili images where only one chili is… | ||
| Jacqui Reed at DDD Europe 2025 | Jacqui Reed | 01m |
Argument: color in diagrams must carry explicit meaning otherwise it adds noise not value. Demonstrates a slide with six meaningless colors and claims the… | ||
| Design Patterns for Software Diagramming | Jacqui Read | 50m |
Explains concrete patterns and anti‑patterns: use meta style to signal draft vs finished, avoid mixing abstraction levels (C4 context → container → component)… | ||
| Platform Engineering is Domain Driven Design | Gregor Hohpe | 01m |
Argues that developer platforms succeed only when they expose a domain-specific language that hides infrastructure detail and composes into automation. Shows… | ||
| Platform Engineering is Domain Driven Design | Gregor Hohpe | 48m |
Argues that platform engineering equals Domain-Driven Design: build a domain-specific language that maps to cloud automation, reference architectures and… | ||
| Talks and labs to look forward to ... | 01m | |
While we are working on the schedule of Domain-Driven Design Europe, here are some talks and labs we look forward to.
See you at the conference… | ||
| nothing matches | ||