Two-way sync
Changes in Rockset or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Rockset and TiDB 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 TiDB's rows in Rockset, 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 TiDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in TiDB sync into Rockset in real time, and result tables in Rockset sync back into TiDB, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Rockset sync into TiDB, 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 Rockset and keep TiDB 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.
| Rockset objects | TiDB objects | |
|---|---|---|
| Workspaces Namespaces that group collections and query lambdas per team or environment. | Views Logical views for shaping reads before syncing outward. | |
| Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Aliases Stable names that point at collections, used to swap datasets without changing queries. | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Integrations Managed source connections (databases, streams, object storage) feeding collections. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Virtual Instances Isolated compute units that separate ingest from query workloads. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Collections Schemaless document containers that ingested and synced records land in. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rockset–TiDB connection.
Changes in Rockset or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rockset or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Rockset or TiDB record.
Track your Rockset ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rockset and TiDB.
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 Rockset and TiDB 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 Rockset and TiDB 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 Rockset and TiDB: authenticate both systems, choose the objects to sync (such as Rockset's Workspaces and Query Lambdas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Rockset: Polling via SQL queries on timestamp fields; ingestion-side change capture is handled by Rockset's managed source connectors. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Rockset side: Query Lambdas, Aliases, Integrations, Virtual Instances, plus custom fields where Rockset exposes them. On the TiDB side: Databases, Tables, Views, Columns. 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 Rockset and TiDB: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in Rockset sync into TiDB, where whatever reads from that database gets them without querying the warehouse.
Rockset: REST API (SQL over HTTP, plus a document Write API). Authentication: API key. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). 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 Rockset and TiDB.