Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 642 5.3.3 PD Microservice Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · 645 5.3.4 TiProxy Deployment TiUP supports deploying PD microservices #5766 @rleungx Starting from v8.0.0, PD supports the microservice mode. This mode splits the times- tamp allocation and cluster scheduling functions of PD into 2.0, PD microservices can also be deployed using TiUP. You can deploy the tso microservice and the scheduling microservice separately in a cluster to enhance PD performance scalability and address PD performance

Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 731 5.3.3 PD Microservice Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · 734 5.3.4 TiProxy Deployment as a relative path, the cluster will be deployed in the home directory of the user. 5.3.3 PD Microservice Deployment Topology This document describes the deployment topology of PD microservices based port Global directory configuration 734 5.3.3.1.1 Topology template Simple template for the PD microservice topology ### # Global variables are applied to all deployments and used as the �→ default value

Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 645 5.3.3 PD Microservice Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · 648 5.3.4 TiProxy Deployment @JmPotato • Fix the issue that the scaling progress is displayed incorrectly after the scheduling microservice is enabled #8331 @rleungx • Fix the issue that the encryption manager is not initialized before as a relative path, the cluster will be deployed in the home directory of the user. 5.3.3 PD Microservice Deployment Topology This document describes the deployment topology of PD microservices based

Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 726 5.3.3 PD Microservice Deployment Topology · · · · · · · · · · · · · · · · · · · · · · · · · · · 729 5.3.4 TiProxy Deployment as a relative path, the cluster will be deployed in the home directory of the user. 5.3.3 PD Microservice Deployment Topology This document describes the deployment topology of PD microservices based port Global directory configuration 729 5.3.3.1.1 Topology template Simple template for the PD microservice topology ### # Global variables are applied to all deployments and used as the �→ default value

ms-3 K8s Pod TLS only ● App with multiple microservices ● external Redis TLS only ● each microservice talks to Redis 1. Tedious configuration in the application 2. Improved visibility into Redis

details 2.2.1.1 Scalability • PD supports the microservice mode (experimental) #5766 @binshi-bing Starting from v8.0.0, PD supports the microservice mode. This mode splits the times- tamp allocation bottlenecks of PD in large-scale clusters. • tso microservice: provides monotonically increasing timestamp allocation for the entire cluster. • scheduling microservice: provides scheduling functions for the entire repair, and replica placement. Each microservice is deployed as an independent process. If you configure more than one replica for a microservice, the microservice automatically implements a primary-secondary

corrupt data #16705 @Connor1996 • PD • Fix the issue that TSO might get stuck when toggling the PD microservice mode on and off #7849 @JmPotato • Fix the issue that the State monitoring metric for DR Auto-Sync execution, see SQL FAQ - DDL execution. 12.10 PD Microservices Starting from v8.0.0, PD supports the microservice mode, which splits the timestamp al- location and cluster scheduling functions of PD into the the routing service for metadata. • tso microservice: provides monotonically increasing timestamp allocation for the entire cluster. • scheduling microservice: provides scheduling functions for the entire

corrupt data #16705 @Connor1996 • PD • Fix the issue that TSO might get stuck when toggling the PD microservice mode on and off #7849 @JmPotato • Fix the issue that the State monitoring metric for DR Auto-Sync execution, see SQL FAQ - DDL execution. 12.10 PD Microservices Starting from v8.0.0, PD supports the microservice mode, which splits the timestamp al- location and cluster scheduling functions of PD into the the routing service for metadata. • tso microservice: provides monotonically increasing timestamp allocation for the entire cluster. • scheduling microservice: provides scheduling functions for the entire

to consider using io.seata.core.context.RootContext.getXID() in the con‐ text of the starting microservice to obtain the Seata XID and then pass it to the ending microser‐ vice through RPC, and call io io.seata.core.context.RootContext.bind(rpcXid) in the business function of the endpoint microservice. 2. In the scenario of using ShardingSphere Proxy, Multiple microservices operate local transactions