Domain-Driven Design is no silver bullet and does not solve any problem in magical ways. The challenges and complexity that we try to tackle with DDD are hard and there is no easy way out. Nevertheless there is a growing popularity and appreciation for the topic in the market which may lead to overly ambitious expectations and eventually to disgruntled expectations.
Michael has been working with DDD for the last 17 years on many software systems and this talk is about his experiences with failure. You can believe: He has failed a lot but there is always a chance to learn. The talk aims at giving you a chance to learn from the mistakes of him as a consultant and of the teams/organizations he has been working with.
The talk will address topics like:
– Domain-Driven Design in the waterfall
– Ignorance for code (aka only focus on strategic design)
– Overusage of patterns for their own sake
– Cultural implications
– Cargo Culting
– Developer Experience
– Rare availability of domain experts
– Dealing with established modeling techniques/methods
– Ignorance for the definitions/meaning of heuristics and patterns
It aims at providing you with a sensibility for potential hazards when you try to adopt DDD for your team and your organization and will contain only real-world scenarios that have actually happened. Each described failure will also come with a learning on what to do better. This will be an interactive talk during which you, the audience will be asked questions and polls (through an online tool).
Fellow at INNOQ.
Michael works as a Fellow for INNOQ in Germany. He has over 15 years of practical consulting experience in software development and architecture. His main areas of interest are Domain-driven Design, Microservices and, generally, Software Architecture. Michael is a regular speaker at national and international conferences.
