I’ve got a system that I’m nudging towards full eventsourcing slowly but surely.
Today there are two databases, Live and Archive. While data is active it’s in the Live db, when it’s done it’s moved to Archive, and is considered readonly (except for audit info).
If we open to the door to using EventStore I don’t really see a benefit in the archive procedure anymore (and to be honest, it’s not exactly my idea to do it in SQL either!).
Question is, how do we subscribe to a stream that only contains the ‘active/live’ data? The only way I can think of is maintaining a readmodel with the streamids, and then subscribing to them one by one, but this seems convoluted. If we move it to a second EventStore as part of archiving we could delete old streams and subscribe to $all I guess, but that would tie us to the implementation of using two stores.