Two-way sync
Changes in InterSystems IRIS or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and TimescaleDB 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 TimescaleDB 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 TimescaleDB, 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 | TimescaleDB objects | How this pairing syncs | |
|---|---|---|---|
| Views SQL views expose curated slices of data for outbound replication. | Views Standard SQL views used to shape or filter data for consumers. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | Globals is specific to InterSystems IRIS and Continuous Aggregates to TimescaleDB — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | Namespaces is specific to InterSystems IRIS and Regular PostgreSQL Tables to TimescaleDB — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | Stored Procedures is specific to InterSystems IRIS and Hypertables to TimescaleDB — each maps to any object or custom field on the other side. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | Tables is specific to InterSystems IRIS and Chunks to TimescaleDB — 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.
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 TimescaleDB as a row-level write, with types converted between the two schemas.
DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–TimescaleDB connection.
Changes in InterSystems IRIS or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or TimescaleDB 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 TimescaleDB record.
Track your InterSystems IRIS ⇄ TimescaleDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and TimescaleDB.
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 TimescaleDB 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 TimescaleDB 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 TimescaleDB: 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.
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 TimescaleDB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed InterSystems IRIS and TimescaleDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–TimescaleDB integration in-house.
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and TimescaleDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. 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: Tables, Views, Schemas, Persistent Classes, plus custom fields where InterSystems IRIS exposes them. On the TimescaleDB side: Regular PostgreSQL Tables, Views, Schemas, Hypertables. Stacksync auto-detects both schemas and converts types between the two systems.
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 InterSystems IRIS and TimescaleDB.