Hi, our team has been discussing how to guarantee idempotency in persistent subscriptions. Persistent subscriptions guarantee that a given event gets delivered at least once to a persistent subscription group member, however, as many of you know, the event might get delivered more than one time (ex. the first delivery times out from the cluster perspective and the event gets re-delivered while the subscriber is still processing the first delivery).
We’re looking for ideas/suggestions on how to best leverage the eventstore infrastructure to guarantee idempotency in persistent subscriptions.
Thanks,
Javier.