Two-way sync
Changes in Apache Druid or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and InterSystems IRIS 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 InterSystems IRIS'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 InterSystems IRIS where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in InterSystems IRIS sync into Apache Druid in real time, and result tables in Apache Druid sync back into InterSystems IRIS, with schema and type mapping between the two systems handled for you.
Point analytical queries at the synced copy in Apache Druid and keep InterSystems IRIS focused on its operational workload.
Rows from InterSystems IRIS land in Apache Druid as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Apache Druid sync into InterSystems IRIS, where whatever reads from that database gets them without querying the warehouse.
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 | InterSystems IRIS objects | |
|---|---|---|
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Views SQL views expose curated slices of data for outbound replication. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Schemas Schema organization scopes which tables a sync connection can see. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Namespaces Namespaces partition databases and determine the connection context for integrations. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–InterSystems IRIS connection.
Changes in Apache Druid or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or InterSystems IRIS 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 InterSystems IRIS record.
Track your Apache Druid ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and InterSystems IRIS.
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 InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS: 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.
Apache Druid: 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. InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
Apache Druid: Rollup can pre-aggregate events at ingestion time, meaning the stored granularity may differ from the raw event stream. InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. Stacksync's field mapping accounts for these differences between Apache Druid and InterSystems IRIS without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Apache Druid and InterSystems IRIS records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Druid and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–InterSystems IRIS integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and InterSystems IRIS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 InterSystems IRIS.