From 9447aa1daeb25b045346905c155668c4b80536f4 Mon Sep 17 00:00:00 2001 From: binbin <83755740+binbinlv@users.noreply.github.com> Date: Fri, 12 Nov 2021 19:13:11 +0800 Subject: [PATCH] [skip ci] Improve design doc (#11749) Signed-off-by: Binbin Lv --- docs/design_docs/proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/proxy.md b/docs/design_docs/proxy.md index b6327928c4..5cc8fea819 100644 --- a/docs/design_docs/proxy.md +++ b/docs/design_docs/proxy.md @@ -206,7 +206,7 @@ all components on multiple nodes. In Milvus Standalone, the interaction between between functions or communication between Grpc. The log system can be either Pulsar or RocksDb. In Milvus Cluster, the communication between components is mostly undertaken by grpc, and the message flow is mostly by Pulsar. -Therefore, in the original design, Milvus2.0 decoupled the core function of the component and the communication between +Therefore, in the original design, Milvus 2.0 decoupled the core function of the component and the communication between components. Taking Proxy as an example, the core function of the Proxy component is determined and has nothing to do with the deployment form. In the project's internal/proxy directory, it contains the functions of the core components of Proxy; and internal/distributed/proxy contains the core functions of Proxy in the deployment of cluster distributed