Destinations

A destination determines where replayed data will be sent.

Batch currently supports the following destinations:

  • Kafka

  • RabbitMQ

  • Amazon SQS

  • HTTP

  • Redis PubSub

  • Redis Streams

A destination must be a publicly accessible resource. Batch will access the destination using the following IP's.

A destination will be automatically health-checked for you and its status will be available in the destination view and on the dashboard.

If a destination is "unhealthy", it means that Batch is not able to communicate with it and a replay is likely going to fail.

Optimal Destination (Geo) Location

Batch's "replayers" are hosted in AWS in the us-west-2 region.

To optimize for throughput, your destinations should be located as physically close as possible to Batch's servers.

If you are unable to "get closer" and require high throughput (10,000+ events/s), reach out to us and we'll see what we can do about standing up infrastructure that's located closer to you.

Kafka Destination

<TODO: INSTRUCTIONS + CONSOLE SCREENSHOT(S)>

RabbitMQ Destination

<TODO: INSTRUCTIONS + CONSOLE SCREENSHOT(S)>

Amazon SQS Destination

<TODO: INSTRUCTIONS + CONSOLE SCREENSHOT(S)>

HTTP Destination

<TODO: INSTRUCTIONS + CONSOLE SCREENSHOT(S)>