We are hosting a Domain Storytelling workshop with experts Stefan Hofer and Henning Schwentner on September 29-30!

This powerful method helps bridge the gap between domain experts and IT professionals by creating visual stories of business processes. In just two half-days, you'll learn to capture domain knowledge efficiently using simple pictograms.

Register now: https://ddd.academy/domain-storytelling/ to take advantage of the early bird

The Domain-Driven Transformation workshop addresses system evolution at three critical levels:

Strategic: Rediscover domains, model target architectures, and plan migration paths
Tactical: Apply proven refactoring patterns to move from anemic models to rich domain implementations
Socio-technical: Reorganize teams to align with domain boundaries and improve communication flows

Learn more: https://ddd.academy/domain-driven-transformation/

I've seen a lot of content about using #DDD (Domain-Driven Design) with #Ruby on #Rails, but none of it has addressed how to do the "one database per bounded context" pattern--especially in the world of Solid* and SQLite by default.

Does anybody have any strategies for this?

You’ve built clean #Java code with entities and services—yet the business still says “this isn’t what we needed.” @otaviojava reveals shows how #DomainDrivenDesign keeps your project connected to real goals, not just nice architecture.

Learn more: https://javapro.io/2025/07/01/mastering-the-basics-of-domain-driven-design-with-java/

I have just published my follow-up post:

>> Event Sourcing in PHP Symfony <<

It explains how anyone can implement event sourcing in a PHP Symfony project with minimal effort — free from ivory tower views.

Please let me know what you think of the post in the thread, and whether you found my naive implementation resonated with you.

https://lukasrotermund.de/posts/event-sourcing-in-php-symfony

Last chance! Get your #DDDEU 2025 tickets. Dive into the world of #DomainDrivenDesign with us.
Secure your ticket now https://ti.to/on3/aardling25

Ash Framework – Model your domain, derive the rest

https://ash-hq.org/

Slides from my presentation at #JAX
20 Years of #DomainDrivenDesign: What I’ve Learned About #DDD
https://speakerdeck.com/ewolff/20-years-of-domain-driven-design-what-ive-learned-about-ddd

«CoMo soll das Fachwissen aus den Köpfen der Fachleute in die Köpfe von Entwicklerinnen, Testerinnen, Product Ownern, Produktmanagern und Business-Analysten transportieren»

Collaborative Modeling: Software-Architektur mit den Stakeholdern gestalten | Developer https://www.heise.de/hintergrund/Collaborative-Modeling-Software-Architektur-mit-den-Stakeholdern-gestalten-10371860.html
#CollaborativeModeling #StakeholderEngagement #DomainDrivenDesign #RequirementsEngineering #CoMo #EventStorming #DomainStorytelling #ExampleMapping #UserStoryMapping #Teamwork #ProjectManagement #Projektmanagement

I will be leading a hands-on workshop at https://dddeurope.com on June 4th!

Implement core DDD concepts including Aggregates, Repositories, Value Objects, and use Hexagonal Architecture for loose coupling. In Java and Python.

Should authentication/authorisation be in your domain or application layer?

Spoiler, it depends.

#dotnet #ddd #domaindrivendesign

https://youtube.com/watch?v=0TpejBzN-xw&si=M4sd83OVGkqbmH4I

Legacy Systems = tightly coupled architectures hard to scale, change & maintain.

National Grid tackled this with 4 paradigms:
#DomainDrivenDesign
#TeamTopologies
#EventDrivenArchitecture
#ChangeDataCapture

Details in the #InfoQ article ⇨ https://bit.ly/44UplDs

Modelle statt Bounded Contexts? Eine Alternative für fachliche Modularisierung

https://tube.tchncs.de/w/gBkRZSS2Vhg6APbE2Ed7Km

MUC DEN

#exploreddd #domaindrivendesign

Slightly anxious about the border procedures, but looking forward to seeing all you awesome people again. Wish me luck!

Why pay more for less? My online #DDD workshop goes deeper, lasts longer, and costs less than a typical conference workshop—plus, you’re learning from the guy who wrote the book.

Join me on May 13–16

Price jumps Apr 21
kalele.io/training/iddd
#DDDesign
#DomainDrivenDesign

Electrifying Norway with F# and DDD

vimeo.com/1070647821

#fsharp #domainDrivenDesign #dev #dotnet

It should be recognized that reducing a team's cognitive load includes speaking the same language as the business in specific contexts.

The cognitive energy required to translate from business concepts to technical concepts, and technical concepts to business concepts, is enormous.

Do you need to reduce cognitive load? Start with a common language. #DDDesign #DDD #DomainDrivenDesign

Will AI untangle your Big Ball of Mud?

Can it identify your Bounded Contexts?

Can it architect your systems with clarity and purpose?

Not yet. But "Implementing Domain-Driven Design" (DDD) will.

Learning is essential—but applying that knowledge is what truly transforms your organization. Are you ready to put your knowledge to work?

Join me for hands-on learning to tackle complexity.

Register today.

https://kalele.io/iddd-workshop