What is the proper diagram to describe an event subscriber final graph?

Question

I'm working on a microservice application and I need to describe the complete execution graph of a specific event being published, where each node in the graph is a specific microservice subscription to this first event.

This diagram should be able to describe new events that are eventually published in response of this first event as well (the one that generates the whole execution graph).

Which diagrams are used to describe this kind of flow?

Answer 1

The usual way is to use an UML sequence diagram. But with a long chain you might end with an unreadable diagram.

The UML communication diagram would therefore offer a more compact and convenient overview, with the different services involved, their links and chronologically numbered messages exchanged labeled with the different events produced/consumed.