This is an automated email from the ASF dual-hosted git repository. liujun pushed a commit to branch mkdocs in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
commit 69e63bf2c45b9f0f43acac8736bfe6fd79816143 Author: ken.lj <[email protected]> AuthorDate: Thu Oct 22 17:15:42 2020 +0800 update en doc links --- en-us/blog/dubbo-101.md | 6 +++--- en-us/blog/dubbo-new-async.md | 2 +- en-us/blog/dubboAsync_server.md | 2 +- en-us/developers/committer-guide/new-committer-guide_dev.md | 4 ++-- en-us/docs/2.7/user/demos/config-connections.md | 2 +- en-us/docs/2.7/user/demos/logger-strategy.md | 2 +- en-us/docs/2.7/user/demos/multi-registry.md | 2 +- en-us/docs/2.7/user/demos/result-cache.md | 2 +- en-us/docs/2.7/user/demos/routing-rule.md | 2 +- en-us/docs/2.7/user/demos/service-container.md | 2 +- en-us/docs/2.7/user/references/metadata/introduction.md | 4 ++-- en-us/docs/2.7/user/references/registry/redis.md | 2 +- en-us/docs/2.7/user/references/telnet.md | 2 +- en-us/docs/3.0/user/demos/config-connections.md | 2 +- en-us/docs/3.0/user/demos/logger-strategy.md | 2 +- en-us/docs/3.0/user/demos/multi-registry.md | 2 +- en-us/docs/3.0/user/demos/result-cache.md | 2 +- en-us/docs/3.0/user/demos/routing-rule.md | 2 +- en-us/docs/3.0/user/demos/service-container.md | 2 +- en-us/docs/3.0/user/references/metadata/introduction.md | 4 ++-- en-us/docs/3.0/user/references/registry/redis.md | 2 +- en-us/docs/3.0/user/references/telnet.md | 2 +- zh-cn/docs/2.7/user/demos/simplify-registry-data.md | 4 ++-- zh-cn/docs/2.7/user/references/metadata/introduction.md | 4 ++-- zh-cn/docs/3.0/user/demos/simplify-registry-data.md | 4 ++-- zh-cn/docs/3.0/user/references/metadata/introduction.md | 4 ++-- 26 files changed, 35 insertions(+), 35 deletions(-) diff --git a/en-us/blog/dubbo-101.md b/en-us/blog/dubbo-101.md index 41f42b7..8ad331d 100644 --- a/en-us/blog/dubbo-101.md +++ b/en-us/blog/dubbo-101.md @@ -385,6 +385,6 @@ Eventually, we give an outline of how to create a Dubbo application quickly base --- 1. [Getting Started Using JavaTM RMI](https://docs.oracle.com/javase/6/docs/technotes/guides/rmi/hello/hello-world.html) -2. [Explicit target](http://dubbo.apache.org/en-us/docs/user/demos/explicit-target.html) -3. [Multicast Registry](http://dubbo.apache.org/en-us/docs/user/references/registry/multicast.html) -4. [Online QOS command](http://dubbo.apache.org/en-us/docs/user/references/qos.html) +2. [Explicit target](../docs/2.7/user/demos/explicit-target.md) +3. [Multicast Registry](../docs/2.7/user/references/registry/multicast.md) +4. [Online QOS command](../docs/2.7/user/references/qos.md) diff --git a/en-us/blog/dubbo-new-async.md b/en-us/blog/dubbo-new-async.md index 7ff16da..13d4215 100644 --- a/en-us/blog/dubbo-new-async.md +++ b/en-us/blog/dubbo-new-async.md @@ -11,7 +11,7 @@ Implementing the full asynchronous programming based on Dubbo, which is a new fe ## Asynchronous mode before version 2.6.x -Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including [Asynchronous Call](../docs/2.7/user/demos/async-call.md), [Parameter Callback](../docs/2.7/user/demos/callback-parameter.md) and [Event Notification](../docs/2.7/user/demos/events-notify.html) on Consumer side. There are some brief introductions to the usage and Demo in the above document links. +Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including [Asynchronous Call](../docs/2.7/user/demos/async-call.md), [Parameter Callback](../docs/2.7/user/demos/callback-parameter.md) and [Event Notification](../docs/2.7/user/demos/events-notify.md) on Consumer side. There are some brief introductions to the usage and Demo in the above document links. But the current asynchronous method has the following problems: diff --git a/en-us/blog/dubboAsync_server.md b/en-us/blog/dubboAsync_server.md index 8284cf2..ae48b6d 100644 --- a/en-us/blog/dubboAsync_server.md +++ b/en-us/blog/dubboAsync_server.md @@ -7,7 +7,7 @@ description: Implementation background and practice of Dubbo server asynchronous # Implementation background and practice of Dubbo server asynchronous interface ## Preface -It is suggested to make an understanding of the thread phase involved in the process of Dubbo first, please refer to [Implementation background and practice of Dubbo client asynchronous interface](http://dubbo.apache.org/en-us/blog/dubboAsync_client.html) for details. +It is suggested to make an understanding of the thread phase involved in the process of Dubbo first, please refer to [Implementation background and practice of Dubbo client asynchronous interface](./dubboAsync_client.md) for details. ## Implementation background It is necessary to introduce the server-side thread strategy in more detail to deepen the user's judgment basis for selecting server-side asynchrony. It is also necessary to introduce coroutines, the "secret weapon" often used in server-side asynchrony. diff --git a/en-us/developers/committer-guide/new-committer-guide_dev.md b/en-us/developers/committer-guide/new-committer-guide_dev.md index 867c72e..5266fdc 100644 --- a/en-us/developers/committer-guide/new-committer-guide_dev.md +++ b/en-us/developers/committer-guide/new-committer-guide_dev.md @@ -82,9 +82,9 @@ If not discussed in the community (mailing list), just as it did not happen. ### Add your name -Please update Dubbo incubator status [page](https://incubator.apache.org/projects/dubbo.html) to add your name. See this [guide](http://dubbo.apache.org/en-us/docs/developers/committer-guide/apache-dubbo-page_dev.html) for instructions. +Please update Dubbo incubator status [page](https://incubator.apache.org/projects/dubbo.html) to add your name. See this [guide](./apache-dubbo-page_dev.md) for instructions. -Please update Dubbo offiical [website](http://dubbo.apache.org/en-us/docs/developers/developers_dev.html) to update your name. +Please update Dubbo offiical [website](../docs/2.7/developers/developers_dev.md) to update your name. ### A small benefit diff --git a/en-us/docs/2.7/user/demos/config-connections.md b/en-us/docs/2.7/user/demos/config-connections.md index b2603c9..78860a3 100644 --- a/en-us/docs/2.7/user/demos/config-connections.md +++ b/en-us/docs/2.7/user/demos/config-connections.md @@ -25,6 +25,6 @@ OR ``` **NOTE:** If used default protocol(`dubbo` protocol), and the value of `connections` attribute is great than 0,then each service reference will has itself connection,else all service which belong to same remote server will share only one connection. In this framework,we called `private` connection or `share` connection. -If `<dubbo:service>` and `<dubbo:reference>` are both configured accepts/connections,`<dubbo:reference>` is preferred,Ref to [Configuration coverage strategy](http://dubbo.apache.org/en-us/docs/user/configuration/xml.html). +If `<dubbo:service>` and `<dubbo:reference>` are both configured accepts/connections,`<dubbo:reference>` is preferred,Ref to [Configuration coverage strategy](../configuration/xml.md). * : Because connection is connect on Server,so configure at Provider. diff --git a/en-us/docs/2.7/user/demos/logger-strategy.md b/en-us/docs/2.7/user/demos/logger-strategy.md index 885d9cb..7bbc994 100644 --- a/en-us/docs/2.7/user/demos/logger-strategy.md +++ b/en-us/docs/2.7/user/demos/logger-strategy.md @@ -20,4 +20,4 @@ <dubbo:application logger="log4j" /> ``` -[^1]: Custom Extensions[logger-adapter](http://dubbo.apache.org/en-us/docs/dev/impls/logger-adapter.html) +[^1]: Custom Extensions[logger-adapter](../../dev/impls/logger-adapter.md) diff --git a/en-us/docs/2.7/user/demos/multi-registry.md b/en-us/docs/2.7/user/demos/multi-registry.md index 6d7e872..0acbe8b 100644 --- a/en-us/docs/2.7/user/demos/multi-registry.md +++ b/en-us/docs/2.7/user/demos/multi-registry.md @@ -80,4 +80,4 @@ When testing, the service needs to be temporarily register to two registries, wh </beans> ``` -[^1]: custom registry, see：[registry extension](http://dubbo.apache.org/en-us/docs/dev/impls/registry.html) +[^1]: custom registry, see：[registry extension](../../dev/impls/registry.md) diff --git a/en-us/docs/2.7/user/demos/result-cache.md b/en-us/docs/2.7/user/demos/result-cache.md index 140cfa7..f85d7a8 100644 --- a/en-us/docs/2.7/user/demos/result-cache.md +++ b/en-us/docs/2.7/user/demos/result-cache.md @@ -8,7 +8,7 @@ Cache Result [^1] is used to speed up access to popular data. Dubbo provides dec * `threadlocal` The current thread cache. For example, a page have a lot of portal and each portal need to check user information, you can reduce this redundant visit with this cache. * `jcache` integrate with [JSR107](http://jcp.org/en/jsr/detail?id=107%27) , you can bridge a variety of cache implementation。 -Caching type can be extended，refer to：[Cache extension](http://dubbo.apache.org/en-us/docs/dev/impls/cache.html) +Caching type can be extended，refer to：[Cache extension](../../docs/2.7/dev/impls/cache.md) ## Configuration diff --git a/en-us/docs/2.7/user/demos/routing-rule.md b/en-us/docs/2.7/user/demos/routing-rule.md index 2aca5ee..c01d4a0 100644 --- a/en-us/docs/2.7/user/demos/routing-rule.md +++ b/en-us/docs/2.7/user/demos/routing-rule.md @@ -187,7 +187,7 @@ The scope of the `request.tag` is for each invocation, using the attachment to p [^1]: Support since `2.2.0` -[^2]: Routing Rules Extension Point: [Route Extension](http://dubbo.apache.org/en-us/docs/dev/impls/router.html) +[^2]: Routing Rules Extension Point: [Route Extension](../../dev/impls/router.md) [^3]: Note: A service can only have one whitelist rule, otherwise the two rules will be filtered out. [^4]: Note: Scripts have no sandbox constraints, can execute arbitrary code, and poses a backdoor risk. [^5]: Support since `2.7.0` diff --git a/en-us/docs/2.7/user/demos/service-container.md b/en-us/docs/2.7/user/demos/service-container.md index b825538..5e8aa3e 100644 --- a/en-us/docs/2.7/user/demos/service-container.md +++ b/en-us/docs/2.7/user/demos/service-container.md @@ -4,7 +4,7 @@ The service container is a standalone launcher because the backend service does The service container is just a simple Main method and loads a simple Spring container to expose the service. -The content of Service container can be extended, built-in spring, jetty, log4j etc.. This can be expanded with [Container Extension Points](http://dubbo.apache.org/en-us/docs/dev/impls/container.html). Configure it with the -D parameter in the java command or `dubbo.properties`. +The content of Service container can be extended, built-in spring, jetty, log4j etc.. This can be expanded with [Container Extension Points](../../dev/impls/container.md). Configure it with the -D parameter in the java command or `dubbo.properties`. ## Container type diff --git a/en-us/docs/2.7/user/references/metadata/introduction.md b/en-us/docs/2.7/user/references/metadata/introduction.md index 48cd2fa..18605ee 100644 --- a/en-us/docs/2.7/user/references/metadata/introduction.md +++ b/en-us/docs/2.7/user/references/metadata/introduction.md @@ -1,6 +1,6 @@ # Background -There are close to [30 configurations](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html) in dubbo provider. Excluding registry center governance requirements, a large part of configurations are used by the provider itself and do not need to be delivered to the consumer. This part of the data does not need to be written to the registry, but only needs to be persisted as key-value. -There are also [20+ configurations](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html) in dubbo consumer. In the registry center, only a few configurations such as application, version, group, ip, dubbo version are needed in the list of service consumers. Other configurations can also be persisted in key-value form. +There are close to [30 configurations](../xml/dubbo-service.md) in dubbo provider. Excluding registry center governance requirements, a large part of configurations are used by the provider itself and do not need to be delivered to the consumer. This part of the data does not need to be written to the registry, but only needs to be persisted as key-value. +There are also [20+ configurations](../xml/dubbo-reference.md) in dubbo consumer. In the registry center, only a few configurations such as application, version, group, ip, dubbo version are needed in the list of service consumers. Other configurations can also be persisted in key-value form. This data is registered into the registry in the service dimension, which leads to the expansion of data volume, and then causes the increased network overhead of the registry (such as zookeeper) and decreased performance. In addition to the storage of the above configuration items, Dubbo service metadata information also needs to be stored. Metadata information includes service interface and method information of interface. This information will be used for service mock, service test. diff --git a/en-us/docs/2.7/user/references/registry/redis.md b/en-us/docs/2.7/user/references/registry/redis.md index ac4e16e..615b68f 100644 --- a/en-us/docs/2.7/user/references/registry/redis.md +++ b/en-us/docs/2.7/user/references/registry/redis.md @@ -65,7 +65,7 @@ A home-brewed service registry server is used in Alibaba instead of redis server ## Installation -Pls. refer to [redis install manual](http://dubbo.apache.org/en-us/docs/admin/install/redis.html) for how to install a redis based registry server. To set it up, specify `dubbo.registry.address` to `redis://127.0.0.1:6379` in `conf/dubbo.properties` for both provider and consumer (you can refer to [quick start](../../quick-start.md)) after install a redis server. +Pls. refer to [redis install manual](../../../admin/install/redis.md) for how to install a redis based registry server. To set it up, specify `dubbo.registry.address` to `redis://127.0.0.1:6379` in `conf/dubbo.properties` for both provider and consumer (you can refer to [quick start](../../quick-start.md)) after install a redis server. [^1]: [Redis](http://redis.io) is a high performance KV cache server diff --git a/en-us/docs/2.7/user/references/telnet.md b/en-us/docs/2.7/user/references/telnet.md index 78ffb80..fe0a4eb 100644 --- a/en-us/docs/2.7/user/references/telnet.md +++ b/en-us/docs/2.7/user/references/telnet.md @@ -19,7 +19,7 @@ It is possible to extend command `status` to check more resources, pls. refer to ## Supported Commands The built-in telnet commands are listed below. Furthermore, it is possible to extend telnet commands, pls. refer to -[extend telnet command](http://dubbo.apache.org/en-us/docs/user/references/telnet.html) for more details. +[extend telnet command](./telnet.md) for more details. ### `ls` diff --git a/en-us/docs/3.0/user/demos/config-connections.md b/en-us/docs/3.0/user/demos/config-connections.md index b2603c9..78860a3 100644 --- a/en-us/docs/3.0/user/demos/config-connections.md +++ b/en-us/docs/3.0/user/demos/config-connections.md @@ -25,6 +25,6 @@ OR ``` **NOTE:** If used default protocol(`dubbo` protocol), and the value of `connections` attribute is great than 0,then each service reference will has itself connection,else all service which belong to same remote server will share only one connection. In this framework,we called `private` connection or `share` connection. -If `<dubbo:service>` and `<dubbo:reference>` are both configured accepts/connections,`<dubbo:reference>` is preferred,Ref to [Configuration coverage strategy](http://dubbo.apache.org/en-us/docs/user/configuration/xml.html). +If `<dubbo:service>` and `<dubbo:reference>` are both configured accepts/connections,`<dubbo:reference>` is preferred,Ref to [Configuration coverage strategy](../configuration/xml.md). * : Because connection is connect on Server,so configure at Provider. diff --git a/en-us/docs/3.0/user/demos/logger-strategy.md b/en-us/docs/3.0/user/demos/logger-strategy.md index 885d9cb..7bbc994 100644 --- a/en-us/docs/3.0/user/demos/logger-strategy.md +++ b/en-us/docs/3.0/user/demos/logger-strategy.md @@ -20,4 +20,4 @@ <dubbo:application logger="log4j" /> ``` -[^1]: Custom Extensions[logger-adapter](http://dubbo.apache.org/en-us/docs/dev/impls/logger-adapter.html) +[^1]: Custom Extensions[logger-adapter](../../dev/impls/logger-adapter.md) diff --git a/en-us/docs/3.0/user/demos/multi-registry.md b/en-us/docs/3.0/user/demos/multi-registry.md index 6d7e872..0acbe8b 100644 --- a/en-us/docs/3.0/user/demos/multi-registry.md +++ b/en-us/docs/3.0/user/demos/multi-registry.md @@ -80,4 +80,4 @@ When testing, the service needs to be temporarily register to two registries, wh </beans> ``` -[^1]: custom registry, see：[registry extension](http://dubbo.apache.org/en-us/docs/dev/impls/registry.html) +[^1]: custom registry, see：[registry extension](../../dev/impls/registry.md) diff --git a/en-us/docs/3.0/user/demos/result-cache.md b/en-us/docs/3.0/user/demos/result-cache.md index 140cfa7..641f007 100644 --- a/en-us/docs/3.0/user/demos/result-cache.md +++ b/en-us/docs/3.0/user/demos/result-cache.md @@ -8,7 +8,7 @@ Cache Result [^1] is used to speed up access to popular data. Dubbo provides dec * `threadlocal` The current thread cache. For example, a page have a lot of portal and each portal need to check user information, you can reduce this redundant visit with this cache. * `jcache` integrate with [JSR107](http://jcp.org/en/jsr/detail?id=107%27) , you can bridge a variety of cache implementation。 -Caching type can be extended，refer to：[Cache extension](http://dubbo.apache.org/en-us/docs/dev/impls/cache.html) +Caching type can be extended，refer to：[Cache extension](../../dev/impls/cache.md) ## Configuration diff --git a/en-us/docs/3.0/user/demos/routing-rule.md b/en-us/docs/3.0/user/demos/routing-rule.md index 2aca5ee..c01d4a0 100644 --- a/en-us/docs/3.0/user/demos/routing-rule.md +++ b/en-us/docs/3.0/user/demos/routing-rule.md @@ -187,7 +187,7 @@ The scope of the `request.tag` is for each invocation, using the attachment to p [^1]: Support since `2.2.0` -[^2]: Routing Rules Extension Point: [Route Extension](http://dubbo.apache.org/en-us/docs/dev/impls/router.html) +[^2]: Routing Rules Extension Point: [Route Extension](../../dev/impls/router.md) [^3]: Note: A service can only have one whitelist rule, otherwise the two rules will be filtered out. [^4]: Note: Scripts have no sandbox constraints, can execute arbitrary code, and poses a backdoor risk. [^5]: Support since `2.7.0` diff --git a/en-us/docs/3.0/user/demos/service-container.md b/en-us/docs/3.0/user/demos/service-container.md index b825538..5e8aa3e 100644 --- a/en-us/docs/3.0/user/demos/service-container.md +++ b/en-us/docs/3.0/user/demos/service-container.md @@ -4,7 +4,7 @@ The service container is a standalone launcher because the backend service does The service container is just a simple Main method and loads a simple Spring container to expose the service. -The content of Service container can be extended, built-in spring, jetty, log4j etc.. This can be expanded with [Container Extension Points](http://dubbo.apache.org/en-us/docs/dev/impls/container.html). Configure it with the -D parameter in the java command or `dubbo.properties`. +The content of Service container can be extended, built-in spring, jetty, log4j etc.. This can be expanded with [Container Extension Points](../../dev/impls/container.md). Configure it with the -D parameter in the java command or `dubbo.properties`. ## Container type diff --git a/en-us/docs/3.0/user/references/metadata/introduction.md b/en-us/docs/3.0/user/references/metadata/introduction.md index 48cd2fa..18605ee 100644 --- a/en-us/docs/3.0/user/references/metadata/introduction.md +++ b/en-us/docs/3.0/user/references/metadata/introduction.md @@ -1,6 +1,6 @@ # Background -There are close to [30 configurations](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html) in dubbo provider. Excluding registry center governance requirements, a large part of configurations are used by the provider itself and do not need to be delivered to the consumer. This part of the data does not need to be written to the registry, but only needs to be persisted as key-value. -There are also [20+ configurations](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html) in dubbo consumer. In the registry center, only a few configurations such as application, version, group, ip, dubbo version are needed in the list of service consumers. Other configurations can also be persisted in key-value form. +There are close to [30 configurations](../xml/dubbo-service.md) in dubbo provider. Excluding registry center governance requirements, a large part of configurations are used by the provider itself and do not need to be delivered to the consumer. This part of the data does not need to be written to the registry, but only needs to be persisted as key-value. +There are also [20+ configurations](../xml/dubbo-reference.md) in dubbo consumer. In the registry center, only a few configurations such as application, version, group, ip, dubbo version are needed in the list of service consumers. Other configurations can also be persisted in key-value form. This data is registered into the registry in the service dimension, which leads to the expansion of data volume, and then causes the increased network overhead of the registry (such as zookeeper) and decreased performance. In addition to the storage of the above configuration items, Dubbo service metadata information also needs to be stored. Metadata information includes service interface and method information of interface. This information will be used for service mock, service test. diff --git a/en-us/docs/3.0/user/references/registry/redis.md b/en-us/docs/3.0/user/references/registry/redis.md index ac4e16e..615b68f 100644 --- a/en-us/docs/3.0/user/references/registry/redis.md +++ b/en-us/docs/3.0/user/references/registry/redis.md @@ -65,7 +65,7 @@ A home-brewed service registry server is used in Alibaba instead of redis server ## Installation -Pls. refer to [redis install manual](http://dubbo.apache.org/en-us/docs/admin/install/redis.html) for how to install a redis based registry server. To set it up, specify `dubbo.registry.address` to `redis://127.0.0.1:6379` in `conf/dubbo.properties` for both provider and consumer (you can refer to [quick start](../../quick-start.md)) after install a redis server. +Pls. refer to [redis install manual](../../../admin/install/redis.md) for how to install a redis based registry server. To set it up, specify `dubbo.registry.address` to `redis://127.0.0.1:6379` in `conf/dubbo.properties` for both provider and consumer (you can refer to [quick start](../../quick-start.md)) after install a redis server. [^1]: [Redis](http://redis.io) is a high performance KV cache server diff --git a/en-us/docs/3.0/user/references/telnet.md b/en-us/docs/3.0/user/references/telnet.md index 78ffb80..fe0a4eb 100644 --- a/en-us/docs/3.0/user/references/telnet.md +++ b/en-us/docs/3.0/user/references/telnet.md @@ -19,7 +19,7 @@ It is possible to extend command `status` to check more resources, pls. refer to ## Supported Commands The built-in telnet commands are listed below. Furthermore, it is possible to extend telnet commands, pls. refer to -[extend telnet command](http://dubbo.apache.org/en-us/docs/user/references/telnet.html) for more details. +[extend telnet command](./telnet.md) for more details. ### `ls` diff --git a/zh-cn/docs/2.7/user/demos/simplify-registry-data.md b/zh-cn/docs/2.7/user/demos/simplify-registry-data.md index 3b02068..a72b3e9 100644 --- a/zh-cn/docs/2.7/user/demos/simplify-registry-data.md +++ b/zh-cn/docs/2.7/user/demos/simplify-registry-data.md @@ -1,8 +1,8 @@ # 背景 -dubbo provider中的服务配置项有接近[30个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 +dubbo provider中的服务配置项有接近[30个配置项](../references/xml/dubbo-service.md)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 -dubbo consumer中的配置项也有[20+个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 +dubbo consumer中的配置项也有[20+个配置项](../references/xml/dubbo-reference.md)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 这些数据是以服务为维度注册进入注册中心，导致了数据量的膨胀，进而引发注册中心(如zookeeper)的网络开销增大，性能降低。 diff --git a/zh-cn/docs/2.7/user/references/metadata/introduction.md b/zh-cn/docs/2.7/user/references/metadata/introduction.md index 0cdf8fc..d5fd39a 100644 --- a/zh-cn/docs/2.7/user/references/metadata/introduction.md +++ b/zh-cn/docs/2.7/user/references/metadata/introduction.md @@ -1,6 +1,6 @@ # 背景 -dubbo provider中的服务配置项有接近[30个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 -dubbo consumer中的配置项也有[20+个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 +dubbo provider中的服务配置项有接近[30个配置项](../xml/dubbo-service.md)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 +dubbo consumer中的配置项也有[20+个配置项](../xml/dubbo-reference.md)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 这些数据是以服务为维度注册进入注册中心，导致了数据量的膨胀，进而引发注册中心(如zookeeper)的网络开销增大，性能降低。 除了上述配置项的存储之外，dubbo服务元数据信息也需要被存储下来。元数据信息包括服务接口，及接口的方法信息。这些信息将被用于服务mock，服务测试。 diff --git a/zh-cn/docs/3.0/user/demos/simplify-registry-data.md b/zh-cn/docs/3.0/user/demos/simplify-registry-data.md index 3b02068..a72b3e9 100644 --- a/zh-cn/docs/3.0/user/demos/simplify-registry-data.md +++ b/zh-cn/docs/3.0/user/demos/simplify-registry-data.md @@ -1,8 +1,8 @@ # 背景 -dubbo provider中的服务配置项有接近[30个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 +dubbo provider中的服务配置项有接近[30个配置项](../references/xml/dubbo-service.md)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 -dubbo consumer中的配置项也有[20+个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 +dubbo consumer中的配置项也有[20+个配置项](../references/xml/dubbo-reference.md)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 这些数据是以服务为维度注册进入注册中心，导致了数据量的膨胀，进而引发注册中心(如zookeeper)的网络开销增大，性能降低。 diff --git a/zh-cn/docs/3.0/user/references/metadata/introduction.md b/zh-cn/docs/3.0/user/references/metadata/introduction.md index 0cdf8fc..d5fd39a 100644 --- a/zh-cn/docs/3.0/user/references/metadata/introduction.md +++ b/zh-cn/docs/3.0/user/references/metadata/introduction.md @@ -1,6 +1,6 @@ # 背景 -dubbo provider中的服务配置项有接近[30个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-service.html)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 -dubbo consumer中的配置项也有[20+个配置项](http://dubbo.apache.org/en-us/docs/user/references/xml/dubbo-reference.html)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 +dubbo provider中的服务配置项有接近[30个配置项](../xml/dubbo-service.md)。 排除注册中心服务治理需要之外，很大一部分配置项是provider自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以key-value形式持久化存储。 +dubbo consumer中的配置项也有[20+个配置项](../xml/dubbo-reference.md)。在注册中心之中，服务消费者列表中只需要关注application，version，group，ip，dubbo版本等少量配置，其他配置也可以以key-value形式持久化存储。 这些数据是以服务为维度注册进入注册中心，导致了数据量的膨胀，进而引发注册中心(如zookeeper)的网络开销增大，性能降低。 除了上述配置项的存储之外，dubbo服务元数据信息也需要被存储下来。元数据信息包括服务接口，及接口的方法信息。这些信息将被用于服务mock，服务测试。
