Two-way sync
Changes in DuckDB or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB 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.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between DuckDB and InterSystems IRIS continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
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.
| DuckDB objects | InterSystems IRIS objects | |
|---|---|---|
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Namespaces Namespaces partition databases and determine the connection context for integrations. | |
| Views SQL views used to shape or filter data for downstream consumers. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Views SQL views expose curated slices of data for outbound replication. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Schemas Schema organization scopes which tables a sync connection can see. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–InterSystems IRIS connection.
Changes in DuckDB or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB 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 DuckDB or InterSystems IRIS record.
Track your DuckDB ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB 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 DuckDB 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 DuckDB 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 DuckDB and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as DuckDB's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). 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.
DuckDB: Execution is columnar and vectorized, optimized for analytical scans rather than high-frequency transactional writes. 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 DuckDB 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 DuckDB 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 DuckDB and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–InterSystems IRIS integration in-house.
Yes — Stacksync ships production-grade connectors for both DuckDB 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 DuckDB and InterSystems IRIS.