Real-time
Two-way sync
Changes in Citus or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to InterSystems IRIS integration — real-time, two-way sync
Keep Citus 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Citus and InterSystems IRIS
Keep Citus and InterSystems IRIS synchronized in real time, across engines, regions, or services, in one or both directions.
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 Citus 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.
Common use cases
- 01 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 02 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 03 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
- 04 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
Common sync patterns
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between Citus and InterSystems IRIS
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.
| Citus objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Schemas Schema organization scopes which tables a sync connection can see. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Views SQL views expose curated slices of data for outbound replication. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Local tables is specific to Citus and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Sequences is specific to Citus and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Distributed tables is specific to Citus and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Reference tables is specific to Citus and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. |
How changes propagate between Citus and InterSystems IRIS
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.
Citus InterSystems IRIS Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
InterSystems IRIS Citus Interval-based propagation
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 applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Citus ⇄ InterSystems IRIS
Connect Citus and InterSystems IRIS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–InterSystems IRIS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Citus or InterSystems IRIS record.
Observability
Monitoring
Track your Citus ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and InterSystems IRIS.
How the Citus and InterSystems IRIS connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published API rate limits
How it works
How to connect Citus to InterSystems IRIS — three steps, no code
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.
- 01
Connect your apps
Authenticate Citus 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.
Citus
connected
InterSystems IRIS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus 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.
objects · Citus ⇄ InterSystems IRISCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus InterSystems IRISCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and InterSystems IRIS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Citus's Schemas and Views), 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 Citus and InterSystems IRIS: Migration with zero-downtime cutover; Shared reference data between services; Regional or environment copies. When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). 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.
-
Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. 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 Citus 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 Citus and InterSystems IRIS records are not retained after a sync operation.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 392 integrations available for Citus and InterSystems IRIS.
Popular · 8 of 392
-
Citus ⇄ Firebase -
Citus ⇄ SingleStore -
Citus ⇄ Amazon Aurora -
Citus ⇄ Amazon Lightsail -
InterSystems IRIS ⇄ Redis Enterprise -
InterSystems IRIS ⇄ SAP ASE (Sybase) -
InterSystems IRIS ⇄ Scaleway Postgres -
InterSystems IRIS ⇄ TiDB
No integrations match .
