2 posts tagged with "Event Driven"

We Event-Modeled a multi-team tournament product to keep delivery scalable: domain squads own slices on one board, and later features can often subscribe to events already on the timeline instead of rewiring core flows.

This case study follows three beats:

1. Why Event Modeling — product-wide board, Conway-aligned teams, event contracts.
2. Event Modeling in practice — the seven steps on the tournament entry process (diagrams, abbreviated tickets).
3. Running tournament entry — Saga and CQRS-style read paths as the runtime shape that matches the model.

We modeled the whole tournament; this post zooms into tournament entry for depth on fan-out, orchestration, and compensation. Simplified example; reflects how we modeled, sliced, and shipped the work.

As our system moved from a monolith towards microservices, services needed a way to communicate without depending on one another directly. We used ActiveMQ, managed through Amazon MQ, for that messaging. Later, we moved to Kafka on Amazon MSK.

This was not simply a change of hosting provider. ActiveMQ and Kafka have different messaging models, so the migration made us revisit how we publish, consume, and operate events. Here is why we made the move, what changed, and what I would keep in mind when planning a similar migration.