Two-way sync
Changes in InterSystems IRIS or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS 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.
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 InterSystems IRIS and OpenSearch 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.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both InterSystems IRIS and OpenSearch, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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.
| InterSystems IRIS objects | OpenSearch objects | |
|---|---|---|
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Index templates Mapping and settings presets applied to new indexes a sync creates | |
| Views SQL views expose curated slices of data for outbound replication. | Ingest pipelines Server-side processors that transform documents as they are written | |
| Schemas Schema organization scopes which tables a sync connection can see. | Data streams Append-oriented time-series storage for logs and events pushed from source systems | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Snapshots Backup artifacts, relevant when reseeding an index from a repository | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Indexes The core container; synced records land in indexes with defined mappings | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Documents JSON records written via the index and bulk APIs and read via search queries |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–OpenSearch connection.
Changes in InterSystems IRIS or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or OpenSearch data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or OpenSearch record.
Track your InterSystems IRIS ⇄ OpenSearch sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and OpenSearch.
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 InterSystems IRIS 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.
Pick the InterSystems IRIS 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.
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 InterSystems IRIS and OpenSearch: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the InterSystems IRIS side: Persistent Classes, Globals, Namespaces, Stored Procedures, plus custom fields where InterSystems IRIS exposes them. On the OpenSearch side: Index templates, Ingest pipelines, Data streams, Snapshots. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for InterSystems IRIS and OpenSearch: Regional or environment copies; Cross-engine sync; Migration with zero-downtime cutover. Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. OpenSearch: REST API over HTTP(S) with JSON payloads. Authentication: Basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service. Stacksync manages authentication, retries, and rate limits on both sides.
InterSystems IRIS: Data is partitioned by namespaces mapped to databases, so a sync connection's namespace determines exactly which tables are visible. OpenSearch: Index templates and data streams control how time-series records are routed, which affects where synced events should land. Stacksync's field mapping accounts for these differences between InterSystems IRIS and OpenSearch without custom code.
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 InterSystems IRIS and OpenSearch.