Consumer lag is the number of events a view has yet to process. In CQRS, it helps monitor the event flow from provider services to query-side views, alongside end-to-end latency. section 13.2.3
A view catching up
After a provider service commits a change, its event may not yet have been processed by the view. A client querying during that delay may see old data; consumer lag measures the view’s unprocessed events. section 13.2.3
Figure 13.4 Because it takes time for an event to flow from the provider service to the CQRS view, a client is not guaranteed to be able to read its own writes. A query might not return data that is up to date.
See how event-flow delay can leave a CQRS view behind a committed change. section 13.2.3


