Jump into my upcoming "Implementing #DDDesign Workshop" and learn the full range of strategic and tactical modeling, as well as additional patterns and tools to understand your domain, design multiple models, and implement.
Registration below. #domainDrivenDesign #DDD #EventStorming #EventDrivenArchitecture #PortsAndAdapters #HexagonalArchitecture
Change is hard. So, do we hang on to the past? After all, everybody else does.
That is, except for the rational people. Really. There's a not-so-fine-line between clinging to the past and doing what's necessary to move beyond.
Attend my "Implementing #DDDesign Workshop"
I have several thousands of tests across four productsβprobably close to 10,000. I have no more confidence in them than I had before #GenAI. Yes, they help.
1/2
Regardless of how you produce source code in 2026, how do you know that you are implementing the right thing on purpose? Going 10x-20x faster on the wrong things is wrong. Conventional approaches are completely backwards. Make #DDDesign your differentiator: 23-26 March
kalele.io/iddd-workshop/
I've been saying for at least 15 years that going all #DDDesign Trojan-Horse:
1. scares the horse
2. won't have troops to push it forward
3. will, if it is pushed, fall down and not get up
4. is unnecessary
REPEAT AFTER ME: Not everyone in our org structure is ADHD.
Connecting engineering effort directly to desired business outcomes can be a real struggle. Steve Pereira led a hands-on session, exploring how outcome mapping provides a clear path to align our efforts and improve flow. It helps make sure our work truly contributes to the impact we want.
Watch: https://virtualddd.com/sessions/outcome-mapping-for-flow-engineering-with-steve-pereira/
Begin with the end in mind - Stephen Covey 70% of transformation efforts fail, and they fail because they lack clarity. 8 people will have 8 understandings of problems and solutions. By breaking down a target outcome, we create clarity and converge. Outcome Mapping is the first activity in Flow Engineering, which arose out of the need for clarity before starting further mapping activities. Outcome Mapping has its own flow, from ideas and pains to methods, guiding you from desire to action. You can map outcomes whether you are starting, in the middle or in the home stretch. It's a great way to bring a group together to converge, and set off in the right direction as a team. In this session: Why outcome mapping is a critical activity You'll see how outcome mapping works How to create your own outcome map Outcome mapping outcomes :] I'll also share similar and complimentary techniques to provide many options for future exploration.
Join me for my upcoming @IDDDWorkshop, 23-26 March. It's four half days of advanced #DDDesign, both strategic and tactical design, Ports and Adapters, Event-Driven Architecture, #EventSourcing, and #CQRS, and a lot more.
See link for registration #DDD #DomainDrivenDesign
kalele.io/iddd-workshop/
Still, I absolutely must converse wellβmeaning thoroughly and preciselyβand I have to drive redesigns and refactorings. On the other hand, as a lead architect and #DDDesign participant, I'd share those efforts along with a team of mature developers anyway.
3/
It has been quite an odyssey, but now it is finally here. Let me introduce you to:
π£ π Domain-Driven Transformation: Modernize Legacy Systems and Mitigate Risk π π£
In this book, Carola Lilienthal and I present our approach to transform architecturally eroded systems at the strategic, tactical, and team-organizational level.
The relationship between problem and solution space is a complex, often debated topic in DDD. A panel with @dahukanna, @cyetain, Indi Young, and @nick_tune explored this and its connection to core, supportive, and generic subdomains.
A valuable discussion for anyone navigating these concepts. You can rewatch the session on our website, or listen to it as a podcast.
#DDDesign #ProblemSpace #SolutionSpace
https://virtualddd.com/sessions/relationships-between-problem-and-solution-space/
One of the more confusing concepts in Domain-Driven Desing is that of problem and solution space. There has been a long debate on Twitter and the ddd-crew github: https://github.com/ddd-crew/strategic-architecture-building-blocks/pulls?q=ispr+isclosed People wonder how distilling the Core with the Core, supportive and generic subdomains fit and what space. What concepts are in the problem space, and what is the solution? And what is a precise definition of problem and solution space? Join us in this session are a diverse group of people spanning multiple disciplines to look at how they see the relationship(s) between problem and solution space in IT. And hopefully, in the end, we can have a useful, consistent model of those relationships between problem and solution space, core, supportive, generics (sub)domains for the #DDDesign community. With us will be: Dawn N Ahukanna Jabe Bloom Indi Young Nick Tune
Vaughn Vernon π¦ π¨ π§ πͺ
Virtual Domain-Driven Design
Henning Schwentner