Two-way sync
Changes in Apache Druid or Citus instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Citus in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Citus's rows in Apache Druid, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Citus where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Citus sync into Apache Druid in real time, and result tables in Apache Druid sync back into Citus, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Apache Druid and keep Citus focused on its operational workload.
Rows from Citus land in Apache Druid as they change, replacing hand-built CDC and batch extract jobs.
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.
| Apache Druid objects | Citus objects | |
|---|---|---|
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Sequences Key generators that matter when external writes must not collide with application inserts. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Views Curated projections over distributed data, often used as read-only sync sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Citus connection.
Changes in Apache Druid or Citus instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Citus data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Apache Druid or Citus record.
Track your Apache Druid ⇄ Citus sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Citus.
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.
Authenticate Apache Druid and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Apache Druid and Citus 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Apache Druid and Citus: authenticate both systems, choose the objects to sync (such as Apache Druid's Segments and Dimensions), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Apache Druid and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Apache Druid side: Lookups, Tasks, Datasources, Segments, plus custom fields where Apache Druid exposes them. On the Citus side: Local tables, Schemas, Views, Sequences. 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 Apache Druid and Citus: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Apache Druid and Citus.