Connector catalog
Bridge connects 100+ sources and destinations across databases, warehouses, data lakes, messaging systems, files and IoT. This page lists what each category covers, the access method it uses, and the limitations that decide a POC.
Docs · Reference · Updated 2026-11-03 · Applies to current Bridge releases
What counts as a connector
A connector is a versioned reader or writer that owns authentication, extraction semantics and type mapping for one system. Bridge ships 100+ connectors today and maintains a public roadmap of 300+. Every connector is exercised by the conformance suite before release, and each declares the versions it supports.
Capture connectors fall into two families: log-based (reads the source transaction log, no table scans) and batch or API-based (reads tables, files or endpoints). The family determines impact on the source, not the quality of the connector.
Catalog by category
| Category | Examples | Access method | Known limitations to check |
|---|---|---|---|
| Relational databases | Oracle, MySQL, SQL Server, PostgreSQL, Db2, Dameng (DM), KingbaseES, GBase | Log-based capture (redo / binlog / WAL) or JDBC batch | Supplemental logging and archive retention on Oracle; ROW format on MySQL; replication-slot retention on PostgreSQL and Kingbase |
| NoSQL | MongoDB, Redis | Change streams / oplog; key scan for Redis | MongoDB change streams require a replica set; Redis is a key-value model, so relational transforms do not map one-to-one |
| Cloud warehouses | Snowflake, Redshift, BigQuery, ClickHouse, Greenplum, AnalyticDB | Streaming ingest or staged COPY / bulk load | Warehouse-side credit or slot cost; per-load size thresholds; identifier case rules differ by warehouse |
| Data lakes | S3, HDFS, Hive, Iceberg, Delta, MaxCompute, FusionInsight | File write plus table-format commit | Iceberg and Delta need a catalogue and commit protocol; small-file accumulation needs compaction |
| Messaging | Kafka, RocketMQ, RabbitMQ, Pulsar | Producer / consumer with offset control | Ordering guarantees depend on partitioning; at-least-once delivery requires idempotent target writes |
| Time-series & IoT | MQTT, InfluxDB, TDengine, Druid | Native protocol or HTTP ingest | High-cardinality tags stress both capture and target; retention policies may silently drop rows |
| Files & object storage | CSV, JSON, Parquet, XML over S3 / SFTP / local | File push with optional compression | Schema inference on semi-structured files; encoding and delimiter edge cases |
Two rules keep this page honest. First, a connector is not "supported" because it appears in a list — it is supported for the versions named in its entry, and that list is what you should compare during a POC. Second, "100+ connectors" is a coverage statement, not a depth statement: the questions worth asking are which of your systems are log-based and which will fall back to batch.
How to choose a first connector set
| Your situation | Start with | Why |
|---|---|---|
| High-churn OLTP to a warehouse | Oracle / MySQL / PostgreSQL log-based to Snowflake or Redshift | Log capture avoids table scans and gives sub-minute lag |
| Legacy consolidation | Db2, Dameng or Kingbase batch to a lake | Batch is sufficient and avoids source configuration changes |
| Event-driven application | Kafka to warehouse or lake | Offset control and replay are native |
| Isolated or regulated network | Any source to file push | File exchange crosses a gateway without inbound connectivity |
Connector questions
Are all 100+ connectors log-based?
No. Log-based capture applies to the database sources that expose a transaction log — Oracle, MySQL, SQL Server, PostgreSQL, Kingbase, DM and MongoDB change streams. Warehouses, lakes, messaging and IoT use their native protocols.
Can I request a connector?
Yes. Enterprise includes custom-connector development, and the public roadmap lists planned additions.
Where are version numbers listed?
In each connector entry in the product documentation. This page summarises families and limitations; the version list is authoritative and moves with releases.
Do connectors cost extra?
No. Connectors are not a billing dimension — there is no per-connector charge on any plan.