Two-way sync
Changes in Amazon Aurora or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Aurora 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.
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 Amazon Aurora and TiDB 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.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both Amazon Aurora and TiDB, 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.
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.
| Amazon Aurora objects | TiDB objects | |
|---|---|---|
| Schemas Namespaces (PostgreSQL) or database-level grouping (MySQL) used in table selection. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Tables Relational tables synced bi-directionally at row level. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | |
| Views Read-only query-backed sources for downstream syncs. | Views Logical views for shaping reads before syncing outward. | |
| Materialized Views Precomputed result sets (PostgreSQL-compatible clusters) readable as sources. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Columns and Data Types Standard MySQL or PostgreSQL types mapped during field mapping. | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Primary and Foreign Keys Constraints used to identify records and preserve relational integrity in syncs. | Sequences Server-side ID generation relevant when external systems write rows. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon Aurora–TiDB connection.
Changes in Amazon Aurora or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Aurora 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 Amazon Aurora or TiDB record.
Track your Amazon Aurora ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Aurora 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 Amazon Aurora 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 Amazon Aurora 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 Amazon Aurora and TiDB: authenticate both systems, choose the objects to sync (such as Amazon Aurora's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Amazon Aurora: MySQL or PostgreSQL wire protocol (SQL); optional RDS Data API over HTTPS. Authentication: Database credentials or IAM database authentication. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
Amazon Aurora: Aurora separates compute from a shared distributed storage layer that keeps six copies of data across three Availability Zones. TiDB: TiFlash maintains columnar replicas of row data, letting analytical queries run on current data without a separate warehouse. Stacksync's field mapping accounts for these differences between Amazon Aurora and TiDB 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 Amazon Aurora and TiDB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon Aurora and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Aurora–TiDB integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon Aurora and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Amazon Aurora and TiDB.