joliver / EventStore eventual consistency

I'm trying to figure out how my event storage and my read model are related in terms of actual nuts and bolts implementations.

My limited understanding of the event store leads me to believe:

1. Event is committed to event store
2. Dispatcher runs
3. If I'm using a queue, I send the message to a queue (lets say mass transit)
4. My read model is subscribed to the queue, so my read database gets the message (mysql)
5. My read model is updated with the new change to my data

This would mean that if anything happened to mass transit, my read database will be out of sync and I have to figure out how to sync it back.

Some stuff I've read/watched that's been published by greg young suggest using the event store itself as a queue, and maintain consistency by keeping an auto increment number on the event store side in order to maintain eventual consistency. I'm wondering if that is implemented in joliver's project?