Real-time
Two-way sync
Changes in Citus or MariaDB instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to MariaDB integration — real-time, two-way sync
Keep Citus and MariaDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Citus and MariaDB
Keep Citus and MariaDB synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Citus and MariaDB continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- 03 Feed a warehouse continuously from MariaDB using binlog-based capture instead of scheduled dumps
- 04 Keep several MariaDB instances aligned with one system of record across environments
Common sync patterns
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Cross-engine sync
Keep the same dataset live in both Citus and MariaDB, so each workload runs on the engine that suits it.
What you can sync between Citus and MariaDB
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Citus objects | MariaDB objects | How this pairing syncs | |
|---|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Views Read-side projections used as outbound sync sources. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Primary and Unique Keys Match keys for idempotent upserts. | Distributed tables is specific to Citus and Primary and Unique Keys to MariaDB — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | Reference tables is specific to Citus and System-Versioned Tables to MariaDB — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | JSON Columns Semi-structured payloads validated with JSON functions. | Local tables is specific to Citus and JSON Columns to MariaDB — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Stored Procedures Server-side logic that can post-process synced rows. | Schemas is specific to Citus and Stored Procedures to MariaDB — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Sequences is specific to Citus and Databases (Schemas) to MariaDB — each maps to any object or custom field on the other side. |
How changes propagate between Citus and MariaDB
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Citus MariaDB Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is applied to MariaDB as a row-level write, with types converted between the two schemas.
MariaDB Citus Sub-second propagation
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Citus ⇄ MariaDB
Connect Citus and MariaDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–MariaDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or MariaDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Citus or MariaDB record.
Observability
Monitoring
Track your Citus ⇄ MariaDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and MariaDB.
How the Citus and MariaDB connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Citus to MariaDB — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Citus and MariaDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
MariaDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and MariaDB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Citus ⇄ MariaDBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus MariaDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and MariaDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and MariaDB: authenticate both systems, choose the objects to sync (such as Citus's Views and Distributed tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Citus side: Views, Sequences, Distributed tables, Reference tables, plus custom fields where Citus exposes them. On the MariaDB side: System-Versioned Tables, JSON Columns, Stored Procedures, Databases (Schemas). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Citus and MariaDB: Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). MariaDB: SQL wire protocol (MySQL-compatible client/server protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host). Stacksync manages authentication, retries, and rate limits on both sides.
-
Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. MariaDB: Composite primary keys are not supported (primary key must be a single column). Stacksync's field mapping accounts for these differences between Citus and MariaDB without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 371 integrations available for Citus and MariaDB.
Popular · 1 of 371
No integrations match .
