Destinations define where your stream data is delivered. Streams supports multiple destination types, each optimized for different use cases — from real-time webhooks to cloud storage, databases, and message queues.
How Delivery Works
Streams processes blocks sequentially and will not proceed to the next block or batch until receiving confirmation that the current batch was successfully delivered. This ensures data consistency but requires your destination to acknowledge receipt promptly.
If delivery fails, Streams retries based on your configuration. After the maximum retry attempts, the stream pauses automatically to prevent data loss.
Multiple Destinations
A single stream can deliver data to multiple destinations simultaneously. This lets you:
- Feed dev, staging, and production systems from one stream
- Combine real-time processing with long-term archival
- Supply multiple downstream services without duplicating streams
| Plan | Max Destinations |
|---|---|
| Free & Build | 1 |
| Scale & Business | 4 |
| Enterprise | 6 |
When using multiple destinations, all must successfully receive each batch before the stream advances. If any destination fails, the entire stream pauses. Upon restart, batches may be re-delivered to destinations that already received them.
Available Destinations
Deliver stream data to your HTTP endpoint in real-time.
Archive to Amazon S3, GCS, Backblaze B2, and more.
Microsoft Azure cloud storage with enterprise features.
Store in a relational database for SQL queries and joins.
Stream to Apache Kafka for high-throughput pipelines.