BARRYBARRY

Connectors

Streaming & messaging

Publish rows as events, or let a message start the run.

Message brokers sit on both sides of a data platform. On the way out, a transport can publish its rows as individual events so downstream consumers react as data arrives rather than waiting for a batch. On the way in, an incoming message is one of the six ways a transport run can start, which is how a pipeline becomes event-driven instead of scheduled. Kafka and Event Hubs do both, and can additionally carry alerts, so one connection can serve three purposes at once. Every capability is derived from the connector itself, so what a connection can be used for is never a matter of configuration.

Apache Kafka
Apache KafkaSinkTriggerAlert
Publishes rows as individual JSON messages with an idempotent producer, consumes topics to start transport runs, and can deliver alerts. Works with Apache Kafka, Confluent Cloud, MSK, Aiven and Redpanda.
Azure Event Hubs
Azure Event HubsSinkTriggerAlert
Publishes rows as events, listens to a hub to start transport runs, and can send alerts to a dedicated hub — all through the native AMQP client.
RabbitMQ
RabbitMQTrigger
Consumes an AMQP queue so each incoming message can start a transport run. It is a trigger only — data is not written back to RabbitMQ.

Looking for something else?

Every connection is Source, Sink, Trigger or Alert — derived from the connector itself, never set by hand. Browse the full catalogue, or ask us about a system you don’t see.

Ready to unlock your data?

See how BARRY brings your on-premises data to the cloud — safely, and on your terms.