Consider using subscriptions alongside with reads
For continuous replication (online backup or testing the cloud on prod data), it would be better to use a catch-up subscription, which runs continuously, rather than end to the end of $all, then wait and start again.
For continuous replication (online backup or testing the cloud on prod data), it would be better to use a catch-up subscription, which runs continuously, rather than end to the end of
$all, then wait and start again.
Does it still work like this - end to end, wait, repeat?
Yes, but I think the delay between the restarts is configurable. Explicit read allows us to get more control over reads, plus I haven't got any indication of demand for this feature, so it was never implemented.