Movement Modes
Wirekite moves data three ways. Every cell in the matrices below refers to one of these modes:Data
One-time bulk load — schema and rows into an empty target, once.
Replicate
Continuous change data capture (CDC), streamed source to target.
Target Sync
One-shot diff-and-apply — reconciles an already-populated target to its source.
As a Source
Which databases Wirekite can extract from, and in which modes.| Engine | Data | Replicate | Target Sync |
|---|---|---|---|
| Oracle | ✓ | ✓ | ✓ |
| PostgreSQL | ✓ | ✓ | ✓ |
| MySQL | ✓ | ✓ | ✓ |
| MariaDB | ✓ | ✓ | ✓ |
| SQL Server | ✓ | ✓ | ✓ |
| SingleStore | ✓ | ✓ | — |
| YugabyteDB | ✓ | ✓ | — |
| TigerData | ✓ | ✓ | — |
| Google AlloyDB | ✓ | ✓ | — |
| Google Spanner | — | ✓ | — |
| Cassandra | — | — | ✓ |
Google Spanner is a Replicate (CDC) source only. Cassandra is a Target Sync source only — it has no CDC path. YugabyteDB, TigerData, and AlloyDB are PostgreSQL-compatible; SingleStore is MySQL-compatible.
As a Target
Which databases Wirekite can load into, and in which modes.| Engine | Data | Replicate | Target Sync |
|---|---|---|---|
| Oracle | ✓ | ✓ | ✓ |
| PostgreSQL | ✓ | ✓ | ✓ |
| MySQL | ✓ | ✓ | ✓ |
| MariaDB | ✓ | ✓ | ✓ |
| SQL Server | ✓ | ✓ | ✓ |
| SingleStore | ✓ | ✓ | ✓ |
| YugabyteDB | ✓ | ✓ | — |
| TigerData | ✓ | ✓ | — |
| Google AlloyDB | ✓ | ✓ | — |
| Google Spanner | ✓ | ✓ | ✓ |
| Snowflake | ✓ | ✓ | ✓ |
| Firebolt | ✓ | ✓ | ✓ |
| Google BigQuery | ✓ | ✓ | ✓ |
| Databricks | ✓ | ✓ | ✓ |
| MongoDB | ✓ | ✓ | ✓ |
Streaming Queues
Wirekite can also publish a source’s change stream to a message queue instead of a database, for downstream consumers to read. Queues carry CDC change events (the Replicate mode).| Queue | Replicate |
|---|---|
| Apache Kafka | ✓ |
| Redpanda | ✓ |
| Google Pub/Sub | ✓ |
Don’t see your engine? New sources and targets are added based on what teams need — reach out at hello@wirekite.io.