Hands-On Mobile Development with .NET Core

The publisher/subscriber pattern

Let's assume that we have completed our brokered queue implementation and dispatched a consumer to finalize a long-running operation. At this point, as previously mentioned, our application is expecting a done signal so that it can get rid of any transient data.

In an open system, like the one we are in the process of implementing, where each service can communicate with each other (rather than a closed system where the execution is done sequentially down the stream), we are no longer dealing with a deterministic synchronous model, and yet the consumers of the system still expect results. In order to allow the source system (that is, the publisher) to propagate the output of an operation to the interested ...