# `3-DC` Deployment Solution: Optimizations
+ All requests are dispatched to single `DC`, other `DCs` are standby
+ Configure scheduling policy to migrate all `TiKV Region leaders` and `PD leader` to the same `DC`
+ Neither obtaining `TSO` or reading `TiKV Regions` will be impacted by the network latency between `DCs`
+ If the serving `DC` is down, routes business traffic to other functioning `DCs`

------------------------------------------------------------
If there is no need for all data centers to provide external services at the same time, all business traffic can be distributed to one data center, and both the `region leader` and `PD leader` can be migrated to the same data center through a scheduling strategy (we also made this optimization in the tests described above). 

This way, whether obtaining `TSO` from `PD` or reading `region` data, is unaffected by the `inter data center` network. When the data center fails, the `PD leader` and `region leader` are automatically selected from other data centers, then you can route business traffics to other surviving data centers.