menu

Blocking until a command is executed

Support the documentation

This documentation was written by volunteers. Please help support our effort:

Help us improve the documentation

There are a few use cases where we need to ensure that a command has been successfully executed - and additionally, the projection has updated. More specifically: the events which have resulted from the command are persisted, and the projections which listen to these events are at least at that position. This is needed in the following scenarios:

  • For some Neos UI REST API calls, we need to change some state, and then read some projection to compute the response.
  • when we re-execute commands during the rebase of a content stream, we must ensure the projection is up to date after every command, to ensure the soft constraint checks for the following command work correctly. If we would violate this condition, it would be extremely likely that all commands executed rapidly one after the other, while the projection is way behind - this would effectively disable the soft constraints during rebase.

To implement this behavior, commands return a CommandResult object, which just has a single method blockUntilProjectionsAreUpToDate().

Internal Implementation

Internally, the command result stores the event identifiers of the resulting events - because of that, the command handlers have to always use the EventWithIdentifier wrapper to have the identifier generated there (and not just during persistence, which would be too late to have it abailable in the commandresult).

Then, when a projector works through its events one after the other, it stores the event identifiers it has recently seen in a list. Currently, we simply use a Flow cache for this with a short TTL.

Then, when we need to block until the projection is up to date, we simply ask the projection if all events are already in this list.

This implementation does deliberately not rely on a global ordering of all events with something like a global sequence counter; as not all event stores later on might have this functionality.

You might wonder how we ensure the recently seen event list does not grow unbounded? We arbitrarily cap it after a certain TTL; because a projection does not need to answer whether it has ever seen a certain event; but instead whether it has recently seen a certain event: The only point where we need this blocking behavior is inside a single request; and not during really long running work. If the user felt that he had to wait too long, he simply triggers a new request which is answered based on the current projection state.

Furthermore, there is an additional detail which had to be implemented: We are only allowed to ask a projection whether it has consumed an event if the projection actually handles this event type - as otherwise, it will never see this event and thus the event won’t be included in the “recently seen” list.

Implementation might change

later on, we might further change the internal implementation; however as the public API is so minimal, it is unlikely that it will change further.