Real-time
Two-way sync
Changes in InterSystems IRIS or MySQL instantly reflect in both systems. No stale data, no manual imports.
Database
InterSystems IRIS to MySQL integration — real-time, two-way sync
Keep InterSystems IRIS and MySQL 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 InterSystems IRIS and MySQL
Keep InterSystems IRIS and MySQL 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 InterSystems IRIS and MySQL 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 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
- 03 Feed a warehouse from MySQL continuously using binlog-based capture instead of nightly dumps
- 04 Two-way sync between a MySQL application database and a CRM so operational records and sales records stay identical
Common sync patterns
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.
Cross-engine sync
Keep the same dataset live in both InterSystems IRIS and MySQL, so each workload runs on the engine that suits it.
What you can sync between InterSystems IRIS and MySQL
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 | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Tables The primary sync target; rows map to records in connected systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views SQL views expose curated slices of data for outbound replication. | Views Read-side projections used as outbound sync sources. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Stored Procedures Server-side logic that can post-process synced rows. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Persistent Classes is specific to InterSystems IRIS and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Columns Field-level mapping targets with engine-typed values. | Globals is specific to InterSystems IRIS and Columns to MySQL — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Namespaces is specific to InterSystems IRIS and Primary and Unique Keys to MySQL — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS and MySQL
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.
InterSystems IRIS MySQL 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 MySQL as a row-level write, with types converted between the two schemas.
MySQL InterSystems IRIS Sub-second propagation
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
DeliveryEach detected change is applied to InterSystems IRIS 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.
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with InterSystems IRIS ⇄ MySQL
Connect InterSystems IRIS and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS or MySQL 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 InterSystems IRIS or MySQL record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ MySQL sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and MySQL.
How the InterSystems IRIS and MySQL connectors work
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
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect InterSystems IRIS to MySQL — 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 InterSystems IRIS and MySQL with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
InterSystems IRIS
connected
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS and MySQL 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 · InterSystems IRIS ⇄ MySQLCustomers 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.
InterSystems IRIS MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and MySQL: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Tables and Views), 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 MySQL 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 MySQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–MySQL integration in-house.
-
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and MySQL. 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 MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). 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: Stored Procedures, Tables, Views, Schemas, plus custom fields where InterSystems IRIS exposes them. On the MySQL side: Primary and Unique Keys, JSON Columns, Stored Procedures, Triggers. Stacksync auto-detects both schemas and converts types between the two systems.
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
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 507 integrations available for InterSystems IRIS and MySQL.
Popular · 6 of 507
-
InterSystems IRIS ⇄ TiDB -
InterSystems IRIS ⇄ VoltDB -
MySQL ⇄ MongoDB -
MySQL ⇄ CockroachDB -
MySQL ⇄ Google AlloyDB -
MySQL ⇄ Dynamo DB
No integrations match .
