Next week I will be doing a talk on the using the Event Store as a read model. I have spent so much time the last few years talking about the benefits of Event Sourcing as a write model but there are some quite unique scenarios where it makes a ton of sense as a read model as well.
It will also be interesting for me as many people have misunderstood the concept of the “projections library” in the event store. In particular I often get asked the question “how do I query all of my states to get the ones with the last name of “xxx””. While this *can* be done in the projections library you probably should not be doing it there. It sounds more like you want a document db/kv store. This is something we have not been good in explaining to people as of yet (largely because we have been so focused on the primary use case of the write side)