I am indeed describing CQRS, or at least the way I see it. The way I am doing is this by making my read side a combination of lightweight "code-only" domain mod

I am indeed describing CQRS, or at least the way I see it. The way I am doing is this by making my read side a combination of lightweight "code-only" domain models and heavy db-side indexing of events themselves (as opposed to domain model tables of some sort) You can read more about it at https://blog.eventsourcing.com/lazy-event-sourcing-ed7e59007e17 https://blog.eventsourcing.com/lazy-event-sourcing-ed7e59007... and https://blog.eventsourcing.com/why-use-eventsourcing-database-6b5e2ac61848#.6kbrzbtr9 https://blog.eventsourcing.com/why-use-eventsourcing-databas... If you have any thoughts or questions, feel free to reach out to me (my nickname is the same almost anywhere, twitter, gmail, etc.) or Eventsourcing gitter room http://gitter.im/eventsourcing/eventsourcing http://gitter.im/eventsourcing/eventsourcing and I'll be happy to talk about these things.