Where Form 2350 Uncertainty 2023-2024

Music, applause. Well, thank you very much. Thanks for taking your precious time to attend. Thank you to Aberhart for inviting me to speak at the go-to conference, a very first-class conference. So, what I'm going to talk about today is using DDD in our modern time. So, what is contemporary DDD like? Actually, this talk is meant to underwhelm you a bit because remember, I'm a champion of simplicity. So, whatever I'm going to say is going to be the simplest thing that could possibly work. And what I'm going to do is hopefully show you how to cut through a lot of the maybe misunderstandings or complexities, accidental or even purposeful complexities that you may use as you develop. So, what is domain-driven design about today? Actually, domain-driven design hasn't really changed since Eric Evans codified the patterns, what is it now, 14 years ago or something like that. The essence of domain-driven design is still modeling a ubiquitous language in a bounded context. What probably has changed is the way that a bounded context is rendered into production these days. If you look carefully at Eric's book and you sort of maybe even a little bit read between the lines, I think you can tell that Eric was not opposed at all to developing a monolith, but a well-structured, well-modularized, well-designed monolith. So potentially, you could actually have multiple bounded contexts within one single deployable unit. Of course, I'm not trying to read his mind, this is just my interpretation of his expressions back, you know, before the year 2003. So, bounded context, ubiquitous language, still the hallmark of domain-driven design. But because we have a bounded context, a boundary where we model a ubiquitous language, we will always have multiple bounded contexts. It's just because the scope of a...