ddd-crew / domain-message-flow-modelling Goto Github PK

Hi,

IIUC, the pattern language is very similar to EventStorming. In EventStorming, as in Domain Message Flow Modelling, Queries are green-ish stickies. What I don't understand is how to use them for visualizing flows.

Together with a Query, there is always a View or a Response. In my opinion, it can be required/helpful to visualize the two separately. A Query has a certain message body, same as a View/Response.

Would be great if you could explain the intended use in the README, maybe with an example.
Alternatively, if you can explain how it is meant to be, I can also create an MR.

Thanks!

Hey ddd-crew,

in preparation of a workshop, I did a modeling test run. During this test a question came to my mind.

How do you model an event-based integration between two bounded contexts (BC A and BC B) with a domain message flow diagram? The command-based integration is easy. BC A sends a message to BC B.

But what if we aim for an approach based on an event-based integration. In this case BC A emits an event that BC B is subsribed to?

Lets make it a bit more explicit based on the example in this repo:

• The sales BC is subscribed to "Payment collected" events
• The billing BC emits the event "Payment collected"

Looking into the language in the example, step 5 gives me the hint that we are integrating based on events (Payment collected). But the arrow-direction from the billing BC to the sales BC confuses me a bit. This would suggest command-based integration rather than event-based integration. I would not expect a direct connection from the billing BC to the sales BC when using events.

What do you think? How do you visualize event based integrations?

Best,
Christian

Can someone explain how can I use this notation? Is this available in miro boards or lucid charts. I tried few places I couldnt find how to use this chart

How about a notation of a time-dependent message? E.g. scenario: cancel an online order after 5 minutes of inactivity

We need to clarify when to use the system icon or the bounded context icon