Two-way sync
Changes in Apache Druid or MySQL instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid 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.
Operational databases and analytical warehouses want the same data at different moments. Analysts want MySQL's rows in Apache Druid, 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 MySQL where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in MySQL sync into Apache Druid in real time, and result tables in Apache Druid sync back into MySQL, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Apache Druid and keep MySQL focused on its operational workload.
Rows from MySQL land in Apache Druid as they change, replacing hand-built CDC and batch extract jobs.
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.
| Apache Druid objects | MySQL objects | |
|---|---|---|
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | JSON Columns Validated semi-structured payloads for nested SaaS data. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Stored Procedures Server-side logic that can post-process synced rows. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Tables The primary sync target; rows map to records in connected systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–MySQL connection.
Changes in Apache Druid or MySQL instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or MySQL data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Apache Druid or MySQL record.
Track your Apache Druid ⇄ MySQL sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and MySQL.
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 Apache Druid 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.
Pick the Apache Druid 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.
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 Apache Druid and MySQL: authenticate both systems, choose the objects to sync (such as Apache Druid's Metrics and Ingestion Supervisors), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. 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 Apache Druid side: Tasks, Datasources, Segments, Dimensions, plus custom fields where Apache Druid exposes them. On the MySQL side: JSON Columns, Stored Procedures, Triggers, Databases (Schemas). 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 Apache Druid and MySQL: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Apache Druid: REST API (SQL over HTTP and native JSON queries); JDBC via Avatica. Authentication: Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy. MySQL: 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). 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 Apache Druid and MySQL.