22 August 2015

At the moment the project is a sort of “Lab PoC” for a CQRS+ES application and it’s have a lot of short-cuts (for the sake of simplicity) that in a real project should be reviewed. One of this is the “implicit synchronism” of the UI. Let’s see one of the front-end calls to the server.


And the server API related:


This code is perfectly consistent, because the actions (send command, manage it, store events, dispatch events, update read model) are all in-process. This is true even if I don’t use anything from the result data in the success callback, but, again, it’s correct for the same reason: because in the CQRS we have separated Commands from Queries, so this command will not have any result (but the httpResult) and because, being all actions in-process, if we have an “Ok” as result, it means that the read model has been correctly updated with the data passed in front-end call.

Let’s go a step forward.

Let’s imagine now that there is a real asynchronism between, let’s say, the storage of the events and the dispatching and the processing of the events. This is quite common in a real CQRS+ES application; very often also the commands are stored in queues and their processing is delegated to a subsequent async process (in this case you could use solution like a polling mediator).

How can we notify the user about the changes introduced by his command in a common web application? It depends on the scenario obviously, some options are:

  • Trick the user that the command was successfully sent and elaborated. This is a good option in a lot of real cases; generally speaking, it’s good everytime there is little chance that an error will happen (e.g. in a e-commerce where the aggregates are changed rarely by more than a user concurrently)
  • Notify the UI when the read model is correctly updated, saying something like “data is updating…” in the meanwhile

There are some other valuable options and variants depending on the requirements. I want to explore the second option, using SignalR to notify the clients of the server-side changes to the read-model. Very useful for me was read and deepen the code of Crucial.CQRS project.

First Question: in which project is it preferable to put the SignalR hub? This hub will born to notify the users that the read-model has changed in someway, so, it seems to be a part of the query-stack. But the query-stack project is a class-library, with no awareness about the “environmental context”. But SignalR introduce references to Owin and web and this is a bad smell…other options could be to create a different project for SignalR hub, or, even better, keep the owin/signalR references in the API project and activate the hub with some notification mechanism…maybe I’ll return on this after.

Keeping it simple at first, I call an event notifier (dependant on Hub) at the end of the denormalizer methods in the QueryStack project. But first I’ve to set-up SignlR Hub


As you see, very simple, because, in this scenario, SignalR has just to notify the clients of server-side events and there are no actions callable from UI. Now that we have the channel between server and clients, we need to define the notification logic:


As you can see, I use:

  • DTO pattern to encapsulate and keep the serialization for SignalR channel out of the rest of the code.
  • AutoMapper to simplify object-to-object mapping and, in this case, it’s very easy

At the end, I call the notifier’s methods at the end of the read-model updates:


In the front-end side we need the code to establish the connection with the hub


and to listen for server-side notifications. I did that using Angular.js global events that can be handled in every controller


How and if manage these events could be an opportunity matter. Sometimes it’s ok to give an explicit notification to the user that something is changed, sometimes it’s ok to “trick” the user with the input data without waiting the notification. It’s all about the domain requirements.

blog comments powered by Disqus