Joe Bew

Currently working as a Software Engineer with focus on agile practices, software design principles, and processes of software development.

[Joe Bew @joebew42]

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.
https://t.co/xsBLviuccP

[Joe Bew @joebew42]

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.

https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

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.

https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

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: https://t.co/yZMqKie06F

[Joe Bew @joebew42]

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: https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

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.
https://t.co/fawlPyqAQw

[Joe Bew @joebew42]

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

https://t.co/X9vDZcwGQk

[Joe Bew @joebew42]

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: https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

Looking for a curated, open, and ever-evolving learning path focused on practices of software development, software design principles, and software architecture?

https://t.co/yZMqKie06F

[Joe Bew @joebew42]

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: https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

Domain-Driven Design helps to better picture the business domain into your code. Particularly when things starts to grow.

#ddd #eventsourcing #eventdriven

https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

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

https://t.co/VBmKlBNhZ6

[Joe Bew @joebew42]

@jdecool Thanks for sharing 😃

[Joe Bew @joebew42]

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 https://t.co/VBmKlBNhZ6

#ddd #eventsourcing #eventdriven