Two-way sync
Changes in ClickHouse or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep ClickHouse 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.
Operational databases and analytical warehouses want the same data at different moments. Analysts want InterSystems IRIS's rows in ClickHouse, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in InterSystems IRIS where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in InterSystems IRIS sync into ClickHouse in real time, and result tables in ClickHouse sync back into InterSystems IRIS, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in ClickHouse sync into InterSystems IRIS, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in ClickHouse and keep InterSystems IRIS focused on its operational workload.
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.
| ClickHouse objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Views Saved queries used as curated, 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. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Tables (MergeTree family) is specific to ClickHouse and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Databases Namespaces that group tables and scope permissions for sync users. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Databases is specific to ClickHouse and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Materialized views is specific to ClickHouse and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Schemas Schema organization scopes which tables a sync connection can see. | Distributed tables is specific to ClickHouse and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Dictionaries is specific to ClickHouse and Persistent Classes 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.
DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.
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 applied to ClickHouse as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–InterSystems IRIS connection.
Changes in ClickHouse or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever ClickHouse 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 ClickHouse or InterSystems IRIS record.
Track your ClickHouse ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between ClickHouse 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 ClickHouse 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 ClickHouse 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 ClickHouse and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as ClickHouse's Views and Tables (MergeTree family)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for ClickHouse and InterSystems IRIS: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in ClickHouse sync into InterSystems IRIS, where whatever reads from that database gets them without querying the warehouse.
ClickHouse: Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available. Authentication: Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS. 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.
ClickHouse: It exposes both a native TCP protocol and an HTTP interface, and can additionally speak MySQL and PostgreSQL wire protocols for compatibility with existing drivers. 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 ClickHouse 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 ClickHouse and InterSystems IRIS records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed ClickHouse and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom ClickHouse–InterSystems IRIS integration in-house.
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 ClickHouse and InterSystems IRIS.