TiDB Best Practices

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiDB 最佳实践 Best Practice

| username: Billmay表妹

TiDB best practice is based on the successful cases extracted from many customer practices to optimize the use of TiDB guidance to help better understand our products and solutions, reduce the threshold to get started while meeting customer self-service needs. Can be sent out directly

  1. Real-time data warehouse based on TiDB and Flink
  1. Best practices for developing applications with TiDB
  1. TiDB best practices
  2. Java app best practices
  3. Haproxy best practices
  4. High concurrency best practices
  5. Grafana monitor best practices
  6. PD scheduling best practices
  7. Massive regions best practices
  8. Three nodes hybrid deployment
  9. Bidirectional replication between clusters
  10. Lossless upgrade of TiDB cluster
  11. TiDB on Kubernetes best practice
  12. Heterogeneous database replication best practice
2
| username: 数据小黑 | Original post link

The resource center is becoming more and more abundant.

3
| username: Billmay表妹 | Original post link

Keep up the good work, little mover!