Two-way sync
Changes in Apache Druid or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and DuckDB 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 DuckDB'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 DuckDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in DuckDB sync into Apache Druid in real time, and result tables in Apache Druid sync back into DuckDB, 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 DuckDB focused on its operational workload.
Rows from DuckDB 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 | DuckDB objects | |
|---|---|---|
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Schemas Namespaces within a database used to organize tables in sync outputs. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Tables Columnar tables created via SQL; the destination for materialized sync data. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Views SQL views used to shape or filter data for downstream consumers. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–DuckDB connection.
Changes in Apache Druid or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or DuckDB 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 DuckDB record.
Track your Apache Druid ⇄ DuckDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and DuckDB.
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 DuckDB 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 DuckDB 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 DuckDB: authenticate both systems, choose the objects to sync (such as Apache Druid's Datasources and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Druid and DuckDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–DuckDB integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and DuckDB. 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 DuckDB: Polling or full re-reads; no change feed or transaction log API. 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: Tasks, Datasources, Segments, Dimensions, plus custom fields where Apache Druid exposes them. On the DuckDB side: Database files, Schemas, Tables, Views. 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.
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 DuckDB.