Just published a new article 🤓 Some of my reflections on DDD, Event-Sourcing and Event-Driven Architecture. 👉Growing systems towards DDD, Event-Sourcing and Event-Driven architecture joebew42.github.io/2025/04/06/gro… #ddd #eventsourcing #eventdriven

Start simple: There is no need to start your system with DDD, Event-Sourcing, or Event-Driven. Consider to let the system grow as the needs become clear. #ddd #eventsouring #eventdriven joebew42.github.io/2025/04/06/gro…

Domain-Driven Design helps to better picture the business domain into your code. Particularly when things starts to grow. #ddd #eventsourcing #eventdriven joebew42.github.io/2025/04/06/gro…

Event-Sourcing is a persistence mechanism. It changes how you store and load the state, but it should not leak outside the repository or be coupled with other parts of your code. #DDD #EventSourcing #EventDriven Read more at: joebew42.github.io/2025/04/06/gro…

Looking for a curated, open, and ever-evolving learning path focused on practices of software development, software design principles, and software architecture? github.com/joebew42/study…

Event-Driven architecture helps with communication. It is about propagating changes and maintain systems decoupled each other. Not about persistence. #ddd #eventsourcing #eventdriven Read more at: joebew42.github.io/2025/04/06/gro…

Decoupling matters. Even if you are using Domain-Driven Design, Event-Sourcing and Event-Driven, they should be loosely coupled. A change in your event publishing strategy should not require changes to your domain model. #DDD #EventSourcing #EventDriven joebew42.github.io/2025/04/06/gro…

I recently read this article, which I highly recommend to organizations looking to adopt a culture of autonomous teams, decentralize and slim down decision process, and help teams grow, both technically and mentally. martinfowler.com/articles/scali…

The Application Service is your transactional boundary. It defines the atomic scope of a use case, ensuring all related changes happen together, or not at all. #DDD #EventStorming #EventDriven Read more at: joebew42.github.io/2025/04/06/gro…

It's been a while since my last updates on this Study Path on Software Development, finally I have some, updates out, check it out if curious: github.com/joebew42/study…

Software grow over time. You might start without DDD, Event-Sourcing, or Event-Driven architecture, and that is perfectly fine. As the system evolves, you may gradually find yourself in the need to refactor towards DDD, Event-Sourcing, or Event-Driven. joebew42.github.io/2025/04/06/gro…

Explore how software can grow from simple MVC Applications, toward Domain-driven Design, Event-Sourcing, and Event-Driven, in an incremental way. How these concepts can stay decoupled, and how Application Services defines transactional boundaries. joebew42.github.io/2025/04/06/gro…

I like to call this approach "Themed Group". A way to help organizations to react quickly to timely needs, without the risk to drain capacity from existing teams and at the same time, ensure the new initiative a clear ownership in any of the existing team. joebew42.github.io/2025/05/01/the…