According to Vernon Vaughn's - Implementing Domain Driven design:
...Events are used to rebuild the state of the Aggregate by replaying them in the same order in which they occurred. The premise is that this approach simplifies persistence..
My question is... In a DDD system where your domain is publishing events (and those events published to an event store), but the aggregates themselves are still persisted to a relational database - does the benefit of replaying events to create/recreate new readmodels come from simply having an event store? or do you need an event sourced domain (i.e having a version/sequence) to guarantee replayability.