Recreate persistent subscriptions in the sink ESDB

[kaancfidan]

Is your feature request related to a problem? Please describe.
Persistent Subscriptions are not replicated to the sink ESDB.

Describe the solution you'd like
I would like the replicator to recreate the persistent subscriptions in the sink ESDB with exact parameters and checkpoints as in the source ESDB.

[alexeyzimarev]

I am not sure it's in scope for the replicator, as well as user-defined projections... I never planned this tool to be a full-blown migration tool between two clusters. But, I'll discuss it with the team.

[kaancfidan]

Well, people will need something to start using Event Store Cloud if they already have self-deployed ESDB in their production.

We extensively use persistent subscriptions to create load balanced services and we currently have 40 million events in the production store. Although our services can handle event redeliveries, doing that for 40 million events takes a significant amount of time.

The only solution we have now is to create the persistent subscriptions with their current offset manually, which we'll do. We will have to recreate 32 separate persistent subscriptions with correct parameters & offsets. I would say it's a minor inconvenience.

If this replication tool took care of that during migration, that would be awesome.

[alexeyzimarev]

It's the same with catch-up subscriptions, I mentioned it in the docs. Persistent subscriptions are maybe easier as for the older ESDB versions you could only subscribe to a normal stream, not to $all.

Handling persistent subscription checkpoints would require the same functionality to track event numbers on both sides, and it's not easy.