I often compare choreography- (reactive systems) and orchestration-based microservices integration to soccer team dynamics. In soccer, a coach can instruct each player on what to do next, but this approach could be more efficient. The team's capacity will be determined and, in a

Certainly, relational normalization is one of the least efficient ways to read data.

In addition to the significant improvements in scalability, resilience, and process distribution, what I really appreciate about using a message broker (with a robust message bus) over the "in-process" Mediator pattern is the design cohesion. There's no need to distinguish

When did the "development environment" become the "cloud development environment"? Vendor lock-in without local support should be a crime. Note: It's a rhetorical question.

One implementation, many flavors #csharp #dotnet

This is a well-documented example of how NOT to apply #EventDriven principles to a system: medium.com/@shiiyan/how-i… Interestingly, I recently shared this with one of our teams: "#EventDrivenArchitecture (EDA) isn't just a tool to lift and shift your transactional code. EDA is a

"Skinny/Thin/Notification" Events and Reactivity "Skinny" (or thin/notification) events—those with minimal payloads, often just a single identifier—contradict the principles of reactivity by introducing temporal dependencies. This forces the consuming system to either "wait" or

A poorly decomposed system introduces more challenges than it solves: Higher Latency: Frequent network calls between tightly coupled services. Complexity: Increased operational overhead to manage communication failures. Inefficiency: Recreating monolithic dependencies across a

1/10 Truths in Distributed Systems Design applied to Reactive DDD: "It’s Never Just Two Boxes and a Line!" This truth highlights the risk of oversimplifying the complexity of distributed systems. Emergent behaviors are inevitable in such systems, making principles like

2/10 Truths in Distributed Systems Design applied to Reactive DDD: "The best way to make systems loosely coupled is by not connecting them." Favor event-driven communication between bounded contexts instead of direct API calls. Choreography-based systems—where events flow

3/10 Truths in #DistributedSystems Design applied to #ReactiveDDD: "The appropriate level of coupling depends on the level of control you have over the endpoints." This principle applies to bounded contexts as microservices/modules. Internal coupling within a bounded context

4/10 Truths in #DistributedSystems Design applied to #ReactiveDDD: "Loose coupling is better than lousy coupling." Coupling is unavoidable. To handle failures effectively, design for idempotency, accept eventual consistency as a trade-off for scalability and resilience, and

It is fascinating how the community around reactive systems is evolving. I want to thank Sam Hatoum and Raf Lefever for their significant contribution (which helped me explain the event-sourced systems). "Investing in scale and real reliability can be made at various system

The end of the year was so intense that I almost forgot to express my gratitude to BR-BIT (especially to Leonildo V., Marlon B., and Alan R.) for the opportunity to contribute to their initiatives. BR-BIT is modernizing its solutions by building a distributed, scalable platform

5/10 Truths in #DistributedSystems Design applied to #ReactiveDDD: "Queues invert control flow but require flow control." #EventStorming is a collaborative modeling technique well-suited for exploring domains and identifying "choreography-based integration points." It aids in

As a software developer, you've likely pondered this question: When is it best to use exceptions, and when should we opt for the result pattern? A well-designed system incorporates multiple levels of validation. The first layer, known as Fail-Fast, occurs at the entry point (at

Exciting News! I'll be attending the EventCentric conference at Domain-Driven Design Europe 2025 in Antwerp, Belgium, on June 4-5! Event-driven systems have been a core part of my career, whether as a developer, architect, or consultant, helping to shape resilient, scalable, and

Just arrived at Explore DDD Conference in Denver! Excited to join some of the greatest minds in #DomainDrivenDesign and dive deep into real-world #DistributedSystems and strategic modeling. #DDDesign

There is a persistent gap between context-specific entities in DDD and the focus on canonical ones. The same entity can have multiple perspectives, and composition is simply a matter of view. Domain Events propagate state rather than data.