I see, so it’s a way of effectively decoupling the state of the aggregate (store it inside the db) with the actual querying (just query the db). That way, at an

I see, so it’s a way of effectively decoupling the state of the aggregate (store it inside the db) with the actual querying (just query the db). That way, at any time, you can just stop the aggregate/sink, and recover where you left off. We have implemented our event store on top of PostgreSQL. I’m not a big fan of using Kafka as an event store.