๐ฏ ๐๐ฅ๐จ๐, ๐๐๐ฒ๐ป๐ ๐ฆ๐ผ๐๐ฟ๐ฐ๐ถ๐ป๐ด & ๐๐๐ โ ๐ช๐ต๐ ๐ช๐ฒ ๐ ๐ถ๐๐๐ป๐ฑ๐ฒ๐ฟ๐๐๐ฎ๐ป๐ฑ ๐ข๐๐ฟ ๐๐ผ๐บ๐ฎ๐ถ๐ป | ๐๐ป๐๐ฒ๐ฟ๐๐ถ๐ฒ๐ ๐๐ถ๐๐ต ๐๐ผ๐น๐ผ ๐ฅ๐ผ๐ฑ๐ฒ๐ป
Is your architecture really the problemโฆ or is it communication? ๐ค In this #SAG2025 expert interview, Golo Roden dives into the trade-offs between #CRUD, #EventSourcing, and #DomainDrivenDesign โ and reveals why many teams struggle not because of technology, but because they donโt truly understand their domain.
Watch the full interview ๐ https://youtu.be/mOtoo-SFxfg
Another stream, another set of notes. So much "new"!
I try out a new design for Projectors, splitting EventConsumer into two pieces. Test-driving shows how it's about design exploration, not just writing tests.
https://ted.dev/articles/2026/04/06/live-coding-journal-apr-6-2026/
Notes from my #Java #EventSourcing work, where I looked at event consumers that only get events they're interested in.
Struggled with Java's MethodHandle (docs could be better!), but otherwise works well.
Thoughts about Projector design.
Read more at: https://ted.dev/articles/2026/04/02/live-coding-journal-apr-2-2026/
Making read models truly expressive from event streams isn't always straightforward. In this live coding talk with @mathiasverraes and @ericevans, we explored techniques for building expressive projections. The key takeaway was seeing practical ways to transform complex events into clear, domain-aligned read models.
Watch: https://virtualddd.com/sessions/ddddd-20-live-coding-expressive-projections/
Letโs write some event sourced projections! Our weapons of choice include higher order functions, algebraic data types, pattern matching, all the goodies of a modern programming languages. But the secret behind our success will be our Dogged Determination to Descriptive naming. Weโll observe how our domain language crystallises, how patterns emerge, and how we end up with code that communicates intent.
We started using event sourcing over ten years ago. One of the hardest lessons was that there is a kind of events that is not obvious at first but have a big impact on your system design. I call this kind secondary domain events.
https://www.planetgeek.ch/2026/04/01/the-problem-with-secondary-domain-events-in-event-sourcing/
We started using event sourcing over ten years ago. One of the hardest lessons was that there is a kind of events that is not obvious at first but have a big impact on your system design. I call this kind secondary domain events. In this post, I'll explain what secondary domain events are, and...
patchlevel
SoftwareArchitecture Gathering
Ted M. Young
Virtual Domain-Driven Design
Urs Enzler