Two-way sync
Changes in Apache Cassandra or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Cassandra 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 Apache Cassandra 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.
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.
Keep the same dataset live in both Apache Cassandra and InterSystems IRIS, so each workload runs on the engine that suits it.
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 Cassandra objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Tables Wide-column tables addressed by partition key, the unit of row-level sync. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| User-Defined Types Composite column types that syncs must flatten or map to structured fields. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | User-Defined Types is specific to Apache Cassandra and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Collections List, set, and map columns handled with type-aware field mapping. | Views SQL views expose curated slices of data for outbound replication. | Collections is specific to Apache Cassandra and Views to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Counters Increment-only counter columns, usually read-only in syncs. | Schemas Schema organization scopes which tables a sync connection can see. | Counters is specific to Apache Cassandra and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Keyspaces Top-level namespaces with replication settings that scope a sync connection. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Keyspaces is specific to Apache Cassandra and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Partitions and Rows Records located by partition and clustering keys during reads and upserts. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Partitions and Rows is specific to Apache Cassandra and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionChanges in Apache Cassandra are captured at the source via change data capture — no polling loop against its API. Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
DeliveryEach detected change is written to Apache Cassandra through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Cassandra–InterSystems IRIS connection.
Changes in Apache Cassandra or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Cassandra 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 Cassandra or InterSystems IRIS record.
Track your Apache Cassandra ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Cassandra 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 Cassandra 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 Cassandra 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 Cassandra and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Apache Cassandra's Tables and User-Defined Types), 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 Apache Cassandra and InterSystems IRIS: Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Apache Cassandra: CQL over the Cassandra native binary protocol. Authentication: Database credentials (password authenticator); TLS and role-based grants where configured. 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 Cassandra: Every write carries a timestamp (writetime) per cell, which integrations can use for incremental extraction and conflict resolution. InterSystems IRIS: IRIS is multi-model: the same stored data can be accessed as relational tables via SQL, as persistent objects, and as multidimensional globals, so integrations usually standardize on the SQL projection. Stacksync's field mapping accounts for these differences between Apache Cassandra 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 Cassandra and InterSystems IRIS 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 392 integrations available for Apache Cassandra and InterSystems IRIS.