One of the big issues I’ve always found with all streaming services is rehydration post migration or for HA or failover.

Has this group done testing for how long it takes for different sizes of streams to rehydrate?

One approach is to keep track of the ID of the last consumed event and use that as the starting point for rehydration. That way, even after a migration or failover, the stream can resume efficiently without replaying the entire history.