The preceding discussion may have left you thinking about how the event being raised, will map the call of the respective microservice perfectly; let's discuss this in further detail. Think of all of the events being raised, as being stored in an event store. The event stored has an associated delegate function, which is called to cater to the respective event. Consider the following diagram:
Although we're showing that the store has just two columns of Event and Function (at the top of the diagram), it stores much more information, such as the details of the publisher and subscriber. Each event contains the complete information that is required to trigger the corresponding service. So, event delegation might be a service to be called or a function within the application itself. It doesn't matter to this architecture.
In other...