Skip to content
Data warehouse

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

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

Keep tables consistent across Apache Druid and Snowflake, 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 Snowflake 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

  • 01 Sync Druid query results into a warehouse to combine real-time aggregates with historical models.
  • 02 Keep lookup tables in Druid refreshed from a CRM or database so query-time joins use current reference data.
  • 03 Push product usage aggregates from Snowflake into sales and success tools for account prioritization
  • 04 Feed finance reconciliation models from ERP data landed in Snowflake on a continuous basis

Common sync patterns

Migration without a big bang

When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.

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.

What you can sync between Apache Druid and Snowflake

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 Snowflake objects How this pairing syncs
Tasks Batch ingestion and compaction jobs monitored during data loads. Tasks Scheduled SQL used to transform synced data after it lands. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Virtual Warehouses The compute a sync's queries run on, sized independently of storage. Ingestion Supervisors is specific to Apache Druid and Virtual Warehouses to Snowflake — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. Databases Top-level containers that scope which data a sync can touch. Lookups is specific to Apache Druid and Databases to Snowflake — each maps to any object or custom field on the other side.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Schemas Namespaces within a database used to organize synced tables. Datasources is specific to Apache Druid and Schemas to Snowflake — each maps to any object or custom field on the other side.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Tables The main landing and activation target for synced records. Segments is specific to Apache Druid and Tables to Snowflake — each maps to any object or custom field on the other side.
Dimensions String and categorical columns used for filtering and grouping in synced queries. Views Modeled projections used as the source side of outbound syncs. Dimensions is specific to Apache Druid and Views to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Snowflake

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.

Apache Druid Snowflake Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

DeliveryEach detected change is applied to Snowflake as a row-level write, with types converted between the two schemas.

Snowflake Apache Druid Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Apache Druid ⇄ Snowflake

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Apache Druid ⇄ Snowflake 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 Snowflake.

How the Apache Druid and Snowflake 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

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

How to connect Apache Druid to Snowflake — 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 Snowflake 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
    Snowflake connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Snowflake 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 ⇄ Snowflake
    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 Snowflake
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Apache Druid and Snowflake integration FAQ

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 481 integrations available for Apache Druid and Snowflake.

Popular · 5 of 481
Coworkers laughing in front of a laptop in a casual office setting

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