Two-way sync
Changes in InterSystems IRIS or PostgreSQL instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and PostgreSQL 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 PostgreSQL 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.
Keep the same dataset live in both InterSystems IRIS and PostgreSQL, 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.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
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 | PostgreSQL objects | |
|---|---|---|
| Schemas Schema organization scopes which tables a sync connection can see. | Views Read-side projections used to expose joined or filtered data to a sync. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Materialized Views Precomputed result sets synced outward on a refresh schedule. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Schemas Namespaces that scope which tables a sync reads and writes. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Columns Field-level mapping targets; types are mapped to the connected system's field types. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–PostgreSQL connection.
Changes in InterSystems IRIS or PostgreSQL instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or PostgreSQL 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 PostgreSQL record.
Track your InterSystems IRIS ⇄ PostgreSQL sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and PostgreSQL.
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 PostgreSQL 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 PostgreSQL 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 PostgreSQL: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Schemas and Persistent Classes), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On PostgreSQL: Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the InterSystems IRIS side: Namespaces, Stored Procedures, Tables, Views, plus custom fields where InterSystems IRIS exposes them. On the PostgreSQL side: Custom Types and Enums, Tables, Views, Materialized Views. 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 PostgreSQL: Cross-engine sync; Migration with zero-downtime cutover; Shared reference data between services. Keep the same dataset live in both InterSystems IRIS and PostgreSQL, so each workload runs on the engine that suits it.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. PostgreSQL: SQL wire protocol (PostgreSQL frontend/backend protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user. Stacksync manages authentication, retries, and rate limits on both sides.
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 PostgreSQL.