Skip to content
Data warehouse ⇄ Database

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

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

Connect OpenSearch and Apache Druid with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want OpenSearch'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 OpenSearch where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in OpenSearch sync into Apache Druid in real time, and result tables in Apache Druid sync back into OpenSearch, with schema and type mapping between the two systems handled for you.

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.
  • Sync product catalogs from an ERP or database into the indexes that back storefront search.
  • Keep Postgres as the source of truth while mirroring rows to OpenSearch for full-text and vector queries.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in Apache Druid and keep OpenSearch focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from OpenSearch land in Apache Druid as they change, replacing hand-built CDC and batch extract jobs.

What you can sync between Apache Druid and OpenSearch

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 OpenSearch objects
Lookups Key-value mappings joined at query time, refreshable from external systems. Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills
Tasks Batch ingestion and compaction jobs monitored during data loads. Index templates Mapping and settings presets applied to new indexes a sync creates
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Ingest pipelines Server-side processors that transform documents as they are written
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Data streams Append-oriented time-series storage for logs and events pushed from source systems
Dimensions String and categorical columns used for filtering and grouping in synced queries. Snapshots Backup artifacts, relevant when reseeding an index from a repository
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Indexes The core container; synced records land in indexes with defined mappings
What ships with Apache Druid ⇄ OpenSearch

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

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

    Choose tables

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

Apache Druid and OpenSearch 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 OpenSearch.

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.