Connectors
Every source, destination, trigger and alert channel BARRY speaks to — filter by category. Each capability is derived from the connector itself.
SourceSinkReads SQL Server 2016 and later, Azure SQL Database, Managed Instance and RDS, with change tracking for change data capture. As a destination it bulk-loads straight into your tables.
SourceSinkReads any modern PostgreSQL, including managed services, and captures inserts, updates and deletes through logical replication. Writes use the binary COPY path, the fastest way into Postgres.
SourceSinkReads MySQL and captures changes from the binary log using either GTIDs or file positions, so a table stays current without repeatedly scanning it.
SourceSinkWire-compatible with the MySQL connector, with support for MariaDB’s three-part GTIDs so replication-based change capture works the same way.
SourceReads Oracle through the managed .NET driver using Easy Connect strings. Full and watermark-based incremental loads are supported; log-based change capture is not part of this connector.
SourceReads Db2 through the platform-native driver, with separate Windows and Linux builds. Full and watermark-based incremental loads are supported.
SourceThe fallback for anything with an ODBC driver on the client machine — SAP HANA, Sybase, Teradata, Informix and similar. Slower and with lower type fidelity than a native connector, but it reaches systems nothing else does.
SinkWrites into ClickHouse Cloud, open-source ClickHouse and hosted variants by streaming rows straight into an INSERT over the HTTP interface.
SinkLoads into Apache Doris through its Stream Load endpoint. Append is the supported write mode, which suits event-style and log-style tables.
SourceReads SAP through Gateway OData services and CDS views, and can track deltas so each run fetches only what changed since the last one.
SourceExtracts SAP tables over RFC and can capture changes at table level. This route needs a small ABAP transport installed in your SAP system.
SourceReads Business Central through its OData v4 API using Entra ID authentication, so financial and operational entities load like any other source.
SourceA generic connector for JSON REST endpoints. The on-prem client walks the endpoint’s pages and turns the responses into rows, which covers most in-house and SaaS APIs.
SourceA generic OData v4 connector. Entity sets are discovered from the service metadata, so you can browse and pick what to load instead of writing requests by hand.
SinkWrites managed Delta tables under Unity Catalog. Data is staged in a volume and applied with COPY INTO, MERGE INTO or a full replace, so the table ends up registered and query-ready.
SinkThe direct-streaming route into Databricks: Arrow batches are ingested over ADBC into a staging table and merged, skipping volume staging entirely.
SinkLoads into Snowflake by staging files and running COPY INTO, with append, overwrite and merge all supported.
SinkLoads Parquet partitions into BigQuery through native load jobs. The dataset and table are expected to exist, which fits a managed-schema setup.
SinkWrites into the Tables area of a Fabric lakehouse. Data is staged in OneLake and applied by generated PySpark running in a Fabric session.
SinkWrites into a Fabric warehouse over its SQL endpoint, either with COPY INTO or through a staging table and a MERGE, depending on the write mode.
SinkWrites Iceberg tables against the catalog of your choice (see below), using a storage connection you have already configured. Append and upsert are supported, the latter through equality deletes.
SinkWrites managed Iceberg tables on S3, committing snapshots through the REST catalog. Append, overwrite and merge are supported.
SinkRegister your Iceberg tables in an Apache Polaris catalog: BARRY commits snapshots through the Polaris REST catalog with OAuth2 client credentials, so engines that share the catalog see the data immediately.
SinkAn Iceberg catalog with git-style branches and commits. BARRY writes snapshots to the branch you choose through the Nessie REST catalog, so you can stage and promote data changes like code.
SinkRegister Iceberg tables in the AWS Glue Data Catalog through its Iceberg REST endpoint, with requests signed by SigV4 against a storage connection you have already configured.
SinkPlannedOn the roadmap: Dremio speaks the Iceberg REST catalog, so once BARRY exposes its generic REST-catalog option you will be able to land Iceberg tables that Dremio queries directly.
SinkA pull endpoint rather than a push: Databricks Lakeflow reads from BARRY on demand, so nothing has to be staged or copied in advance.
SinkExposes data to Spark as a readable source, so a cluster reads directly from BARRY instead of waiting for a landed copy to appear.
SinkWrites into hierarchical-namespace storage with the full range of Azure authentication options — access key, SAS, service principal, managed identity or workload identity federation.
SinkWrites into flat-namespace blob accounts, for storage that was not created with a hierarchical namespace.
SinkWrites to Amazon S3 and anything speaking the same API — MinIO, Cloudflare R2, Ceph and others — with six authentication methods including OIDC-based role assumption.
SinkWrites into GCS buckets using a service-account key, application default credentials, or impersonation of another service account.
SinkWrites files into the Files area of a Fabric lakehouse — the right choice when Fabric is your platform but you want plain files rather than managed tables.
SinkDelivers files to an FTP server, with plain, explicit TLS and implicit TLS all handled by the same connector.
SinkDelivers files over SSH, authenticating with a password or a private key — the usual route for exchanging data with partners.
SinkTriggerAlertPublishes 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.
SinkTriggerAlertPublishes 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.
TriggerConsumes an AMQP queue so each incoming message can start a transport run. It is a trigger only — data is not written back to RabbitMQ.
AlertPosts an Adaptive Card into a Teams channel through an incoming webhook, so a failed or stale run shows up where the team already talks.
AlertPosts a message into a Slack channel through an incoming webhook URL — the quickest channel to set up when your team already lives in Slack.
AlertSends a message into a Webex space using a bot token and the room identifier, for organisations standardised on Webex.
AlertSends alert email through any SMTP relay, often the simplest option when notifications need to reach people outside the chat tools.
AlertSends mail through the Microsoft Graph API using an Entra application registration, so alerts come from a real mailbox in your tenant rather than an anonymous relay.
AlertPosts JSON to a Logic App HTTP trigger, which lets you route alerts into whatever workflow, ticket system or approval chain you have already built.
AlertCreates a work item — a bug or a task — in Azure DevOps, so a failed run turns into something that appears in the team’s backlog.
AlertPublishes an event to a custom Event Grid topic, useful when alerts should fan out to several subscribers rather than a single channel.
AlertSends an arbitrary HTTPS request, which covers any system that accepts a webhook but has no dedicated connector.
Missing a system? Tell us what you need.
See how BARRY brings your on-premises data to the cloud — safely, and on your terms.
You are currently viewing a placeholder content from Vimeo. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More Information