Skip to content
Data warehouse

Apache Druid to Dremio integration — real-time, two-way sync

Keep Apache Druid and Dremio 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 Apache Druid and Dremio

Keep tables consistent across Apache Druid and Dremio, for a migration, a multi-warehouse stack, or a dataset two platforms both need.

Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.

Stacksync syncs tables between Apache Druid and Dremio continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.

Common use cases

  • Sync Druid query results into a warehouse to combine real-time aggregates with historical models.
  • Keep lookup tables in Druid refreshed from a CRM or database so query-time joins use current reference data.
  • Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
  • Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.

Serve tools that only connect to one platform

Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.

Shared datasets across teams

Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.

Consolidation after M&A

Bring the acquired company's warehouse data across continuously instead of through one-off dumps.

What you can sync between Apache Druid and Dremio

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 Dremio objects
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Reflections Materialized accelerations that make repeated extraction queries cheaper.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Jobs Query execution records useful for monitoring sync workloads.
Lookups Key-value mappings joined at query time, refreshable from external systems. Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place.
Tasks Batch ingestion and compaction jobs monitored during data loads. Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads.
What ships with Apache Druid ⇄ Dremio

Connect Apache Druid and Dremio for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Dremio connection.

Real-time

Two-way sync

Changes in Apache Druid or Dremio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid or Dremio 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 Apache Druid or Dremio record.

Observability

Monitoring

Track your Apache Druid ⇄ Dremio sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Druid and Dremio.

How the Apache Druid and Dremio connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits
How it works

How to connect Apache Druid to Dremio — 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.

  1. 01

    Connect your apps

    Authenticate Apache Druid and Dremio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Druid connected
    Dremio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Dremio 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Druid ⇄ Dremio
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Apache Druid Dremio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Apache Druid and Dremio integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Apache Druid and Dremio.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.