BARRYBARRY

Documentation

Connectors

Every source, sink, trigger and alert channel, with its configuration.

In BARRY everything you talk to is a Connection — configured once, then referenced wherever you need it. A connection's capabilities are not something you set by hand; they are derived from the connector itself. The same row can be a Source, a Sink, a Trigger, an Alert channel, or several of those at once, and the UI only ever offers it where that capability makes sense.

The relational connectors read the databases your business already runs on — SQL Server, PostgreSQL, MySQL, MariaDB, Oracle and Db2 — as they are, with no upgrade required. Several of them also write, so one system can be a source in one pipeline and a destination in another. When the native connectors run out, a generic ODBC source reaches almost anything with a driver on the client machine.

Business systems tend to hand their data over through APIs rather than database ports. SAP comes in through Gateway OData services and CDS views, or over RFC at table level; Dynamics 365 Business Central through its OData API; and when a system has no dedicated connector, the generic REST and OData connectors cover most in-house and SaaS endpoints, each dealing with its own authentication and paging.

On the sink side the warehouse and lakehouse connectors land governed, query-ready tables: a managed Delta table under Unity Catalog, a Fabric lakehouse or warehouse, Snowflake, BigQuery, and Apache Iceberg written against a Polaris, Glue or Nessie catalog. Some are self-contained, owning the whole path from Arrow batches to a registered table; others stage files and apply them with the platform's own load command.

Around those sit the rest of the catalogue. Object storage — S3, ADLS Gen2, Blob and GCS — and file transfer over FTP and SFTP handle raw files. Kafka, Event Hubs, RabbitMQ and Event Grid provide streaming sinks and messaging triggers. Teams, Slack and webhooks are alert channels. Because every capability is derived from the registry, a source-only database never appears as a sink and a Teams channel only shows up where an alert is expected — the catalogue stays honest without anyone maintaining it by hand.

← All documentation

Ready to unlock your data?

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