Replays are at the core of the Batch platform. Replays allow you to replay events in your collections back to your event bus, helping with data loss and disaster recovery.
For information on what destinations we can replay your data to, please see Destinations.
While Batch does transform and annotate your payloads with additional data for display and indexing purposes, your original payload will be replayed back exactly as it was received, in the format in which it was received.
<TODO: INSTRUCTIONS + SCREENSHOT>
What does a PAUSE Mean?
Why would you PAUSE a replay?
What are the implications of a PAUSE? (possibility for repeated events)
During a replay, Batch will "push" events to your configured destination.
Replays take ~30 seconds to start up (and can increase from there, as the data is read from S3).
This list describes how the events are pushed and what their payloads look like.
We will perform non-batched,
POST requests against the URL that you specified when creating the destination
We will pass any headers that were configured on the destination
The payload will be included in the body of the
The payload is an unmodified version of the original payload we received from you
Replays are counted in the number of GB's transferred; think bandwidth. Your plan comes with a specific number of GB's you can replay per month.
If you need additional replay, you can either upgrade your plan or purchase a replay add-on.
<TODO: INSERT REPLAY USAGE SCREENSHOT>
Replay throughput will vary based on where the replay destination is located at.
On average, Batch should be able to replay at:
~10,000 events per second if you are on the US West coast
~5,000 events per second if you are on the US East coast
~1,000 events per second if you are in EU
~500 events per second if you are in Asia
If you need higher throughput, you should try to relocate your destination to be closer to Batch's location.
If that is not possible, reach out to us and we'll see if it's possible for us to get closer to you.