Two-way sync
Changes in InterSystems IRIS or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and VoltDB 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 VoltDB 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 VoltDB, 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 | VoltDB objects | |
|---|---|---|
| Views SQL views expose curated slices of data for outbound replication. | Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Stored Procedures Precompiled transactional units that serve as the primary write interface. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Materialized Views Synchronously maintained aggregates over tables, useful as pre-computed read sources. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Streams Insert-only constructs that feed the export subsystem with committed rows. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–VoltDB connection.
Changes in InterSystems IRIS or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or VoltDB 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 VoltDB record.
Track your InterSystems IRIS ⇄ VoltDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and VoltDB.
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 VoltDB 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 VoltDB 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 VoltDB: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Views and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 VoltDB: 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. VoltDB: SQL over JDBC plus native client libraries and an HTTP/JSON interface. Authentication: Database credentials. 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. VoltDB: Transactions execute as stored procedures run serially within each partition, which removes locking for single-partition work. Stacksync's field mapping accounts for these differences between InterSystems IRIS and VoltDB 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 InterSystems IRIS and VoltDB records are not retained after a sync operation.
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 VoltDB.