What is "Pipeline Egress"?
Egress is the exit point
In Datastreamer, Pipeline Egress refers to the final stage of a data pipeline — where transformed data leaves the Datastreamer platform and is delivered to a target destination.
Whether you’re routing data to a warehouse, an object store, or a streaming endpoint, the egress component determines where your data goes and how it’s formatted upon delivery.
Egress of one pipeline could be the ingress of another!
In complex use cases, some customers chain pipelines by having the egress of one be the ingress of the other. This is most common with Searchable Storage.
Examples of Egress Options
Destination Type | Examples |
---|---|
Cloud Data Warehouses | BigQuery, Snowflake |
Cloud Storage | Amazon S3, Google Cloud Storage |
Streaming / Queues | Kafka, Kinesis, Pub/Sub |
HTTP Endpoints | Webhooks, Custom APIs |
Files | Local testing (JSON, CSV) |
Egress Component Configuration
Each egress destination has its own configuration schema, typically including:
- Authentication details (e.g., service account, access key)
- Destination path or table name
- Output format (e.g., JSON, CSV, Avro)
- Delivery guarantees (streaming, batch, retries, etc.)
Updated about 20 hours ago