- TiDB on EKS - TiDB Deployment on EKS(Cluster/Monitoring/Dashboard/Online Diag)
- TiDB to Oracle(MSK/Glue) - Data replication from TiDB to Oracle through TiCDC, MSK(confluent jdbc sink) and Glue schema registry
- TiDB to Oracle(S3) - Data replication from TiDB to Oracle through TiCDC, S3 (CSV files)
- TiDB to Postgres - Data replication from TiDB to Postgres through TiCDC and kafka(debezium source and confluent jdbc sink)
- TiDB to Elasticsearch - Data replication from TiDB to Elasticsearch through TiCDC and kafka(debezium sink)
- TiDB to Elasticsearch(MSK/Glue) - Data replication from TiDB to Elasticsearch through TiCDC, MSK(debezium sink) and Glue schema registry
- TiDB to Redshift - Data replication from TiDB to redshift through TiCDC, Kafka(confluent redshift)
- TiDB to Redshift(MSK/Glue) - Data replication from TiDB to redshift through TiCDC, MSK(confluent redshift) and Glue schema registry
- Mongo to TiDB - Data replication from MongoDB to TiDB through kafka(debezium mongo source and customized jdbc sink)
- Aurora to TiDBCloud - Data replication from Aurora to TiDB through DM
- Aurora to TiDBCloud with TiDB Cloud API- Data replication from Aurora to TiDB through DM with TiDB Cloud API which makes the process much more easy
- MySQL to TiDBCloud - Data migration from MySQL on EC2 to TiDB Cloud which use DM on cloud
- TiDB data transfer to S3 with Glue ETL - Use Glue ETL to transfer the data from TiDB to AWS S3.
- Count performance tuning - Performance tuning for table count
- transferdb ddl conversion - Data conversion from oracle to mysql document. Please refer to transferdb
- Low latency during heavy batch - TiKV nodes isolation between batch and online transaction
- Resource control to improve latency during heavy batch - Resource control between batch and online transaction to reduce impact to online [batch: insert/select, dumpling]