From twitter: https://twitter.com/mathiasverraes/status/1298665213978447873?s=20 Using collaborative modelling to build a shared understanding of your domain and use it to guide your design _is_ the philosophy behind DDD though. The rest is the principles, patterns, and practices. But perhaps just doing EventStorming does not actually make you a DDD'er, but what is? In today's panel, we will discuss with several people from the community what makes you a DDD'er? Joining us are: Emanuela Damiani Krisztina Hirth Mathias Verraes Jessica White Nick Tune
It’s like 10,000 streams when what you need is a queue – Chris Simon
🎶🎵 A new dev team adopted E-D-A Got head of line blocking, on their very first day Isn't it ironic, don't you think 🎶🎵 The last few years have seen widespread adoption of Event-Driven Architecture, supported by DDD practices...
