Discuss the Operations Management System of TiDB under Microservices

Translated
1

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

Original topic: 谈谈Tidb在微服务下的运维管理体系

| username: 近墨者zyl

Under the architecture of microservice applications, the underlying layer is a large TiDB cluster DB service. How should the operation and maintenance management system be constructed? TiDB does not have the concept of tenants. Is it corresponding to microservices through the form of schemas, or in what way? How should the operation and maintenance system be constructed from the upper-layer microservice applications (container cloud) to the middleware, and then to the database TiDB cluster layer?

2
| username: tidb狂热爱好者 | Original post link

TiDB doesn’t have an operations system, haha. Horizontal scaling, tree-like scaling, comprehensive monitoring, no need to worry series.

3
| username: LuoBlack | Original post link

Shouldn’t each microservice correspond to an independent database cluster? If they correspond to a large TiDB cluster, it will inevitably cause performance interference between services at the database level.

4
| username: LuoBlack | Original post link

To manage multiple clusters, you can consider using this platform TiEM

5
| username: 近墨者zyl | Original post link

It’s too wasteful to have separate database clusters.

6
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.