You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dubbo.apache.org by al...@apache.org on 2024/09/13 07:29:16 UTC

(dubbo-website) branch master updated: Refactor website structure (#2860)

This is an automated email from the ASF dual-hosted git repository.

albumenj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 1a4b998f54b Refactor website structure (#2860)
1a4b998f54b is described below

commit 1a4b998f54b52e78101a851e840c71737410976c
Author: Albumen Kevin <jh...@gmail.com>
AuthorDate: Fri Sep 13 15:29:11 2024 +0800

    Refactor website structure (#2860)
---
 .github/workflows/build_and_deploy_history.yml     |    2 +-
 .github/workflows/link_check.yml                   |    2 +-
 .htmltest.yml                                      |    4 +-
 assets/scss/_base.scss                             |    4 +-
 assets/scss/_buttons.scss                          |   15 +
 assets/scss/_case-studies.scss                     |    2 +-
 assets/scss/_custom.scss                           |   91 +-
 assets/scss/_skin.scss                             |    1 +
 assets/scss/main.scss                              |   11 +-
 cn_config.toml                                     |   22 +-
 config.toml                                        |   85 +-
 content/en/_index.html                             |  129 +-
 content/en/blog/_index.md                          |    2 +-
 content/en/docs3-v2/_index.md                      |    6 +-
 .../observability/kubernetes-probes.md             |    2 +-
 .../others/dubbo-kubernetes-probe.md               |    8 +-
 .../others/logger-howto.md                         |    2 +-
 .../others/logger-management.md                    |    4 +-
 .../others/service-container.md                    |    4 +-
 .../performance/loadbalance.md                     |    4 +-
 .../performance/profiler.md                        |    4 +-
 .../performance/result-cache.md                    |    4 +-
 .../performance/router-snapshot.md                 |    4 +-
 .../advanced-features-and-usage/service/context.md |    4 +-
 .../service/fault-tolerent-strategy.md             |    4 +-
 .../service/group-merger.md                        |    4 +-
 .../service/multi-registry.md                      |    2 +-
 .../service/parameter-validation.md                |    2 +-
 content/en/docs3-v2/java-sdk/faq/0/1.md            |    2 +-
 content/en/docs3-v2/java-sdk/faq/0/13.md           |    4 +-
 content/en/docs3-v2/java-sdk/faq/0/2.md            |    4 +-
 content/en/docs3-v2/java-sdk/faq/1/12.md           |    2 +-
 content/en/docs3-v2/java-sdk/faq/1/14.md           |    2 +-
 content/en/docs3-v2/java-sdk/faq/1/17.md           |    4 +-
 content/en/docs3-v2/java-sdk/faq/1/18.md           |    4 +-
 content/en/docs3-v2/java-sdk/faq/1/3.md            |    2 +-
 content/en/docs3-v2/java-sdk/faq/1/4.md            |    2 +-
 content/en/docs3-v2/java-sdk/faq/1/8.md            |    2 +-
 .../java-sdk/reference-manual/protocol/http.md     |    5 +
 .../java-sdk/reference-manual/protocol/rest.md     |    5 +
 .../reference-manual/protocol/tripe-3.3.md         |  282 +++++
 .../reference-manual/protocol/tripe-rest-manual.md |  984 +++++++++++++++
 content/en/download/_index.md                      |    2 +-
 content/en/featured-background.jpg                 |  Bin 83079 -> 331001 bytes
 content/en/overview/_index.md                      |    2 +-
 content/en/overview/demo/_index.md                 |    6 +
 content/zh-cn/_index.html                          |  156 +--
 content/zh-cn/blog/ web/_index.md                  |    9 +
 content/zh-cn/blog/_index.md                       |    2 +-
 .../dubbo-triple-with-apisix-gateway.md            |  154 +++
 .../how-to-proxy-dubbo-in-apache-apisix.md         |  134 ++-
 .../integration/how-to-proxy-dubbo-in-higress.md   |   93 +-
 .../codeanalysis/multiple-protocols-on-one-port.md |  135 +++
 .../dubbo-supporting-grpc-http2-and-protobuf.md    |    4 +-
 content/zh-cn/blog/java/demos/hystrix.md           |  189 +++
 content/zh-cn/blog/java/demos/resilience4j.md      |   14 +
 content/zh-cn/blog/java/proposals/_index.md        |    7 +
 .../java/proposals/service-discovery-migration.md  |  401 +++++++
 .../blog/java/proposals/service-discovery-rule.md  |  Bin 0 -> 9461 bytes
 .../java/proposals/service-discovery-samples.md    |   87 ++
 content/zh-cn/blog/news/20230130-release.md        |    2 +-
 content/zh-cn/blog/news/apache-33-release.md       |  192 +++
 content/zh-cn/blog/news/dubbo-initializer.md       |   64 +
 content/zh-cn/blog/news/releases/3.1.4.md          |    2 +-
 content/zh-cn/blog/nodejs/_index.md                |    9 +
 content/zh-cn/contact/_index.md                    |    6 +-
 content/zh-cn/demo/_index.md                       |   31 +
 content/zh-cn/docs/advanced/service-container.md   |    2 +-
 content/zh-cn/docs/advanced/static-service.md      |    2 +-
 content/zh-cn/docs/references/registry/simple.md   |    2 +-
 content/zh-cn/download/_index.md                   |    4 +-
 content/zh-cn/featured-background.jpg              |  Bin 83079 -> 331001 bytes
 content/zh-cn/github/_index.md                     |    8 +-
 content/zh-cn/overview/core-features/_index.md     |    9 -
 content/zh-cn/overview/core-features/ecosystem.md  |   45 -
 .../zh-cn/overview/core-features/extensibility.md  |  122 --
 .../zh-cn/overview/core-features/load-balance.md   |  104 --
 content/zh-cn/overview/core-features/more.md       |   71 --
 .../zh-cn/overview/core-features/observability.md  |   59 -
 content/zh-cn/overview/core-features/protocols.md  |   88 --
 content/zh-cn/overview/core-features/security.md   |  108 --
 .../overview/core-features/service-definition.md   |  128 --
 .../overview/core-features/service-discovery.md    |   72 --
 .../zh-cn/overview/core-features/service-mesh.md   |   89 --
 .../zh-cn/overview/core-features/traffic/_index.md |  274 -----
 .../core-features/traffic/circuit-breaking.md      |   41 -
 .../core-features/traffic/condition-rule.md        |   78 --
 .../core-features/traffic/configuration-rule.md    |   94 --
 .../core-features/traffic/mesh-rule.md.bak         |  372 ------
 .../overview/core-features/traffic/script-rule.md  |   63 -
 .../overview/core-features/traffic/tag-rule.md     |   61 -
 content/zh-cn/overview/demo/_index.md              |    6 +
 content/zh-cn/overview/home/_index.md              |    1 +
 content/zh-cn/overview/mannual/_index.md           |   15 +-
 .../zh-cn/overview/mannual/control-plane/_index.md |   10 +
 .../overview/mannual/control-plane/architecture.md |  296 +++++
 .../mannual/control-plane/documentation.md         |   17 +
 .../zh-cn/overview/mannual/control-plane/mock.md   |  176 +++
 .../zh-cn/overview/mannual/control-plane/search.md |   55 +
 .../zh-cn/overview/mannual/control-plane/test.md   |  193 +++
 .../overview/mannual/dubbo-go-pixiu/_index.md      |   10 -
 .../overview/mannual/dubbo-go-pixiu/dev/_index.md  |   10 -
 .../mannual/dubbo-go-pixiu/dev/dubbo-pilot.md      |  201 ----
 .../mannual/dubbo-go-pixiu/dev/filter-extension.md |  141 ---
 .../overview/mannual/dubbo-go-pixiu/dev/trie.md    |  145 ---
 .../mannual/dubbo-go-pixiu/overview/_index.md      |   10 -
 .../mannual/dubbo-go-pixiu/overview/faq.md         |   28 -
 .../mannual/dubbo-go-pixiu/overview/terminology.md |   42 -
 .../dubbo-go-pixiu/overview/what-is-pixiu.md       |   46 -
 .../overview/mannual/dubbo-go-pixiu/user/_index.md |   10 -
 .../mannual/dubbo-go-pixiu/user/adapter/_index.md  |   10 -
 .../mannual/dubbo-go-pixiu/user/adapter/dubbo.md   |   10 -
 .../dubbo-go-pixiu/user/adapter/springcloud.md     |   10 -
 .../mannual/dubbo-go-pixiu/user/appendix/_index.md |   10 -
 .../appendix/http-to-dubbo-default-stragety.md     |  325 -----
 .../mannual/dubbo-go-pixiu/user/configurations.md  |  158 ---
 .../mannual/dubbo-go-pixiu/user/deployment.md      |   88 --
 .../dubbo-go-pixiu/user/httpfilter/_index.md       |   10 -
 .../dubbo-go-pixiu/user/httpfilter/hystrix.md      |   17 -
 .../dubbo-go-pixiu/user/httpfilter/ratelimit.md    |   17 -
 .../mannual/dubbo-go-pixiu/user/listener/_index.md |   10 -
 .../mannual/dubbo-go-pixiu/user/listener/http.md   |   51 -
 .../mannual/dubbo-go-pixiu/user/listener/http2.md  |   17 -
 .../mannual/dubbo-go-pixiu/user/listener/tcp.md    |   17 -
 .../mannual/dubbo-go-pixiu/user/listener/triple.md |   17 -
 .../dubbo-go-pixiu/user/networkfilter/_index.md    |   10 -
 .../dubbo-go-pixiu/user/networkfilter/dubbo.md     |   17 -
 .../dubbo-go-pixiu/user/networkfilter/http.md      |   17 -
 .../mannual/dubbo-go-pixiu/user/quality/_index.md  |   10 -
 .../dubbo-go-pixiu/user/quality/performance.md     |   17 -
 .../dubbo-go-pixiu/user/quality/stability.md       |   17 -
 .../mannual/dubbo-go-pixiu/user/quickstart.md      |  169 ---
 .../mannual/dubbo-go-pixiu/user/samples/_index.md  |   10 -
 .../dubbo-go-pixiu/user/samples/http_proxy.md      |   73 --
 .../dubbo-go-pixiu/user/samples/http_to_dubbo.md   |   17 -
 .../mannual/dubbo-go-pixiu/user/samples/https.md   |   17 -
 .../zh-cn/overview/mannual/erlang-sdk/_index.md    |   10 -
 .../overview/mannual/erlang-sdk/quick-start.md     |   74 --
 .../zh-cn/overview/mannual/erlang-sdk/reference.md |   32 -
 .../overview/mannual/erlang-sdk/serialization.md   |   34 -
 .../zh-cn/overview/mannual/erlang-sdk/service.md   |   38 -
 .../zh-cn/overview/mannual/golang-sdk/_index.md    |    2 +-
 .../overview/mannual/golang-sdk/introduction.md    |  124 ++
 .../mannual/golang-sdk/preface/3.0_feature.md      |   79 --
 .../overview/mannual/golang-sdk/preface/_index.md  |   18 -
 .../mannual/golang-sdk/preface/concept/_index.md   |   10 -
 .../mannual/golang-sdk/preface/concept/generic.md  |  162 ---
 .../golang-sdk/preface/concept/multi_language.md   |   29 -
 .../mannual/golang-sdk/preface/concept/protocol.md |  117 --
 .../mannual/golang-sdk/preface/concept/registry.md |   95 --
 .../mannual/golang-sdk/preface/design/_index.md    |   10 -
 .../golang-sdk/preface/design/aop_and_extension.md |  110 --
 .../golang-sdk/preface/design/app_and_interface.md |   73 --
 .../golang-sdk/preface/design/architecture.md      |   30 -
 .../overview/mannual/golang-sdk/preface/samples.md |  184 ---
 .../mannual/golang-sdk/quickstart/_index.md        |    6 +-
 .../mannual/golang-sdk/quickstart/install.md       |   58 -
 .../mannual/golang-sdk/quickstart/microservices.md |  195 +++
 .../golang-sdk/quickstart/quickstart_triple.md     |  137 ---
 .../quickstart/quickstart_triple_with_customize.md |  221 ----
 .../overview/mannual/golang-sdk/quickstart/rpc.md  |  248 ++++
 .../overview/mannual/golang-sdk/refer/_index.md    |    4 +-
 .../mannual/golang-sdk/refer/basic_concept.md      |   42 -
 .../mannual/golang-sdk/refer/compatible_version.md |   23 -
 .../overview/mannual/golang-sdk/refer/config.md    |  130 --
 .../overview/mannual/golang-sdk/refer/ecology.md   |   45 +-
 .../overview/mannual/golang-sdk/refer/generic.md   |  162 +++
 .../overview/mannual/golang-sdk/refer/nacos.md     |  147 +++
 .../golang-sdk/refer/sourcecode/3.0_feature.md     |   80 ++
 .../mannual/golang-sdk/refer/sourcecode/_index.md  |   10 +
 .../refer/sourcecode/aop_and_extension.md          |  111 ++
 .../refer/sourcecode/app_and_interface.md          |   74 ++
 .../golang-sdk/refer/sourcecode/architecture.md    |   31 +
 .../features => refer/sourcecode}/generic-2.md     |    0
 .../mannual/golang-sdk/refer/sourcecode/generic.md |  107 ++
 .../golang-sdk/{ => refer}/sourcecode/protocol.md  |    0
 .../golang-sdk/{ => refer}/sourcecode/registry.md  |    0
 .../mannual/golang-sdk/refer/use_dubbogo_cli.md    |   10 +-
 .../mannual/golang-sdk/sourcecode/_index.md        |    9 -
 .../overview/mannual/golang-sdk/tutorial/_index.md |    1 +
 .../golang-sdk/tutorial/configuration/_index.md    |  161 +++
 .../golang-sdk/tutorial/configuration/file.md      |  280 +++++
 .../golang-sdk/tutorial/configuration/remote.md    |   80 ++
 .../golang-sdk/tutorial/debugging/_index.md        |    9 -
 .../golang-sdk/tutorial/debugging/grpc_cli.md      |   84 --
 .../mannual/golang-sdk/tutorial/deploy2/_index.md  |   10 +
 .../mannual/golang-sdk/tutorial/deploy2/deploy.md  |  430 +++++++
 .../tutorial/deploy2/graceful_shutdown.md          |   66 +
 .../{governance/service-mesh => deploy2}/istio.md  |    0
 .../proxyless_service_mesh.md                      |    0
 .../service-mesh => deploy2}/traffic_management.md |    0
 .../golang-sdk/tutorial/deployment/_index.md       |    9 -
 .../tutorial/deployment/docker/_index.md           |    9 -
 .../tutorial/deployment/kubernetes/_index.md       |    9 -
 .../tutorial/deployment/practice/_index.md         |    9 -
 .../mannual/golang-sdk/tutorial/develop/_index.md  |    9 -
 .../tutorial/develop/config-center/_index.md       |    9 -
 .../develop/config-center/config-center-dynamic.md |  156 ---
 .../tutorial/develop/config-center/desc.md         |    9 -
 .../develop/config-center/remote_config.md         |   52 -
 .../golang-sdk/tutorial/develop/features/_index.md |    9 -
 .../tutorial/develop/features/config_api.md        |  107 --
 .../tutorial/develop/features/context.md           |   23 -
 .../tutorial/develop/features/custom-logger.md     |   94 --
 .../tutorial/develop/interflow/_index.md           |    9 -
 .../tutorial/develop/interflow/call_grpc.md        |   23 -
 .../tutorial/develop/interflow/call_java.md        |  851 -------------
 .../golang-sdk/tutorial/develop/protocol/_index.md |    9 -
 .../tutorial/develop/protocol/choose_protocol.md   |  239 ----
 .../golang-sdk/tutorial/develop/protocol/error.md  |  131 --
 .../develop/protocol/exception_response.md         |  124 --
 .../golang-sdk/tutorial/develop/registry/_index.md |    9 -
 .../golang-sdk/tutorial/develop/registry/desc.md   |   63 -
 .../tutorial/develop/registry/multi_registry.md    |  125 --
 .../tutorial/develop/registry/nacos-2.md           |   87 --
 .../golang-sdk/tutorial/develop/registry/nacos.md  |  150 ---
 .../tutorial/develop/registry/polaris.md           |   75 --
 .../tutorial/develop/registry/registry.md          |  118 --
 .../tutorial/develop/registry/service-discovery.md |   65 -
 .../tutorial/develop/registry/zookeeper.md         |  111 --
 .../golang-sdk/tutorial/develop/template.md        |   96 --
 .../mannual/golang-sdk/tutorial/gateway/_index.md  |    7 +
 .../service-mesh/pixiu => gateway}/http_triple.md  |    0
 .../pixiu => gateway}/pixiu-nacos-triple.md        |    0
 .../golang-sdk/tutorial/governance/_index.md       |    9 -
 .../tutorial/governance/features/_index.md         |    9 -
 .../golang-sdk/tutorial/governance/features/aop.md |   73 --
 .../tutorial/governance/features/custom-filter.md  |  115 --
 .../tutorial/governance/features/timeout.md        |   66 -
 .../tutorial/governance/health/_index.md           |    9 -
 .../tutorial/governance/health/kubernetes.md       |    9 -
 .../tutorial/governance/health/start-check.md      |   37 -
 .../governance/health/triple-health-check.md       |  114 --
 .../golang-sdk/tutorial/governance/limit/_index.md |    9 -
 .../tutorial/governance/limit/adaptive-service.md  |   26 -
 .../tutorial/governance/limit/internally/_index.md |    9 -
 .../tutorial/governance/limit/polaris/_index.md    |    9 -
 .../tutorial/governance/limit/sentinel/_index.md   |    9 -
 .../tutorial/governance/limit/tps_limiter.md       |  112 --
 .../tutorial/governance/monitor/_index.md          |    9 -
 .../tutorial/governance/monitor/grafana/_index.md  |    9 -
 .../tutorial/governance/monitor/http/_index.md     |    9 -
 .../tutorial/governance/monitor/logger/_index.md   |    9 -
 .../tutorial/governance/monitor/metrics.md         |  214 ----
 .../governance/monitor/promethus/_index.md         |    9 -
 .../tutorial/governance/monitor/rpc_metrics.md     |   58 -
 .../tutorial/governance/service-mesh/_index.md     |    9 -
 .../tutorial/governance/service-mesh/deploy.md     |  435 -------
 .../governance/service-mesh/pixiu/_index.md        |    9 -
 .../tutorial/governance/tracing/_index.md          |    9 -
 .../tutorial/governance/tracing/jaeger/_index.md   |    9 -
 .../governance/tracing/opentelmentry/_index.md     |    9 -
 .../governance/tracing/skywalking/_index.md        |    9 -
 .../tutorial/governance/traffic/_index.md          |    9 -
 .../governance/traffic/graceful_shutdown.md        |   70 --
 .../tutorial/governance/traffic/mesh_router.md     |  153 ---
 .../golang-sdk/tutorial/interop-dubbo/_index.md    |   10 +
 .../call_java_protocol_dubbo_non_protobuf.md       |   77 ++
 .../call_java_protocol_triple_protobuf.md          |  106 ++
 .../tutorial/interop-dubbo/service-discovery.md    |   80 ++
 .../golang-sdk/tutorial/interop-grpc/_index.md     |   10 +
 .../golang-sdk/tutorial/interop-grpc/call_grpc.md  |  244 ++++
 .../golang-sdk/tutorial/load-balance/_index.md     |    6 +
 .../tutorial/load-balance/loadbalance.md           |   61 +
 .../golang-sdk/tutorial/observability/_index.md    |   10 +
 .../golang-sdk/tutorial/observability/logger.md    |   77 ++
 .../tutorial/observability/rpc_metrics.md          |  147 +++
 .../golang-sdk/tutorial/observability/tracing.md   |   85 ++
 .../mannual/golang-sdk/tutorial/rpc/_index.md      |    9 +
 .../mannual/golang-sdk/tutorial/rpc/attachments.md |  181 +++
 .../mannual/golang-sdk/tutorial/rpc/error.md       |  156 +++
 .../mannual/golang-sdk/tutorial/rpc/filter.md      |   97 ++
 .../mannual/golang-sdk/tutorial/rpc/healthcheck.md |   95 ++
 .../mannual/golang-sdk/tutorial/rpc/protocol.md    |  143 +++
 .../mannual/golang-sdk/tutorial/rpc/retry.md       |  185 +++
 .../mannual/golang-sdk/tutorial/rpc/start-check.md |   43 +
 .../mannual/golang-sdk/tutorial/rpc/streaming.md   |  216 ++++
 .../mannual/golang-sdk/tutorial/rpc/timeout.md     |  155 +++
 .../tutorial/service-discovery/_index.md           |   11 +
 .../tutorial/service-discovery/multi_registry.md   |   86 ++
 .../golang-sdk/tutorial/service-discovery/nacos.md |   58 +
 .../tutorial/service-discovery/zookeeper.md        |   68 ++
 .../mannual/golang-sdk/tutorial/traffic/_index.md  |    9 +
 .../mannual/golang-sdk/tutorial/traffic/router.md  |   11 +
 .../golang-sdk/tutorial/traffic/sentinel.md        |   35 +
 .../golang-sdk/tutorial/transaction/_index.md      |    7 +
 .../golang-sdk/tutorial/transaction/seata.md       |   18 +
 .../zh-cn/overview/mannual/golang-sdk/versions.md  |   41 +
 content/zh-cn/overview/mannual/java-sdk/_index.md  |    6 +-
 .../java-sdk/advanced-features-and-usage/_index.md |   14 -
 .../observability/_index.md                        |   26 -
 .../observability/logging.md                       |  172 ---
 .../observability/meter.md                         |  331 -----
 .../observability/tracing.md                       |   40 -
 .../advanced-features-and-usage/others/_index.md   |   10 -
 .../advanced-features-and-usage/others/docker.md   |   78 --
 .../others/dubbo-kubernetes-probe.md               |   80 --
 .../others/graceful-shutdown.md                    |   53 -
 .../others/logger-howto.md                         |  180 ---
 .../others/logger-management.md                    |  121 --
 .../others/service-container.md                    |   66 -
 .../advanced-features-and-usage/others/set-host.md |   93 --
 .../performance/_index.md                          |   10 -
 .../performance/adaptive-concurrency-control.md    |   50 -
 .../performance/concurrency-control.md             |   91 --
 .../performance/config-connections.md              |   57 -
 .../performance/dump.md                            |   64 -
 .../performance/lazy-connect.md                    |   27 -
 .../performance/loadbalance.md                     |   67 --
 .../performance/profiler.md                        |  196 ---
 .../performance/reference-config-cache.md          |   53 -
 .../performance/result-cache.md                    |  126 --
 .../performance/router-snapshot.md                 |   89 --
 .../performance/serialization.md                   |  253 ----
 .../performance/simplify-registry-data.md          |  272 -----
 .../performance/stickiness.md                      |   35 -
 .../performance/support-graalvm.md                 |  220 ----
 .../performance/threading-model/_index.md          |   10 -
 .../performance/threading-model/consumer.md        |   57 -
 .../performance/threading-model/provider.md        |  138 ---
 .../advanced-features-and-usage/security/_index.md |   10 -
 .../advanced-features-and-usage/security/auth.md   |   50 -
 .../security/class-check.md                        |  222 ----
 .../advanced-features-and-usage/security/tls.md    |   62 -
 .../security/token-authorization.md                |   58 -
 .../advanced-features-and-usage/service/_index.md  |   10 -
 .../service/accesslog.md                           |   35 -
 .../service/async-call.md                          |  184 ---
 .../service/async-execute-on-provider.md           |  106 --
 .../service/attachment.md                          |  146 ---
 .../service/callback-parameter.md                  |  126 --
 .../service/consistent-hash.md                     |   56 -
 .../advanced-features-and-usage/service/context.md |   57 -
 .../service/delay-publish.md                       |   74 --
 .../service/distributed-transaction.md             |   33 -
 .../service/echo-service.md                        |   47 -
 .../service/events-notify.md                       |  116 --
 .../service/explicit-target.md                     |   68 --
 .../service/fault-tolerent-strategy.md             |  152 ---
 .../service/generic-reference.md                   |  385 ------
 .../service/generic-service.md                     |   70 --
 .../service/group-merger.md                        |   78 --
 .../service/isolation-executor.md                  |  240 ----
 .../service/json-compatibility-check.md            |   67 --
 .../service/local-call.md                          |   86 --
 .../service/local-mock.md                          |  162 ---
 .../service/local-stub.md                          |   63 -
 .../service/multi-protocols.md                     |   67 --
 .../service/multi-registry.md                      |  100 --
 .../service/multi-versions.md                      |   57 -
 .../service/parameter-validation.md                |  205 ----
 .../service/port-unification.md                    |  139 ---
 .../service/preflight-check.md                     |   75 --
 .../service/reactive.md                            |  242 ----
 .../service/registry-only.md                       |   38 -
 .../service/service-downgrade.md                   |  100 --
 .../service/service-group.md                       |  193 ---
 .../service/specify-ip.md                          |  111 --
 .../service/streaming.md                           |   17 -
 .../service/subscribe-only.md                      |   41 -
 .../service/transaction.md                         |  413 -------
 .../advanced-features-and-usage/traffic/_index.md  |   26 -
 .../traffic/_index.md.bak                          |   45 -
 .../traffic/config-rule.md.bak                     |  176 ---
 .../traffic/routing-rule.md.bak                    |  244 ----
 .../advanced-features-and-usage/triple/_index.md   |   10 -
 .../advanced-features-and-usage/triple/idl.md      |  246 ----
 .../triple/streaming.md                            |  305 -----
 .../advanced-features-and-usage/triple/wrap.md     |  179 ---
 content/zh-cn/overview/mannual/java-sdk/faq/0/1.md |   31 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/10.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/11.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/12.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/13.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/14.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/15.md    |   28 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/16.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/17.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/18.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/19.md    |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/2.md |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/20.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/21.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/22.md    |   30 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/23.md    |   28 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/24.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/25.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/26.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/27.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/28.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/29.md    |   38 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/3.md |   40 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/4.md |   57 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/5.md |   32 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/6.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/7.md |   26 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/8.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/0/9.md |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/0/99.md    |   23 -
 .../overview/mannual/java-sdk/faq/0/_index.md      |   17 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/1.md |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/10.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/11.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/12.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/13.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/14.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/15.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/16.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/17.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/18.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/19.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/20.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/21.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/22.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/26.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/27.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/28.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/29.md    |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/3.md |   22 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/30.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/31.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/32.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/33.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/34.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/35.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/36.md    |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/37.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/38.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/39.md    |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/4.md |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/40.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/41.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/1/42.md    |   18 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/5.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/6.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/7.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/8.md |   27 -
 content/zh-cn/overview/mannual/java-sdk/faq/1/9.md |   34 -
 .../overview/mannual/java-sdk/faq/1/_index.md      |   17 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/1.md |   17 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/10.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/11.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/12.md    |   22 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/13.md    |   22 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/14.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/15.md    |   22 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/16.md    |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/17.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/18.md    |   22 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/19.md    |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/2.md |   31 -
 .../zh-cn/overview/mannual/java-sdk/faq/2/20.md    |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/3.md |   22 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/4.md |   22 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/5.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/6.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/7.md |   22 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/8.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/2/9.md |   22 -
 .../overview/mannual/java-sdk/faq/2/_index.md      |   10 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/1.md |   27 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/2.md |   26 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/3.md |   21 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/4.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/5.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/6.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/7.md |   28 -
 content/zh-cn/overview/mannual/java-sdk/faq/3/8.md |   29 -
 .../overview/mannual/java-sdk/faq/3/_index.md      |   10 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/1.md |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/10.md    |   36 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/11.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/12.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/13.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/14.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/15.md    |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/16.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/17.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/18.md    |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/19.md    |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/2.md |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/20.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/4/21.md    |   27 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/3.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/4.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/5.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/6.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/7.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/8.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/4/9.md |   32 -
 .../overview/mannual/java-sdk/faq/4/_index.md      |   10 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/1.md |   28 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/10.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/11.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/12.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/13.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/14.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/15.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/16.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/17.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/18.md    |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/2.md |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/20.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/21.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/22.md    |   28 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/23.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/24.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/25.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/26.md    |   21 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/27.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/28.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/29.md    |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/3.md |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/30.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/31.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/32.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/33.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/34.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/35.md    |   26 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/36.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/37.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/38.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/39.md    |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/4.md |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/40.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/41.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/42.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/5/43.md    |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/5.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/6.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/7.md |   27 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/8.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/5/9.md |   27 -
 .../overview/mannual/java-sdk/faq/5/_index.md      |   10 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/1.md |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/10.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/11.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/12.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/13.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/14.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/15.md    |   23 -
 .../zh-cn/overview/mannual/java-sdk/faq/6/16.md    |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/2.md |   33 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/3.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/4.md |   21 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/5.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/6.md |   26 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/7.md |   23 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/8.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/6/9.md |   27 -
 .../overview/mannual/java-sdk/faq/6/_index.md      |   10 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/1.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/2.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/3.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/4.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/5.md |   25 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/6.md |   24 -
 content/zh-cn/overview/mannual/java-sdk/faq/7/7.md |   24 -
 .../overview/mannual/java-sdk/faq/7/_index.md      |   10 -
 .../zh-cn/overview/mannual/java-sdk/faq/81/1.md    |   27 -
 .../zh-cn/overview/mannual/java-sdk/faq/81/2.md    |   24 -
 .../zh-cn/overview/mannual/java-sdk/faq/81/3.md    |   25 -
 .../zh-cn/overview/mannual/java-sdk/faq/81/4.md    |   29 -
 .../overview/mannual/java-sdk/faq/81/_index.md     |   17 -
 .../zh-cn/overview/mannual/java-sdk/faq/99/0.md    |   29 -
 .../zh-cn/overview/mannual/java-sdk/faq/99/1.md    |   26 -
 .../overview/mannual/java-sdk/faq/99/_index.md     |   10 -
 .../zh-cn/overview/mannual/java-sdk/faq/_index.md  |   17 -
 .../zh-cn/overview/mannual/java-sdk/faq/intro.md   |   51 -
 .../mannual/java-sdk/quick-start/_index.md         |    6 +-
 .../overview/mannual/java-sdk/quick-start/api.md   |  287 -----
 .../overview/mannual/java-sdk/quick-start/brief.md |  319 -----
 .../mannual/java-sdk/quick-start/deploy.md         |  139 +++
 .../overview/mannual/java-sdk/quick-start/idl.md   |  241 ----
 .../mannual/java-sdk/quick-start/spring-boot.md    |  564 ---------
 .../mannual/java-sdk/quick-start/spring-xml.md     |  403 -------
 .../mannual/java-sdk/quick-start/starter.md        |  178 +++
 .../mannual/java-sdk/reference-manual/_index.md    |    3 +-
 .../reference-manual/architecture/_index.md        |    2 +-
 .../reference-manual/architecture/dubbo-spi.md     |  913 ++++++++++++++
 .../architecture/multi-instance/_index.md          |    7 +
 .../architecture/multi-instance/develop.md         |  Bin 0 -> 7392 bytes
 .../architecture/multi-instance/model.md           |  178 +++
 .../architecture/multi-instance/multi-instance.md  |  113 ++
 .../architecture/multi-instance/workflow.md        |   25 +
 .../architecture/multi-protocol.md                 |  132 ++
 .../reference-manual/config-center/_index.md       |    2 +-
 .../reference-manual/config-center/introduction.md |   29 +
 .../reference-manual/config-center/nacos.md        |    9 +-
 .../reference-manual/config-center/others.md       |   54 +
 .../reference-manual/config-center/zookeeper.md    |   12 +-
 .../java-sdk/reference-manual/config/_index.md     |    1 +
 .../java-sdk/reference-manual/config/annotation.md |  219 ----
 .../java-sdk/reference-manual/config/api.md        |  315 -----
 .../java-sdk/reference-manual/config/api/_index.md |   10 +
 .../java-sdk/reference-manual/config/api/api.md    |  389 ++++++
 .../reference-manual/config/maven-plugin.md        |  179 +++
 .../java-sdk/reference-manual/config/overview.md   |  174 ---
 .../java-sdk/reference-manual/config/principle.md  |  198 ++-
 .../java-sdk/reference-manual/config/properties.md | 1265 +++++++++++---------
 .../reference-manual/config/properties3.md.bak     |  578 +++++++++
 .../reference-manual/config/spring/_index.md       |   10 +
 .../reference-manual/config/spring/spring-boot.md  |   93 ++
 .../java-sdk/reference-manual/config/spring/xml.md |  199 +++
 .../java-sdk/reference-manual/config/xml.md        |  123 --
 .../mannual/java-sdk/reference-manual/faq/0/1.md   |   29 +
 .../mannual/java-sdk/reference-manual/faq/0/10.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/11.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/12.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/13.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/14.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/0/15.md  |   29 +
 .../mannual/java-sdk/reference-manual/faq/0/16.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/0/17.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/18.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/19.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/2.md   |   18 +
 .../mannual/java-sdk/reference-manual/faq/0/20.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/0/21.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/0/22.md  |   31 +
 .../mannual/java-sdk/reference-manual/faq/0/23.md  |   29 +
 .../mannual/java-sdk/reference-manual/faq/0/24.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/0/25.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/0/26.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/0/27.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/0/28.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/29.md  |   39 +
 .../mannual/java-sdk/reference-manual/faq/0/3.md   |   41 +
 .../mannual/java-sdk/reference-manual/faq/0/4.md   |   58 +
 .../mannual/java-sdk/reference-manual/faq/0/5.md   |   33 +
 .../mannual/java-sdk/reference-manual/faq/0/6.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/0/7.md   |   27 +
 .../mannual/java-sdk/reference-manual/faq/0/8.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/9.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/0/99.md  |   24 +
 .../java-sdk/reference-manual/faq/0/_index.md      |   18 +
 .../mannual/java-sdk/reference-manual/faq/1/1.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/10.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/11.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/12.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/13.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/14.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/15.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/16.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/1/17.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/18.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/19.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/20.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/21.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/22.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/26.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/27.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/28.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/29.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/3.md   |   23 +
 .../mannual/java-sdk/reference-manual/faq/1/30.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/1/31.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/32.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/1/33.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/34.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/35.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/36.md  |   22 +
 .../mannual/java-sdk/reference-manual/faq/1/37.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/38.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/39.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/4.md   |   28 +
 .../mannual/java-sdk/reference-manual/faq/1/40.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/1/41.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/42.md  |   19 +
 .../mannual/java-sdk/reference-manual/faq/1/5.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/1/6.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/7.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/1/8.md   |   28 +
 .../mannual/java-sdk/reference-manual/faq/1/9.md   |   35 +
 .../java-sdk/reference-manual/faq/1/_index.md      |   18 +
 .../mannual/java-sdk/reference-manual/faq/2/1.md   |   18 +
 .../mannual/java-sdk/reference-manual/faq/2/10.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/2/11.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/12.md  |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/13.md  |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/14.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/15.md  |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/16.md  |   22 +
 .../mannual/java-sdk/reference-manual/faq/2/17.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/18.md  |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/19.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/2/2.md   |   32 +
 .../mannual/java-sdk/reference-manual/faq/2/20.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/3.md   |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/4.md   |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/5.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/2/6.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/7.md   |   23 +
 .../mannual/java-sdk/reference-manual/faq/2/8.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/2/9.md   |   23 +
 .../java-sdk/reference-manual/faq/2/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/3/1.md   |   28 +
 .../mannual/java-sdk/reference-manual/faq/3/2.md   |   27 +
 .../mannual/java-sdk/reference-manual/faq/3/3.md   |   22 +
 .../mannual/java-sdk/reference-manual/faq/3/4.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/3/5.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/3/6.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/3/7.md   |   29 +
 .../mannual/java-sdk/reference-manual/faq/3/8.md   |   30 +
 .../java-sdk/reference-manual/faq/3/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/4/1.md   |   28 +
 .../mannual/java-sdk/reference-manual/faq/4/10.md  |   37 +
 .../mannual/java-sdk/reference-manual/faq/4/11.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/4/12.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/13.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/4/14.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/15.md  |   22 +
 .../mannual/java-sdk/reference-manual/faq/4/16.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/17.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/18.md  |   22 +
 .../mannual/java-sdk/reference-manual/faq/4/19.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/2.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/20.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/21.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/4/3.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/4.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/5.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/6.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/4/7.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/8.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/4/9.md   |   33 +
 .../java-sdk/reference-manual/faq/4/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/5/1.md   |   29 +
 .../mannual/java-sdk/reference-manual/faq/5/10.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/11.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/5/12.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/5/13.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/14.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/15.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/16.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/5/17.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/18.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/2.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/20.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/21.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/5/22.md  |   29 +
 .../mannual/java-sdk/reference-manual/faq/5/23.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/5/24.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/5/25.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/26.md  |   22 +
 .../mannual/java-sdk/reference-manual/faq/5/27.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/28.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/29.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/3.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/30.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/31.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/32.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/33.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/34.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/35.md  |   27 +
 .../mannual/java-sdk/reference-manual/faq/5/36.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/37.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/5/38.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/39.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/5/4.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/40.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/5/41.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/42.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/5/43.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/5.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/6.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/7.md   |   28 +
 .../mannual/java-sdk/reference-manual/faq/5/8.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/5/9.md   |   28 +
 .../java-sdk/reference-manual/faq/5/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/6/1.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/6/10.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/11.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/12.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/6/13.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/6/14.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/15.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/16.md  |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/2.md   |   34 +
 .../mannual/java-sdk/reference-manual/faq/6/3.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/4.md   |   22 +
 .../mannual/java-sdk/reference-manual/faq/6/5.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/6/6.md   |   27 +
 .../mannual/java-sdk/reference-manual/faq/6/7.md   |   24 +
 .../mannual/java-sdk/reference-manual/faq/6/8.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/6/9.md   |   28 +
 .../java-sdk/reference-manual/faq/6/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/7/1.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/7/2.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/7/3.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/7/4.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/7/5.md   |   26 +
 .../mannual/java-sdk/reference-manual/faq/7/6.md   |   25 +
 .../mannual/java-sdk/reference-manual/faq/7/7.md   |   25 +
 .../java-sdk/reference-manual/faq/7/_index.md      |   11 +
 .../mannual/java-sdk/reference-manual/faq/81/1.md  |   28 +
 .../mannual/java-sdk/reference-manual/faq/81/2.md  |   25 +
 .../mannual/java-sdk/reference-manual/faq/81/3.md  |   26 +
 .../mannual/java-sdk/reference-manual/faq/81/4.md  |   30 +
 .../java-sdk/reference-manual/faq/81/_index.md     |   18 +
 .../mannual/java-sdk/reference-manual/faq/99/0.md  |   30 +
 .../mannual/java-sdk/reference-manual/faq/99/1.md  |   27 +
 .../java-sdk/reference-manual/faq/99/_index.md     |   11 +
 .../java-sdk/reference-manual/faq/_index.md        |   18 +
 .../mannual/java-sdk/reference-manual/faq/intro.md |   53 +
 .../java-sdk/reference-manual/graalvm/_index.md    |    3 +-
 .../reference-manual/graalvm/support-graalvm.md    |  223 ++++
 .../java-sdk/reference-manual/merics/_index.md     |   11 +
 .../java-sdk/reference-manual/merics/meter.md      |  331 +++++
 .../java-sdk/reference-manual/mesh/_index.md       |    3 +-
 .../reference-manual/metadata-center/_index.md     |    2 +-
 .../reference-manual/metadata-center/nacos.md      |    9 +-
 .../reference-manual/metadata-center/others.md     |   84 ++
 .../reference-manual/metadata-center/overview.md   |   12 +-
 .../reference-manual/metadata-center/redis.md      |   13 -
 .../reference-manual/metadata-center/zookeeper.md  |    6 +-
 .../reference-manual/performance/_index.md         |    2 +-
 .../reference-manual/performance/benchmarking.md   |    6 -
 .../java-sdk/reference-manual/protocol/_index.md   |    4 +-
 .../java-sdk/reference-manual/protocol/dubbo.md    |   31 +-
 .../java-sdk/reference-manual/protocol/grpc.md     |   44 -
 .../java-sdk/reference-manual/protocol/hessian.md  |   89 --
 .../java-sdk/reference-manual/protocol/http.md     |   81 --
 .../reference-manual/protocol/memcached.md         |   71 --
 .../reference-manual/protocol/multi-protocols.md   |  136 +++
 .../reference-manual/protocol/others/_index.md     |   11 +
 .../reference-manual/protocol/others/hessian.md    |   87 ++
 .../reference-manual/protocol/others/http.md.bak   |   81 ++
 .../reference-manual/protocol/others/memcached.md  |   57 +
 .../reference-manual/protocol/others/redis.md      |   58 +
 .../reference-manual/protocol/others/rmi.md        |  108 ++
 .../reference-manual/protocol/others/thrift.md     |   49 +
 .../protocol/others/v3.2_rest_protocol_design.md   |  645 ++++++++++
 .../reference-manual/protocol/others/webservice.md |  119 ++
 .../java-sdk/reference-manual/protocol/overview.md |  236 +---
 .../java-sdk/reference-manual/protocol/redis.md    |   71 --
 .../java-sdk/reference-manual/protocol/rest.md     |  760 ------------
 .../java-sdk/reference-manual/protocol/rest.md.bak |  815 +++++++++++++
 .../java-sdk/reference-manual/protocol/rmi.md      |  107 --
 .../java-sdk/reference-manual/protocol/thrift.md   |   61 -
 .../reference-manual/protocol/tripe-rest-manual.md |  969 +++++++++++++++
 .../reference-manual/protocol/triple-3.3.md        |  276 +++++
 .../java-sdk/reference-manual/protocol/triple.md   |  318 +++++
 .../reference-manual/protocol/triple.md.bak        |  170 +++
 .../reference-manual/protocol/triple/_index.md     |   42 -
 .../reference-manual/protocol/triple/guide.md      |  290 -----
 .../reference-manual/protocol/triple/idl.md        |  247 ----
 .../reference-manual/protocol/triple/migration.md  |  102 --
 .../reference-manual/protocol/triple/overview.md   |   51 -
 .../reference-manual/protocol/triple/pojo.md       |  209 ----
 .../reference-manual/protocol/triple/streaming.md  |  164 ---
 .../protocol/v3.2_rest_protocol_design.md          |  659 ----------
 .../reference-manual/protocol/webservice.md        |  124 --
 .../java-sdk/reference-manual/qos/_index.md        |    4 +-
 .../reference-manual/qos/introduction/_index.md    |    7 +
 .../qos/{ => introduction}/command.md              |    0
 .../qos/{ => introduction}/default_metrics.md      |    0
 .../qos/introduction/logger-management.md          |  103 ++
 .../reference-manual/qos/introduction/probe.md     |   43 +
 .../reference-manual/qos/introduction/profiler.md  |   83 ++
 .../qos/introduction/router-snapshot.md            |  119 ++
 .../qos/{ => introduction}/security.md             |    0
 .../qos/{ => introduction}/service-management.md   |    0
 .../reference-manual/qos/logger-management.md      |  102 --
 .../java-sdk/reference-manual/qos/overview.md      |   15 +-
 .../mannual/java-sdk/reference-manual/qos/probe.md |   50 -
 .../java-sdk/reference-manual/qos/profiler.md      |   82 --
 .../java-sdk/reference-manual/qos/qos-list.md      |   53 +
 .../reference-manual/qos/router-snapshot.md        |  118 --
 .../java-sdk/reference-manual/registry/_index.md   |   13 +-
 .../reference-manual/registry/multicast/_index.md  |   60 -
 .../reference-manual/registry/multiple-registry.md |  193 +++
 .../registry/multiple-registry/_index.md           |  195 ---
 .../java-sdk/reference-manual/registry/nacos.md    |  210 ++++
 .../reference-manual/registry/nacos/_index.md      |  199 ---
 .../reference-manual/registry/others/_index.md     |   10 +
 .../reference-manual/registry/others/consul.md     |   53 +
 .../reference-manual/registry/others/etcd.md       |   50 +
 .../reference-manual/registry/others/multicast.md  |   61 +
 .../reference-manual/registry/others/redis.md      |   94 ++
 .../java-sdk/reference-manual/registry/overview.md |   89 ++
 .../reference-manual/registry/overview/_index.md   |   80 --
 .../reference-manual/registry/redis/_index.md      |   83 --
 .../service-discovery-application-vs-interface.md  |  390 ++++++
 .../java-sdk/reference-manual/registry/simple.md   |   66 -
 .../reference-manual/registry/zookeeper.md         |  213 ++++
 .../reference-manual/registry/zookeeper/_index.md  |  142 ---
 .../reference-manual/routing-rule/_index.md        |    7 +
 .../reference-manual/serialization/_index.md       |    5 +-
 .../reference-manual/serialization/avro.md         |   66 -
 .../reference-manual/serialization/dubbo/_index.md |    9 +
 .../reference-manual/serialization/dubbo/avro.md   |   66 +
 .../serialization/dubbo/fastjson.md                |   68 ++
 .../serialization/dubbo/fastjson2.md               |   73 ++
 .../reference-manual/serialization/dubbo/fst.md    |  154 +++
 .../reference-manual/serialization/dubbo/gson.md   |   67 ++
 .../serialization/dubbo/hessian.md                 |   57 +
 .../reference-manual/serialization/dubbo/kryo.md   |  158 +++
 .../serialization/dubbo/msgpack.md                 |   72 ++
 .../reference-manual/serialization/fastjson.md     |   66 -
 .../reference-manual/serialization/fastjson2.md    |   72 --
 .../java-sdk/reference-manual/serialization/fst.md |   71 --
 .../reference-manual/serialization/gson.md         |   66 -
 .../reference-manual/serialization/hessian.md      |   56 -
 .../reference-manual/serialization/kryo.md         |   72 --
 .../reference-manual/serialization/msgpack.md      |   72 --
 .../reference-manual/serialization/protobuf.md     |   59 -
 .../serialization/serialization-upgrade.md         |   39 +
 .../serialization/serialization.md                 |  298 +++++
 .../serialization/triple/_index.md                 |    9 +
 .../serialization/triple/protobuf.md               |   85 ++
 .../serialization/triple/wrapper.md                |   73 ++
 .../java-sdk/reference-manual/spi/_index.md        |    4 +-
 .../reference-manual/spi/description/_index.md     |    8 +-
 .../reference-manual/spi/description/dubbo-spi.md  |  713 -----------
 .../java-sdk/reference-manual/spi/overview.md      |  108 +-
 .../java-sdk/reference-manual/spi/spi-list.md      |  Bin 0 -> 27710 bytes
 .../upgrades-and-compatibility/_index.md           |   11 +
 .../migration-service-discovery.md                 |   77 ++
 .../upgrades-and-compatibility/migration-triple.md |  108 ++
 .../migration-triple.md.bak                        |  346 ++++++
 .../upgrades-and-compatibility/migration.md        |  305 +++++
 .../upgrades-and-compatibility/migration.md.bak    |   97 ++
 .../version/2.x-to-3.x-compatibility-guide.md      |  101 ++
 .../version}/3.0-to-3.1-compatibility-guide.md     |    0
 .../version}/3.1-to-3.2-compatibility-guide.md     |    0
 .../version/3.2-to-3.3-compatibility-guide.md      |  350 ++++++
 .../upgrades-and-compatibility/version/_index.md   |   11 +
 .../overview/mannual/java-sdk/tasks/_index.md      |   10 +
 .../mannual/java-sdk/tasks/deploy/_index.md        |   14 +
 .../tasks/deploy/deploy-on-kubernetes-service.md   |  116 ++
 .../java-sdk/tasks/deploy/deploy-on-kubernetes.md  |   89 ++
 .../mannual/java-sdk/tasks/deploy/deploy-on-vm.md  |  120 ++
 .../mannual/java-sdk/tasks/develop/_index.md       |   10 +
 .../overview/mannual/java-sdk/tasks/develop/api.md |  299 +++++
 .../mannual/java-sdk/tasks/develop/springboot.md   |  207 ++++
 .../mannual/java-sdk/tasks/extensibility/_index.md |   65 +
 .../mannual/java-sdk/tasks/extensibility/filter.md |   94 ++
 .../java-sdk/tasks/extensibility/protocol.md       |  188 +++
 .../java-sdk/tasks/extensibility/registry.md       |  134 +++
 .../mannual/java-sdk/tasks/extensibility/router.md |  149 +++
 .../mannual/java-sdk/tasks/extensibility/spi.md    |   66 +
 .../mannual/java-sdk/tasks/framework/_index.md     |    9 +
 .../mannual/java-sdk/tasks/framework/async.md      |  230 ++++
 .../mannual/java-sdk/tasks/framework/attachment.md |  133 ++
 .../tasks/framework/fault-tolerent-strategy.md     |  107 ++
 .../mannual/java-sdk/tasks/framework/filter.md     |  136 +++
 .../mannual/java-sdk/tasks/framework/generic.md    |  149 +++
 .../java-sdk/tasks/framework/lightweight-rpc.md    |  109 ++
 .../java-sdk/tasks/framework/more/_index.md        |    9 +
 .../tasks/framework/more/callback-parameter.md     |  127 ++
 .../tasks/framework/more/concurrency-control.md    |   92 ++
 .../tasks/framework/more/config-connections.md     |  104 ++
 .../java-sdk/tasks/framework/more/echo-service.md  |   41 +
 .../java-sdk/tasks/framework/more/events-notify.md |  113 ++
 .../tasks/framework/more/explicit-target.md        |   70 ++
 .../java-sdk/tasks/framework/more/generic-impl.md  |   78 ++
 .../java-sdk/tasks/framework/more/local-call.md    |   82 ++
 .../java-sdk/tasks/framework/more/local-mock.md    |  193 +++
 .../java-sdk/tasks/framework/more/local-stub.md    |   63 +
 .../tasks/framework/more/parameter-validation.md   |  200 ++++
 .../java-sdk/tasks/framework/more/reactive.md      |  241 ++++
 .../tasks/framework/more/reference-config-cache.md |   54 +
 .../java-sdk/tasks/framework/more/result-cache.md  |  122 ++
 .../tasks/framework/more/router-snapshot.md        |   89 ++
 .../java-sdk/tasks/framework/more/set-host.md      |   81 ++
 .../java-sdk/tasks/framework/more/specify-ip.md    |  105 ++
 .../java-sdk/tasks/framework/threading-model.md    |  425 +++++++
 .../mannual/java-sdk/tasks/framework/timeout.md    |   79 ++
 .../java-sdk/tasks/framework/version_group.md      |  312 +++++
 .../mannual/java-sdk/tasks/gateway/_index.md       |    8 +
 .../mannual/java-sdk/tasks/gateway/architecture.md |   41 +
 .../mannual/java-sdk/tasks/gateway/dubbo.md        |   81 ++
 .../mannual/java-sdk/tasks/gateway/triple.md       |  256 ++++
 .../overview/mannual/java-sdk/tasks/mesh/_index.md |   44 +
 .../tasks/mesh/bookinfo-proxyless/_index.md        |   48 +
 .../mesh/bookinfo-proxyless/security/_index.md     |   92 ++
 .../bookinfo-proxyless/security/request-routing.md |  152 +++
 .../mesh/bookinfo-proxyless/traffic/_index.md      |   92 ++
 .../bookinfo-proxyless/traffic/request-routing.md  |  152 +++
 .../java-sdk/tasks/mesh/bookinfo-sidecar/_index.md |   48 +
 .../tasks/mesh/bookinfo-sidecar/security/_index.md |   92 ++
 .../bookinfo-sidecar/security/request-routing.md   |  152 +++
 .../tasks/mesh/bookinfo-sidecar/traffic/_index.md  |   92 ++
 .../bookinfo-sidecar/traffic/request-routing.md    |  152 +++
 .../java-sdk/tasks/mesh/migration/_index.md        |   43 +
 .../java-sdk/tasks/mesh/migration/deploy-on-k8s.md |  323 +++++
 .../java-sdk/tasks/mesh/migration/dubbo-mesh.md    |  302 +++++
 .../java-sdk/tasks/mesh/migration/proxyless.md     |  275 +++++
 .../mannual/java-sdk/tasks/observability/_index.md |   10 +
 .../java-sdk/tasks/observability/console.md        |  112 ++
 .../java-sdk/tasks/observability/grafana.md        |   93 ++
 .../java-sdk/tasks/observability/logging.md        |  361 ++++++
 .../java-sdk/tasks/observability/prometheus.md     |   52 +
 .../java-sdk/tasks/observability/tracing/_index.md |   55 +
 .../java-sdk/tasks/observability/tracing/otlp.md   |  135 +++
 .../tasks/observability/tracing/skywalking.md      |   83 ++
 .../tasks/observability/tracing/tracing.md         |  147 +++
 .../java-sdk/tasks/observability/tracing/zipkin.md |  159 +++
 .../mannual/java-sdk/tasks/protocols/_index.md     |   12 +
 .../mannual/java-sdk/tasks/protocols/dubbo.md      |  119 ++
 .../mannual/java-sdk/tasks/protocols/protocol.md   |  250 ++++
 .../mannual/java-sdk/tasks/protocols/rest.md       |  188 +++
 .../java-sdk/tasks/protocols/triple/_index.md      |   12 +
 .../java-sdk/tasks/protocols/triple/grpc.md        |   67 ++
 .../mannual/java-sdk/tasks/protocols/triple/idl.md |  290 +++++
 .../java-sdk/tasks/protocols/triple/interface.md   |  148 +++
 .../java-sdk/tasks/protocols/triple/streaming.md   |  325 +++++
 .../mannual/java-sdk/tasks/rate-limit/_index.md    |   11 +
 .../rate-limit/adaptive-concurrency-control.md     |   48 +
 .../tasks/rate-limit/concurrency-control.md        |  101 ++
 .../mannual/java-sdk/tasks/rate-limit/sentinel.md  |  228 ++++
 .../mannual/java-sdk/tasks/security/_index.md      |   10 +
 .../mannual/java-sdk/tasks/security/auth.md        |   51 +
 .../mannual/java-sdk/tasks/security/class-check.md |  223 ++++
 .../mannual/java-sdk/tasks/security/tls.md         |   64 +
 .../java-sdk/tasks/security/token-authorization.md |   59 +
 .../java-sdk/tasks/service-discovery/_index.md     |   10 +
 .../java-sdk/tasks/service-discovery/kubernetes.md |   25 +
 .../tasks/service-discovery/loadbalance.md         |  120 ++
 .../java-sdk/tasks/service-discovery/nacos.md      |  219 ++++
 .../java-sdk/tasks/service-discovery/registry.md   |  273 +++++
 .../java-sdk/tasks/service-discovery/zookeeper.md  |  218 ++++
 .../java-sdk/tasks/traffic-management/_index.md    |  118 ++
 .../java-sdk/tasks/traffic-management/accesslog.md |   87 ++
 .../tasks/traffic-management/architecture.md       |  201 ++++
 .../java-sdk/tasks/traffic-management/arguments.md |   88 ++
 .../java-sdk/tasks/traffic-management/host.md      |   69 ++
 .../java-sdk/tasks/traffic-management/isolation.md |  138 +++
 .../java-sdk/tasks/traffic-management/mock.md      |   72 ++
 .../java-sdk/tasks/traffic-management/region.md    |   85 ++
 .../java-sdk/tasks/traffic-management/retry.md     |   75 ++
 .../java-sdk/tasks/traffic-management/route.md     |   56 +
 .../java-sdk/tasks/traffic-management/timeout.md   |   72 ++
 .../java-sdk/tasks/traffic-management/weight.md    |   94 ++
 .../mannual/java-sdk/tasks/trasaction/_index.md    |    9 +
 .../tasks/trasaction/distributed-transaction.md    |  159 +++
 .../mannual/java-sdk/tasks/troubleshoot/_index.md  |   10 +
 .../java-sdk/tasks/troubleshoot/no-provider.md     |  601 ++++++++++
 .../java-sdk/tasks/troubleshoot/profiler.md        |  190 +++
 .../java-sdk/tasks/troubleshoot/request-failed.md  |  166 +++
 .../java-sdk/tasks/troubleshoot/start-failed.md    |  253 ++++
 .../2.x-to-3.x-compatibility-guide.md              |  104 --
 .../3.2-to-3.3-compatibility-guide.md              |   28 -
 .../java-sdk/upgrades-and-compatibility/_index.md  |   10 -
 .../upgrades-and-compatibility/migration-triple.md |  350 ------
 .../protobuf&interface.md                          |  152 ---
 .../serialization-upgrade.md                       |   38 -
 .../service-discovery/_index.md                    |   10 -
 .../migration-service-discovery.md                 |  168 ---
 .../service-discovery/service-discovery-rule.md    |  Bin 9327 -> 0 bytes
 .../service-discovery/service-discovery-samples.md |   87 --
 .../upgrades-and-compatibility/version/_index.md   |   42 -
 .../zh-cn/overview/mannual/java-sdk/versions.md    |   23 +
 .../zh-cn/overview/mannual/nodejs-sdk/_index.md    |    7 +
 .../overview/mannual/nodejs-sdk/quick-start.md     |  186 +++
 content/zh-cn/overview/mannual/rust-sdk/_index.md  |    2 +-
 .../zh-cn/overview/mannual/rust-sdk/quick-start.md |   36 +-
 .../overview/mannual/rust-sdk/service-discovery.md |    4 -
 content/zh-cn/overview/mannual/web-sdk/_index.md   |    7 +
 .../zh-cn/overview/mannual/web-sdk/quick-start.md  |  267 +++++
 content/zh-cn/overview/quickstart/_index.md        |   69 --
 content/zh-cn/overview/quickstart/go/_index.md     |   52 -
 content/zh-cn/overview/quickstart/go/install.md    |   49 -
 .../overview/quickstart/go/quickstart_triple.md    |  124 --
 .../go/quickstart_triple_with_customize.md         |  212 ----
 content/zh-cn/overview/quickstart/java/_index.md   |   42 -
 content/zh-cn/overview/quickstart/java/brief.md    |  313 -----
 .../zh-cn/overview/quickstart/java/spring-boot.md  |  571 ---------
 content/zh-cn/overview/quickstart/nodejs/_index.md |   12 -
 content/zh-cn/overview/quickstart/rust/_index.md   |  253 ----
 .../overview/reference/Metrics/standard_metrics.md |    2 +
 content/zh-cn/overview/reference/_index.md         |   10 -
 content/zh-cn/overview/reference/admin/_index.md   |    7 -
 .../zh-cn/overview/reference/admin/architecture.md |  293 -----
 .../overview/reference/admin/documentation.md      |   14 -
 content/zh-cn/overview/reference/admin/mock.md     |  173 ---
 content/zh-cn/overview/reference/admin/search.md   |   52 -
 content/zh-cn/overview/reference/admin/test.md     |  190 ---
 .../zh-cn/overview/reference/erlang-sdk/_index.md  |   12 +
 .../overview/reference/erlang-sdk/quick-start.md   |   71 ++
 .../overview/reference/erlang-sdk/reference.md     |   34 +
 .../overview/reference/erlang-sdk/serialization.md |   36 +
 .../zh-cn/overview/reference/erlang-sdk/service.md |   40 +
 .../overview/reference/integrations/grafana.md     |    2 +-
 .../overview/reference/integrations/higress.md     |   48 +
 .../zh-cn/overview/reference/integrations/nacos.md |   50 +
 .../overview/reference/integrations/prometheus.md  |    2 +-
 .../overview/reference/integrations/skywalking.md  |    2 +-
 .../overview/reference/integrations/zipkin.md      |    2 +-
 .../overview/reference/integrations/zookeeper.md   |   92 ++
 content/zh-cn/overview/reference/pixiu/_index.md   |   12 +
 .../zh-cn/overview/reference/pixiu/dev/_index.md   |   10 +
 .../overview/reference/pixiu/dev/dubbo-pilot.md    |  203 ++++
 .../reference/pixiu/dev/filter-extension.md        |  143 +++
 content/zh-cn/overview/reference/pixiu/dev/trie.md |  147 +++
 .../overview/reference/pixiu/overview/_index.md    |   12 +
 .../zh-cn/overview/reference/pixiu/overview/faq.md |   30 +
 .../reference/pixiu/overview/terminology.md        |   44 +
 .../reference/pixiu/overview/what-is-pixiu.md      |   48 +
 .../zh-cn/overview/reference/pixiu/user/_index.md  |   12 +
 .../reference/pixiu/user/adapter/_index.md         |   12 +
 .../overview/reference/pixiu/user/adapter/dubbo.md |   12 +
 .../reference/pixiu/user/adapter/springcloud.md    |   12 +
 .../reference/pixiu/user/appendix/_index.md        |   12 +
 .../appendix/http-to-dubbo-default-stragety.md     |  327 +++++
 .../reference/pixiu/user/configurations.md         |  160 +++
 .../overview/reference/pixiu/user/deployment.md    |   90 ++
 .../reference/pixiu/user/httpfilter/_index.md      |   12 +
 .../pixiu}/user/httpfilter/dubbo.md                |    0
 .../reference/pixiu/user/httpfilter/hystrix.md     |   19 +
 .../reference/pixiu/user/httpfilter/ratelimit.md   |   19 +
 .../reference/pixiu/user/listener/_index.md        |   12 +
 .../overview/reference/pixiu/user/listener/http.md |   53 +
 .../reference/pixiu/user/listener/http2.md         |   19 +
 .../overview/reference/pixiu/user/listener/tcp.md  |   19 +
 .../reference/pixiu/user/listener/triple.md        |   19 +
 .../reference/pixiu/user/networkfilter/_index.md   |   12 +
 .../reference/pixiu/user/networkfilter/dubbo.md    |   19 +
 .../pixiu}/user/networkfilter/grpc.md              |    0
 .../reference/pixiu/user/networkfilter/http.md     |   19 +
 .../reference/pixiu/user/quality/_index.md         |   12 +
 .../reference/pixiu/user/quality/performance.md    |   19 +
 .../reference/pixiu/user/quality/stability.md      |   19 +
 .../overview/reference/pixiu/user/quickstart.md    |  171 +++
 .../reference/pixiu/user/samples/_index.md         |   12 +
 .../reference/pixiu/user/samples/http_proxy.md     |   75 ++
 .../reference/pixiu/user/samples/http_to_dubbo.md  |   19 +
 .../overview/reference/pixiu/user/samples/https.md |   19 +
 .../overview/reference/protoc-installation.md      |   73 ++
 content/zh-cn/overview/reference/protocols/http.md |    4 +
 content/zh-cn/overview/tasks/_index.md             |    9 -
 content/zh-cn/overview/tasks/deploy/_index.md      |   66 -
 .../overview/tasks/deploy/deploy-on-docker.md      |  221 ----
 .../tasks/deploy/deploy-on-k8s-containerd.md       |  232 ----
 .../overview/tasks/deploy/deploy-on-k8s-docker.md  |  226 ----
 .../zh-cn/overview/tasks/deploy/deploy-on-vm.md    |  199 ---
 content/zh-cn/overview/tasks/develop/_index.md     |   82 --
 content/zh-cn/overview/tasks/develop/async.md      |  168 ---
 content/zh-cn/overview/tasks/develop/context.md    |  104 --
 content/zh-cn/overview/tasks/develop/generic.md    |   73 --
 content/zh-cn/overview/tasks/develop/idl.md        |  242 ----
 .../overview/tasks/develop/service_reference.md    |  131 --
 content/zh-cn/overview/tasks/develop/template.md   |   61 -
 .../zh-cn/overview/tasks/develop/version_group.md  |   78 --
 content/zh-cn/overview/tasks/ecosystem/_index.md   |   70 --
 .../overview/tasks/ecosystem/configuration.md      |   12 -
 content/zh-cn/overview/tasks/ecosystem/gateway.md  |  242 ----
 .../overview/tasks/ecosystem/metadata-center.md    |   12 -
 content/zh-cn/overview/tasks/ecosystem/registry.md |   12 -
 .../zh-cn/overview/tasks/ecosystem/transaction.md  |  312 -----
 .../zh-cn/overview/tasks/extensibility/_index.md   |  103 --
 .../zh-cn/overview/tasks/extensibility/filter.md   |  158 ---
 .../zh-cn/overview/tasks/extensibility/protocol.md |  274 -----
 .../zh-cn/overview/tasks/extensibility/registry.md |   12 -
 .../zh-cn/overview/tasks/extensibility/router.md   |  220 ----
 content/zh-cn/overview/tasks/mesh/_index.md        |   43 -
 .../tasks/mesh/bookinfo-proxyless/_index.md        |   47 -
 .../mesh/bookinfo-proxyless/security/_index.md     |   91 --
 .../bookinfo-proxyless/security/request-routing.md |  151 ---
 .../mesh/bookinfo-proxyless/traffic/_index.md      |   91 --
 .../bookinfo-proxyless/traffic/request-routing.md  |  151 ---
 .../overview/tasks/mesh/bookinfo-sidecar/_index.md |   47 -
 .../tasks/mesh/bookinfo-sidecar/security/_index.md |   91 --
 .../bookinfo-sidecar/security/request-routing.md   |  151 ---
 .../tasks/mesh/bookinfo-sidecar/traffic/_index.md  |   91 --
 .../bookinfo-sidecar/traffic/request-routing.md    |  151 ---
 .../zh-cn/overview/tasks/mesh/migration/_index.md  |   42 -
 .../overview/tasks/mesh/migration/deploy-on-k8s.md |  322 -----
 .../overview/tasks/mesh/migration/dubbo-mesh.md    |  301 -----
 .../overview/tasks/mesh/migration/proxyless.md     |  274 -----
 .../zh-cn/overview/tasks/observability/_index.md   |   85 --
 .../zh-cn/overview/tasks/observability/admin.md    |   92 --
 .../zh-cn/overview/tasks/observability/grafana.md  |   81 --
 .../overview/tasks/observability/prometheus.md     |   40 -
 .../overview/tasks/observability/tracing/_index.md |  164 ---
 .../overview/tasks/observability/tracing/otlp.md   |  134 ---
 .../tasks/observability/tracing/skywalking.md      |   82 --
 .../overview/tasks/observability/tracing/zipkin.md |  158 ---
 content/zh-cn/overview/tasks/protocols/_index.md   |   63 -
 content/zh-cn/overview/tasks/protocols/dubbo.md    |    9 -
 content/zh-cn/overview/tasks/protocols/grpc.md     |   11 -
 .../overview/tasks/protocols/multi-protocols.md    |  132 --
 .../zh-cn/overview/tasks/protocols/springcloud.md  |   12 -
 content/zh-cn/overview/tasks/protocols/triple.md   |    9 -
 content/zh-cn/overview/tasks/protocols/web.md      |   50 -
 content/zh-cn/overview/tasks/rate-limit/_index.md  |   48 -
 content/zh-cn/overview/tasks/rate-limit/hystrix.md |  173 ---
 .../overview/tasks/rate-limit/resilience4j.md      |   11 -
 .../zh-cn/overview/tasks/rate-limit/sentinel.md    |  101 --
 .../overview/tasks/traffic-management/_index.md    |  198 ---
 .../overview/tasks/traffic-management/accesslog.md |   85 --
 .../overview/tasks/traffic-management/arguments.md |   87 --
 .../overview/tasks/traffic-management/host.md      |   68 --
 .../overview/tasks/traffic-management/isolation.md |  109 --
 .../overview/tasks/traffic-management/mock.md      |   71 --
 .../overview/tasks/traffic-management/region.md    |   84 --
 .../overview/tasks/traffic-management/retry.md     |   74 --
 .../overview/tasks/traffic-management/timeout.md   |   73 --
 .../overview/tasks/traffic-management/weight.md    |   93 --
 .../zh-cn/overview/tasks/troubleshoot/_index.md    |    9 -
 .../overview/tasks/troubleshoot/no-provider.md     |  600 ----------
 .../overview/tasks/troubleshoot/request-failed.md  |  165 ---
 .../overview/tasks/troubleshoot/start-failed.md    |  252 ----
 content/zh-cn/overview/what/_index.md              |    2 +-
 .../zh-cn/overview/what/core-features/_index.md    |   10 +
 .../zh-cn/overview/what/core-features/ecosystem.md |   46 +
 .../overview/what/core-features/extensibility.md   |  123 ++
 .../overview/what/core-features/load-balance.md    |  105 ++
 content/zh-cn/overview/what/core-features/more.md  |   72 ++
 .../overview/what/core-features/observability.md   |   60 +
 .../zh-cn/overview/what/core-features/protocols.md |   89 ++
 .../zh-cn/overview/what/core-features/security.md  |  109 ++
 .../what/core-features/service-definition.md       |  129 ++
 .../core-features/service-definition.md.bak        |    0
 .../what/core-features/service-discovery.md        |   73 ++
 .../overview/what/core-features/service-mesh.md    |   90 ++
 .../overview/what/core-features/traffic/_index.md  |  275 +++++
 .../what/core-features/traffic/circuit-breaking.md |   43 +
 .../what/core-features/traffic/condition-rule.md   |   79 ++
 .../core-features/traffic/configuration-rule.md    |   95 ++
 .../what/core-features/traffic/introduction.md     |  268 +++++
 .../what/core-features/traffic/mesh-rule.md        |  373 ++++++
 .../what/core-features/traffic/script-rule.md      |   64 +
 .../what/core-features/traffic/tag-rule.md         |   62 +
 data/announcements/zh/scheduled.yaml               |   11 +
 data/download/en/1javaReleases.yaml                |   20 +-
 data/download/zh/1javaReleases.yaml                |   20 +-
 go.mod                                             |    5 +-
 go.sum                                             |   13 +-
 i18n/en.toml                                       |   56 +-
 i18n/zh-cn.toml                                    |   52 +-
 layouts/_default/baseof.html                       |    2 +-
 layouts/partials/footer.html                       |  241 +++-
 layouts/partials/navbar-collapse-commuity.html     |   16 +
 layouts/partials/navbar-collapse-ecosystem.html    |   17 +
 layouts/partials/navbar-community-selector.html    |    9 +
 layouts/partials/navbar-ecosystem-selector.html    |    9 +
 layouts/partials/navbar-lang-selector.html         |   55 +-
 layouts/partials/navbar-menu-list-mobile.html      |   48 +
 layouts/partials/navbar.html                       |  219 +++-
 layouts/partials/scripts.html                      |   53 +-
 layouts/shortcodes/blocks/cover.html               |  197 ++-
 layouts/shortcodes/blocks/demo-en.html             |  252 ++++
 layouts/shortcodes/blocks/demo-zh.html             |  252 ++++
 static/css/language.css                            |   84 +-
 .../0e6b75c3-3340-4bed-a566-88c46a03ada6.png       |  Bin 0 -> 70351 bytes
 .../53a6f3c7-20ad-49f6-abc0-4e2d80a9597d.png       |  Bin 0 -> 638971 bytes
 .../5f8ebef5-08f3-463a-bb86-14b32a09ebb2.png       |  Bin 0 -> 750937 bytes
 .../68b69954-9df2-48b2-bd63-fe07ba8cb25b.png       |  Bin 0 -> 878159 bytes
 .../78d6744b-928a-41d4-857c-ff91ad69c896.png       |  Bin 0 -> 1109403 bytes
 .../7e4f3ced-9932-472f-bb8f-272ec97a7fbe.png       |  Bin 0 -> 898694 bytes
 .../c7d4f983-f619-4d39-94b6-5d62fd5a430e.png       |  Bin 0 -> 675717 bytes
 .../ee5812e0-a90b-4a02-abab-b658cdddefc1.png       |  Bin 0 -> 438261 bytes
 static/imgs/demo/img.png                           |  Bin 0 -> 201433 bytes
 static/imgs/demo/online-boutique-arch.png          |  Bin 0 -> 201433 bytes
 static/imgs/docs3-v2/java-sdk/seata/flow.png       |  Bin 0 -> 62564 bytes
 static/imgs/golang/architecture/arc.png            |  Bin 0 -> 2068065 bytes
 static/imgs/golang/architecture/filter.png         |  Bin 0 -> 1317083 bytes
 static/imgs/golang/architecture/language.png       |  Bin 0 -> 1357725 bytes
 static/imgs/golang/architecture/protocol.png       |  Bin 0 -> 360649 bytes
 static/imgs/golang/architecture/streaming.png      |  Bin 0 -> 110886 bytes
 static/imgs/golang/metrics/dashboard.png           |  Bin 0 -> 250099 bytes
 static/imgs/golang/metrics/datasource.png          |  Bin 0 -> 97773 bytes
 static/imgs/golang/metrics/import-datasource.png   |  Bin 0 -> 91148 bytes
 static/imgs/golang/metrics/import-json.png         |  Bin 0 -> 104299 bytes
 static/imgs/golang/metrics/import.png              |  Bin 0 -> 65239 bytes
 static/imgs/golang/metrics/podmonitor.png          |  Bin 0 -> 85451 bytes
 .../v3/manual/java/migration/dubbo-to-triple.png   |  Bin 0 -> 145511 bytes
 static/imgs/v3/manual/java/multi-instance/arch.png |  Bin 0 -> 193476 bytes
 static/imgs/v3/manual/java/protocol/http3-arch.jpg |  Bin 0 -> 136852 bytes
 static/imgs/v3/manual/java/protocol/http3-qps.jpg  |  Bin 0 -> 92227 bytes
 static/imgs/v3/manual/java/protocol/http3-rt.jpg   |  Bin 0 -> 80611 bytes
 static/imgs/v3/manual/java/protocol/rest-arg.jpg   |  Bin 0 -> 57283 bytes
 .../tutorial/kubernetes/kubernetes-service.png     |  Bin 0 -> 352920 bytes
 .../manual/java/tutorial/kubernetes/kubernetes.png |  Bin 0 -> 368691 bytes
 static/imgs/v3/quickstart/samples.jpg              |  Bin 0 -> 133568 bytes
 static/imgs/v3/quickstart/start.jpg                |  Bin 0 -> 486805 bytes
 static/imgs/v3/tasks/framework/cluster-filter.png  |  Bin 0 -> 188681 bytes
 static/imgs/v3/tasks/framework/filter.png          |  Bin 0 -> 107064 bytes
 .../imgs/v3/tasks/framework/timeout-deadline.png   |  Bin 0 -> 534309 bytes
 static/imgs/v3/tasks/framework/timeout.png         |  Bin 0 -> 548684 bytes
 .../imgs/v3/tasks/gateway/apisix-nacos-dubbo.png   |  Bin 0 -> 898494 bytes
 .../imgs/v3/tasks/gateway/arch-centralized-bff.png |  Bin 0 -> 926820 bytes
 .../v3/tasks/gateway/arch-decentralized-dubbo.png  |  Bin 0 -> 723982 bytes
 static/imgs/v3/tasks/gateway/dubbo-gateway.png     |  Bin 0 -> 371913 bytes
 static/imgs/v3/tasks/gateway/dubbo-rest.png        |  Bin 0 -> 933454 bytes
 static/imgs/v3/tasks/gateway/http-to-dubbo.png     |  Bin 0 -> 859261 bytes
 static/imgs/v3/tasks/gateway/http-to-triple.png    |  Bin 0 -> 872627 bytes
 static/imgs/v3/tasks/gateway/nacos.png             |  Bin 0 -> 2216 bytes
 static/imgs/v3/tasks/gateway/triple-gateway.png    |  Bin 0 -> 460958 bytes
 static/imgs/v3/tasks/gateway/triple-higress.png    |  Bin 0 -> 801237 bytes
 .../protocol/multiple-protocols-on-same-port.png   |  Bin 0 -> 663037 bytes
 .../imgs/v3/tasks/protocol/multiple-protocols.png  |  Bin 0 -> 762412 bytes
 static/imgs/v3/tasks/protocol/triple-grpc.png      |  Bin 0 -> 1998879 bytes
 static/imgs/v3/tasks/registry/formula.png          |  Bin 0 -> 32889 bytes
 .../imgs/v3/tasks/registry/zookeeper-hierarchy.png |  Bin 0 -> 369144 bytes
 .../imgs/v3/tasks/registry/zookeeper-mapping.png   |  Bin 0 -> 228418 bytes
 .../imgs/v3/tasks/registry/zookeeper-metadata.png  |  Bin 0 -> 608221 bytes
 static/imgs/v3/tasks/sentinel/dashboard-1.png      |  Bin 0 -> 225866 bytes
 static/imgs/v3/tasks/sentinel/dashboard-2.png      |  Bin 0 -> 735258 bytes
 static/imgs/v3/tasks/sentinel/dashboard-3.png      |  Bin 0 -> 2031102 bytes
 static/imgs/v3/tasks/sentinel/dashboard-4.png      |  Bin 0 -> 293534 bytes
 static/imgs/v3/tasks/sentinel/dashboard-5.png      |  Bin 0 -> 234367 bytes
 static/js/script.js                                |    3 +-
 static/release/downloadDubbo.sh                    |  100 ++
 static/release/downloadDubboCtl.sh                 |  100 ++
 1307 files changed, 47959 insertions(+), 45819 deletions(-)

diff --git a/.github/workflows/build_and_deploy_history.yml b/.github/workflows/build_and_deploy_history.yml
index c25fd94c3a7..8a91fed44c4 100644
--- a/.github/workflows/build_and_deploy_history.yml
+++ b/.github/workflows/build_and_deploy_history.yml
@@ -23,7 +23,7 @@ jobs:
       - name: Setup Hugo
         uses: peaceiris/actions-hugo@v2
         with:
-          hugo-version: 'latest'
+          hugo-version: '0.121.2'
           extended: true
       - name: Build
         env:
diff --git a/.github/workflows/link_check.yml b/.github/workflows/link_check.yml
index a80e74a76ee..9a56600953f 100644
--- a/.github/workflows/link_check.yml
+++ b/.github/workflows/link_check.yml
@@ -25,7 +25,7 @@ jobs:
       - name: Setup Hugo
         uses: peaceiris/actions-hugo@v2
         with:
-          hugo-version: '0.122.0'
+          hugo-version: '0.121.2'
           extended: true
       - name: Build
         env:
diff --git a/.htmltest.yml b/.htmltest.yml
index 44b93ede5a5..bd5fb65df81 100644
--- a/.htmltest.yml
+++ b/.htmltest.yml
@@ -1,6 +1,6 @@
 DirectoryPath: public
-IgnoreAltMissing: false
-IgnoreAltEmpty: false
+IgnoreAltMissing: true
+IgnoreAltEmpty: true
 IgnoreInternalEmptyHash: true
 IgnoreDirectoryMissingTrailingSlash: true
 IgnoreCanonicalBrokenLinks: false
diff --git a/assets/scss/_base.scss b/assets/scss/_base.scss
index dc8a3b87e98..bf146fbf548 100755
--- a/assets/scss/_base.scss
+++ b/assets/scss/_base.scss
@@ -149,7 +149,7 @@ main {
 // HERO
 .header-hero {
   background-image: url(/imgs/texture.png);
-  background-color: $blue;
+  background-color: $gray;
   text-align: center;
   padding-left: 0;
   padding-right: 0;
@@ -181,7 +181,7 @@ main {
 }
 
 .header-hero {
-  background-color: $blue;
+  background-color: $gray;
 
   h5 {
     margin: 20px 0;
diff --git a/assets/scss/_buttons.scss b/assets/scss/_buttons.scss
new file mode 100644
index 00000000000..2139b5b4ca9
--- /dev/null
+++ b/assets/scss/_buttons.scss
@@ -0,0 +1,15 @@
+// Buttons
+
+@if $enable-rounded {
+  .btn {
+    border-radius: 1rem;
+
+    &-lg {
+      border-radius: 2rem;
+    }
+
+    &-sm {
+      border-radius: 1rem;
+    }
+  }
+}
diff --git a/assets/scss/_case-studies.scss b/assets/scss/_case-studies.scss
index 4f448641275..52eea8acf94 100755
--- a/assets/scss/_case-studies.scss
+++ b/assets/scss/_case-studies.scss
@@ -66,7 +66,7 @@ h2 {
 }
 
 body footer {
-  background-color: #585858 !important;
+  background-color: #F4F4F6 !important;
 }
 
 .section1 {
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index 88b5c91c488..7158c8b8bda 100755
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -3,6 +3,7 @@ $announcement-size-adjustment: 8px;
 /* GLOBAL */
 .td-main {
   .row {
+    --bs-gutter-x: 4rem;
     margin: 0;
   }
 
@@ -24,6 +25,10 @@ $announcement-size-adjustment: 8px;
   .ui-widget-content a {
     color: $blue;
   }
+
+  a {
+    text-decoration: none;
+  }
 }
 
 .footer-margin-0{
@@ -106,17 +111,18 @@ body.td-404 main .error-details {
 .td-navbar {
   position: fixed !important;
   width: 100%;
-  padding-bottom: 1rem !important;
+  height: 40px;
   background: transparent !important;
   transition: 0.3s;
+  padding: 1rem;
 
   .navbar-brand {
-    position: absolute;
-    width: 45px;
-    height: 44px;
+    // position: absolute;
+    width: 96px;
+    height: 20px;
     background-repeat: no-repeat;
     background-size: contain;
-    background-image: url("/imgs/favicon.png");
+    background-image: url("/imgs/nav_logo2.png");
   }
 
   #hamburger {
@@ -135,9 +141,11 @@ body.td-404 main .error-details {
   }
 }
 
+
+
 .td-navbar-nav-scroll {
   overflow: visible !important;
-  display: none;
+  // display: none;
 
   .navbar-nav {
     overflow: visible !important;
@@ -146,6 +154,7 @@ body.td-404 main .error-details {
     flex-direction: row;
     flex-wrap: wrap;
     justify-content: space-evenly;
+    padding-bottom: 0px!important;
 
     .nav-item {
       position: relative;
@@ -154,7 +163,7 @@ body.td-404 main .error-details {
       .active::after {
         position: absolute;
         width: 100%;
-        height: 2px;
+        height: 0px;
         content: "";
         bottom: -4px;
         left: 0;
@@ -163,21 +172,22 @@ body.td-404 main .error-details {
     }
   }
 
+
   @media only screen and (min-width: 768px) {
-    display: block;
-    margin-top: 3.5rem !important;
+    display: flex!important;
+    align-items: center!important;
   }
 
-  @media only screen and (min-width: 1075px) {
-    margin-top: 1rem !important;
-  }
 }
 
+
 // Flip-Nav
 .flip-nav .td-navbar {
-  background-color: white !important;
-  // box-shadow: 0 1px 2px $medium-grey;
-  border: 1px solid #ddd;
+  // background-color: #EBECEF !important;
+  .dropdown {
+    min-width: 0px;
+
+  }
   .navbar-nav {
     .nav-item {
       &.show .nav-link,
@@ -194,6 +204,24 @@ body.td-404 main .error-details {
           color: $medium-grey;
         }
       }
+      .nav-link {
+        font-size: 14px;
+        font-weight: 400;
+        color: #597371;
+        &:hover {
+          color:#49615f;
+        }
+      }
+    }
+    .nav-item-line ::after{
+      content:"";
+      position: absolute;
+      top: 50%;
+      transform: translateY(-50%);
+      left: 100%;
+      width: 1px;
+      height: 16px;
+      background-color: #8FA8A6;
     }
   }
 
@@ -659,7 +687,7 @@ body.td-documentation {
     margin-bottom: 0px;
 
     // for padding-top see _size.scss
-    padding-bottom: calc(max(2em, 2rem));
+    padding-bottom: calc(max(1em, 1rem));
 
     max-width: calc(min(1200px - 8em, 80vw));
   }
@@ -687,7 +715,7 @@ body.td-documentation {
 @media (min-width: 992px) {
   #announcement aside { // more specific
     .announcement-main {
-      padding-top: calc(max(8em, 8rem));
+      padding-top: calc(max(6em, 6rem));
     }
   }
 }
@@ -860,10 +888,27 @@ div.alert > em.javascript-required {
   margin: calc(max(4em, ( 8vh + 4em ) / 2)) 0 0.25em 0;
 }
 
-#td-sidebar-menu{
-  overflow: auto;
-  white-space: nowrap;
+#docsearch {
+  .DocSearch-Button {
+    background: #DDDEE4;
+    padding: 0 10px !important;
+  }
+  .DocSearch-Button-Container{
+    width: 15px;
+  }
+  .DocSearch-Button-Placeholder{
+    font-size: 12px;
+    display: none;
+  }
+  .DocSearch-Button-Keys{
+    display: none;
+  }
+}
+
+#language .btn-language {
+    width: 156px;
+    height: 40px;
+    margin-right: 16px;
+    margin-bottom: 12px;
+    border-radius: 24px;
 }
-.td-page-meta a{
-  display: inline-block !important;
-}
\ No newline at end of file
diff --git a/assets/scss/_skin.scss b/assets/scss/_skin.scss
index 32c94b9dc52..4d5a1bc8103 100755
--- a/assets/scss/_skin.scss
+++ b/assets/scss/_skin.scss
@@ -3,3 +3,4 @@ $light-grey: #f7f7f7;
 $dark-grey: #303030;
 $medium-grey: #4c4c4c;
 $white: #ffffff;
+$gray: #EBECEF;
diff --git a/assets/scss/main.scss b/assets/scss/main.scss
index 1674155188f..82efa2e46e8 100644
--- a/assets/scss/main.scss
+++ b/assets/scss/main.scss
@@ -1,9 +1,11 @@
-@import "support/functions";
+@import "../vendor/bootstrap/scss/functions";
+@import "_variables_forward";
 @import "variables_project";
 @import "variables";
 @import "support/mixins";
 
 @import "../vendor/bootstrap/scss/bootstrap";
+@import "support/bootstrap_vers_test";
 
 @import "../vendor/Font-Awesome/scss/fontawesome.scss";
 @import "../vendor/Font-Awesome/scss/solid.scss";
@@ -11,6 +13,7 @@
 
 @import "support/utilities";
 @import "colors";
+@import "table";
 @import "boxes";
 @import "blog";
 @import "code";
@@ -18,7 +21,6 @@
 @import "sidebar-tree";
 @import "sidebar-toc";
 @import "buttons";
-@import "breadcrumb";
 @import "alerts";
 @import "content";
 @import "search";
@@ -27,6 +29,9 @@
 @import "section-index";
 @import "pageinfo";
 @import "taxonomy";
+@import "drawio";
+@import "shortcodes";
+@import "swagger";
 
 @if $td-enable-google-fonts {
     @import url("/css/open-sans.css");
@@ -98,4 +103,4 @@ footer {
 @import "tablet";
 @import "desktop";
 @import "reset";
-@import "size";
\ No newline at end of file
+@import "size";
diff --git a/cn_config.toml b/cn_config.toml
index 00198e97de0..8fd6d8df161 100644
--- a/cn_config.toml
+++ b/cn_config.toml
@@ -55,7 +55,7 @@ defaultContentLanguageInSubdir = false
 [languages.en]
 title = "Apache Dubbo"
 description = "Apache Dubbo Official Website"
-languageName = "English"
+languageName = "EN"
 contentDir = "content/en"
 # Weight used for sorting.
 weight = 1
@@ -208,6 +208,26 @@ url = "mailto:dev-subscribe@dubbo.apache.org"
 icon = "fa fa-envelope"
 desc = "Discuss development issues around the project"
 
+
+[params.ecosystem]
+navLabel = "生态"
+  [params.ecosystem.navOptions]
+    [[params.ecosystem.navOptions.items]]
+        name = "Launch A Project"
+        url = "/zh-cn/blog"
+    [[params.ecosystem.navOptions.items]]
+        name = "可视化控制台"
+        url = "/zh-cn/download"
+    [[params.ecosystem.navOptions.items]]
+        name = "商城系统"
+        url = "/option-3"
+    [[params.ecosystem.navOptions.items]]
+        name = "Benchmark"
+        url = "/option-3"
+    [[params.ecosystem.navOptions.items]]
+        name = "Proxyless Mesh"
+        url = "/option-3"
+
 [sitemap]
 changefreq = "monthly"
 filename = "sitemap.xml"
diff --git a/config.toml b/config.toml
index 52ca0c53ec5..e7464afad88 100644
--- a/config.toml
+++ b/config.toml
@@ -55,7 +55,7 @@ defaultContentLanguageInSubdir = false
 [languages.en]
 title = "Apache Dubbo"
 description = "Apache Dubbo Official Website"
-languageName = "English"
+languageName = "EN"
 contentDir = "content/en"
 # Weight used for sorting.
 weight = 1
@@ -68,6 +68,81 @@ contentDir = "content/zh-cn"
 #time_format_default = "02.01.2006"
 #time_format_blog = "02.01.2006"
 
+    [languages.en.params.community]
+    navLabel = "COMMUNITY"
+    weight = 2
+    [[languages.en.params.community.navOptions.items]]
+        name = "News"
+        url = "/en/blog/news/"
+    [[languages.en.params.community.navOptions.items]]
+        name = "Security Notices"
+        url = "/en/overview/notices/"
+    [[languages.en.params.community.navOptions.items]]
+        name = "Contributor's Guide"
+        url = "/zh-cn/contact/"
+#    [[languages.en.params.community.navOptions.items]]
+#        name = "Meet The Team"
+#        url = ""
+
+    # Weight used for sorting.
+    weight = 2
+    [languages.zh-cn.params.community]
+    navLabel = "联系社区"
+    weight = 2
+    [[languages.zh-cn.params.community.navOptions.items]]
+        name = "新闻"
+        url = "/zh-cn/blog/news/"
+    [[languages.zh-cn.params.community.navOptions.items]]
+        name = "安全公告"
+        url = "/zh-cn/overview/notices/"
+    [[languages.zh-cn.params.community.navOptions.items]]
+        name = "贡献者指南"
+        url = "/zh-cn/contact/"
+#    [[languages.zh-cn.params.community.navOptions.items]]
+#        name = "认识团队"
+#        url = ""
+
+
+
+    [languages.en.params.ecosystem]
+    navLabel = "ECOSYSTEM"
+    weight = 2
+    [[languages.en.params.ecosystem.navOptions.items]]
+        name = "Code Generator"
+        url = "https://start.dubbo.apache.org/"
+    [[languages.en.params.ecosystem.navOptions.items]]
+        name = "Visualizable Console"
+        url = "/zh-cn/overview/mannual/control-plane/"
+#    [[languages.en.params.ecosystem.navOptions.items]]
+#        name = "Benchmarking"
+#        url = "http://47.251.95.138:3000/public-dashboards/b75030ae3d0f402ca06b6826de3b590b?orgId=1"
+    [[languages.en.params.ecosystem.navOptions.items]]
+        name = "Proxyless Mesh"
+        url = "/zh-cn/overview/what/core-features/service-mesh/"
+    [[languages.en.params.ecosystem.navOptions.items]]
+        name = "More Demos"
+        url = "https://github.com/apache/dubbo-samples"
+
+
+    [languages.zh-cn.params.ecosystem]
+    navLabel = "生态"
+    weight = 2
+    [[languages.zh-cn.params.ecosystem.navOptions.items]]
+        name = "代码生成"
+        url = "https://start.dubbo.apache.org/"
+    [[languages.zh-cn.params.ecosystem.navOptions.items]]
+        name = "可视化控制台"
+        url = "/zh-cn/overview/mannual/control-plane/"
+#    [[languages.zh-cn.params.ecosystem.navOptions.items]]
+#        name = "商城系统"
+#        url = "http://47.251.95.138:3000/public-dashboards/b75030ae3d0f402ca06b6826de3b590b?orgId=1"
+    [[languages.zh-cn.params.ecosystem.navOptions.items]]
+        name = "无代理网格"
+        url = "/zh-cn/overview/what/core-features/service-mesh/"
+    [[languages.zh-cn.params.ecosystem.navOptions.items]]
+        name = "更多样例"
+        url = "https://github.com/apache/dubbo-samples"
+
 [markup]
 [markup.goldmark]
 [markup.goldmark.renderer]
@@ -97,11 +172,7 @@ algolia_docsearch = true
 offlineSearch = false
 
 
-[[menu.main]]
-    name = "Initializer"
-    weight = 50
-    url = "https://start.dubbo.apache.org/bootstrap.html"
-    post = "<i class='fas fa-external-link-alt'></i>"
+
 #[[menu.main]]
 #    name = "Admin"
 #    weight = 60
@@ -205,6 +276,8 @@ url = "mailto:dev-subscribe@dubbo.apache.org"
 icon = "fa fa-envelope"
 desc = "Discuss development issues around the project"
 
+
+
 [sitemap]
 changefreq = "monthly"
 filename = "sitemap.xml"
diff --git a/content/en/_index.html b/content/en/_index.html
index 292cd6a73b6..11956139966 100644
--- a/content/en/_index.html
+++ b/content/en/_index.html
@@ -4,99 +4,34 @@ linkTitle = "Apache Dubbo Website"
 +++
 
 {{< blocks/cover title="Apache Dubbo" image_anchor="top" height="min" color="secondary" >}}
-<!--<div class="mt-2 mb-3 font-weight-normal">选择编程语言后快速体验!</div>-->
 
-<!--<div class="github-stat-buttons">-->
-<!--    &lt;!&ndash; Place this tag where you want the button to render. &ndash;&gt;-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Java-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo" data-color-scheme="no-preference: dark_high_contrast; light: light_high_contrast; dark: light;"-->
-<!--       data-icon="octicon-star" data-size="large" data-show-count="true" aria-label="Star apache/dubbo on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:120px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Go-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo-go" data-icon="octicon-star"-->
-<!--       data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Rust-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo-rust" data-icon="octicon-star"-->
-<!--       data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--        <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--            Node.js-->
-<!--        </a>-->
-<!--        <a class="github-button" href="https://github.com/apache/dubbo-rust" data-icon="octicon-star"-->
-<!--           data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--</div>-->
-
-<!--<div class="mx-auto">-->
-<!--    <p class="display-4 lead font-weight-light">一款易用的、具备高性能 RPC 通信及服务治理能力的微服务开发框架</p>-->
-<!--</div>-->
-
-<div class="mx-auto mt-3">
-    <div class="mt-2 mb-3 font-weight-normal">Get Started!</div>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal" href='docs3-v2/java-sdk'>
-        Java
-    </a>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal" href='docs3-v2/golang-sdk'>
-        Go
-    </a>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal" href='docs3-v2/rust-sdk'>
-        Rust
-    </a>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal" target="_blank" href='https://github.com/apache/dubbo-js'>
-        Node.js
-    </a>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal"  target="_blank" href='https://github.com/apache/dubbo-python2'>
-        Python
-    </a>
-    <a class="btn btn-lg btn-info rounded mr-3 font-weight-normal" href='docs3-v2'>
-        More...
-    </a>
-
-</div>
 {{< /blocks/cover >}}
 
 {{% blocks/lead color="white" height="min" id="whyDubbo" %}}
 <h1 class="font-weight-normal">Why Dubbo?</h1>
-<!--<p class="font-weight-light">-->
-<!--    Apache Dubbo 首先是一款 rpc 框架,通过可扩展的传输协议(二进制、基于 HTTP/2 的流式通信、HTTP+JSON 等)为微服务组件提供高性能通信,并通过 SDK 为每种语言提供易于使用的微服务配置、API 与编程范式。孵化于阿里巴巴电商应用场景,Dubbo 核心架构充分考虑了超大规模微服务集群实践诉求,历经众多行业标杆企业生产级流量考验,其构建的企业级微服务治理能力如服务发现、流量治理、可观测、认证鉴权、Service Mesh部署方案可以很好的解决企业微服务实践问题。-->
-<!--</p>-->
-<!--<p class="font-weight-light">-->
-<!--    Apache Dubbo 是一款支持多语言的、易用的 web 和 rpc 框架,同时为构建企业级微服务提供服务发现、流量治理、可观测、认证鉴权等能力、工具与最佳实践。-->
-<!--</p>-->
 {{% /blocks/lead %}}
 
 {{< blocks/section id="oceanNodes" >}}
 {{% blocks/feature image="framework" url="./overview/what/advantages/usability/" %}}
-#### [Easy To Use](#), Let Developers Focus On Real Business
+#### [Easy To Use](./overview/what/advantages/usability/), Let Developers Focus On Real Business
 
 Unified microservice development paradigm with multi-language SDK support. Supporting any protocol from HTTP/2, gRPC, REST, Thrift, to TCP.
 {{% /blocks/feature %}}
 
 {{% blocks/feature image="governance" icon="fas fa-share-alt" url="./overview/what/advantages/traffic-management/" %}}
-#### [Service Governance](#), Monitor and Control Cluster In Real-time
+#### [Service Governance](./overview/what/advantages/traffic-management/), Monitor and Control Cluster In Real-time
 
 Built-in traffic management policies such as service discovery, load balancing, and routing. Rich ecosystem with tracing, circuit break, transaction, logging, metrics, service mesh, and visualized console integrations.
 {{% /blocks/feature %}}
 
 {{% blocks/feature image="performance" icon="fa fa-share-alt" title="Mesh Solution" url="./overview/what/advantages/performance/" %}}
-#### [High Performance](#),Designed For Scale
+#### [High Performance](./overview/what/advantages/performance/),Designed For Scale
 
 Making the Alibaba Global Shopping Festival possible by supporting millions of instances and trillions of calls every year, it's designed as low-latency, high-throughput, and high-scalability in the first place.
 {{% /blocks/feature %}}
 
 {{% blocks/feature image="production" icon="fa fa-share-alt" title="production" url="./overview/what/advantages/extensibility/" %}}
-#### [Production Ready](#), Proven Production-stable For Years
+#### [Production Ready](./overview/what/advantages/extensibility/), Proven Production-stable For Years
 
 Dubbo users has achieved full industry coverage: Commercial Bank of China, Ctrip, Haier, Kingdee, Cloud Vendors like Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.
 {{% /blocks/feature %}}
@@ -124,59 +59,3 @@ Dubbo users has achieved full industry coverage: Commercial Bank of China, Ctrip
 {{< /blocks/section >}}
 
 {{< blocks/dubbo-features >}}
-
-<div id="resources" class="community-section">
-    <h2>Follow Us</h2>
-
-    <p class="community-simple">Subscribe to one or more of the following channels to receive project updates, keep connection with community developers.</p>
-
-    <div class="container">
-        <div class="community-resource">
-            <a href="#">
-                <img src="/imgs/contacts/wechat-account.jpg" alt="Wechat">
-            </a>
-            <a href="#">Wechat Channel</a>
-            <p>Apache Dubbo</p>
-        </div>
-        <div id="slack" class="community-resource">
-            <a href="#">
-                <img src="/imgs/contacts/dingtalk.png" alt="Dingtalk">
-            </a>
-            <a href="#">DingTalk Channel</a>
-            <p>Online community meetings or Bi-weekly!</p>
-        </div>
-        <div id="twitter" class="community-resource">
-            <a href="https://twitter.com/apachedubbo">
-                <img src="/imgs/contacts/twitter.png" alt="Twitter">
-            </a>
-            <a href="https://twitter.com/apachedubbo">Twitter&nbsp;&#9654;</a>
-            <p><em>#apachedubbo</em></p>
-            <p>Real-time announcements of blog posts, events, news, ideas.</p>
-        </div>
-
-        <div id="github" class="community-resource">
-            <a href="https://github.com/apache/dubbo-awesome">
-                <img src="/imgs/contacts/github.png" alt="GitHub">
-            </a>
-            <a href="https://github.com/apache/dubbo-awesome">GitHub&nbsp;&#9654;</a>
-            <p>All the project and issue tracking, plus of course code.</p>
-        </div>
-    </div>
-</div>
-
-<!--{{< blocks/contact-us >}}-->
-
-
-<!--{{< blocks/section color="primary" >}}-->
-<!--{{% blocks/feature icon="far fa-envelope" title="订阅邮件组" %}}-->
-<!--dev@dubbo.apache.org 参与社区的讨论-->
-<!--{{% /blocks/feature %}}-->
-
-<!--{{% blocks/feature icon="fab fa-github" title="欢迎参与贡献!" url="https://github.com/apache/dubbo#contributing" %}}-->
-<!--我们通过 [Pull Request](https://github.com/apache/dubbo/pulls) 在 **GitHub** 上协作。我们期待您的加入!-->
-<!--{{% /blocks/feature %}}-->
-
-<!--{{% blocks/feature icon="fas fa-bullhorn" title="请关注我们的技术博客!" url="/zh/blog" %}}-->
-<!--我们会在第一时间分享 Dubbo 新发布的特性和使用心得-->
-<!--{{% /blocks/feature %}}-->
-<!--{{< /blocks/section >}}-->
diff --git a/content/en/blog/_index.md b/content/en/blog/_index.md
index 6da132d2497..e46032b196e 100644
--- a/content/en/blog/_index.md
+++ b/content/en/blog/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "Apache Dubbo Blog"
-linkTitle: "Blog"
+linkTitle: "BLOG"
 menu:
   main:
     weight: 30
diff --git a/content/en/docs3-v2/_index.md b/content/en/docs3-v2/_index.md
index d96137280d9..11f11b8ffcf 100755
--- a/content/en/docs3-v2/_index.md
+++ b/content/en/docs3-v2/_index.md
@@ -3,7 +3,7 @@ type: docs
 title: "SDK Manual"
 linkTitle: "SDK Manual"
 hide_summary: true
-menu:
-  main:
-    weight: 21
+# menu:
+#   main:
+#     weight: 21
 ---
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/observability/kubernetes-probes.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/observability/kubernetes-probes.md
index 0018d215cda..9a677e95711 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/observability/kubernetes-probes.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/observability/kubernetes-probes.md
@@ -5,4 +5,4 @@ linkTitle: "Kubernetes Probes"
 weight: 5
 no_list: true
 hide_summary: true
----
\ No newline at end of file
+---
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/dubbo-kubernetes-probe.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/dubbo-kubernetes-probe.md
index 9b612bb8a0a..838ec3ec36c 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/dubbo-kubernetes-probe.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/dubbo-kubernetes-probe.md
@@ -31,18 +31,18 @@ For an introduction to more extensions of Dubbo3 SPI, see [Dubbo SPI Extensions]
 
 For the livenessProbe liveness detection, since the Dubbo3 framework itself cannot obtain the liveness status of the application, this interface has no default implementation and returns success by default. Developers can expand this SPI interface according to the SPI definition, and judge whether it is alive or not from the application level.
 
-About [liveness liveness probe](../../../reference-manual/spi/description/liveness/) extension example
+About [liveness liveness probe](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/liveness/) extension example
 ### Readiness check
 
 For the readinessProbe readiness detection, Dubbo3 currently provides two detection dimensions by default. One is to judge whether the Dubbo3 service itself is started or stopped, and the other is to check whether all services have registered interfaces. If all services have been offline from the registration center (you can Operate via QOS Operations) will return Not Ready.
 
-About the [readiness readiness probe](../../../reference-manual/spi/description/readiness/) extended example
+About the [readiness readiness probe](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/readiness/) extended example
 
 ### Start detection
 
 For startupProbe startup detection, Dubbo3 currently provides a detection dimension by default, which is to return to the ready state after all startup processes (interface exposure, registration center writing, etc.) are completed.
 
-About the [startup startup probe](../../../reference-manual/spi/description/startup/) extended example
+About the [startup startup probe](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/startup/) extended example
 
 ### Reference example
 ```yaml
@@ -67,4 +67,4 @@ startupProbe:
 ```
 > QOS When the computing node detects memory pressure, kuberentes will BestEffort -> Burstable -> Guaranteed to evict Pods in sequence.
 
-At present, all three probes have corresponding interfaces, and the path is the command in QOS. Please modify the port information according to the QOS configuration (the default port is 22222). For other parameters, please refer to [Kubernetes official documentation](https://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).
\ No newline at end of file
+At present, all three probes have corresponding interfaces, and the path is the command in QOS. Please modify the port information according to the QOS configuration (the default port is 22222). For other parameters, please refer to [Kubernetes official documentation](https://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-howto.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-howto.md
index 95c901a009d..ffb035af7b7 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-howto.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-howto.md
@@ -10,7 +10,7 @@ weight: 7
 
 ## Feature Description
 
-Prior to dubbo 3.3.0-beta.3, dubbo and dubbo-samples were using a mix of log4j and logback, leading to frequent conflicts and errors due to some modules lacking log configuration. Therefore, after 3.3.0-beta.3, the logging components have been upgraded to log4j2 for simplicity and reduced maintenance costs. This document explains how to configure and use the logging framework to avoid conflicts caused by indirectly introducing multiple logging frameworks.
+Prior to dubbo 3.3.0, dubbo and dubbo-samples were using a mix of log4j and logback, leading to frequent conflicts and errors due to some modules lacking log configuration. Therefore, after 3.3.0-beta.3, the logging components have been upgraded to log4j2 for simplicity and reduced maintenance costs. This document explains how to configure and use the logging framework to avoid conflicts caused by indirectly introducing multiple logging frameworks.
 
 ## How To Use
 
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-management.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-management.md
index 3e664f9a3ba..cbceac3e78d 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-management.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/logger-management.md
@@ -35,7 +35,7 @@ dubbo.application.logger=log4j
 <dubbo:application logger="log4j" />
 ```
 
-For custom extensions, please refer to [Log Adapter Extension](../../../reference-manual/spi/description/logger-adapter)
+For custom extensions, please refer to [Log Adapter Extension](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/logger-adapter)
 
 ## Logging framework runtime management
 ### 1. Query log configuration
@@ -117,4 +117,4 @@ dubbo>switchLogger slf4j
 OK
 dubbo>loggerInfo
 Available logger adapters: [jcl, slf4j, log4j, jdk]. Current Adapter: [slf4j]. Log level: INFO
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/service-container.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/service-container.md
index 724749dae7a..a2df989b7ba 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/service-container.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/others/service-container.md
@@ -11,7 +11,7 @@ The service container of Dubbo 3 is a standalone startup program, because the ba
 
 The Dubbo3 service container is just a simple Main method and loads a simple Spring container for exposing services.
 
-The loading content of the service container can be extended, and spring, jetty, log4j, etc. are built-in, and can be extended through [container extension point](../../../reference-manual/spi/description/container). The configuration is configured in the -D parameter of the java command or `dubbo.properties`.
+The loading content of the service container can be extended, and spring, jetty, log4j, etc. are built-in, and can be extended through [container extension point](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/container). The configuration is configured in the -D parameter of the java command or `dubbo.properties`.
 
 ## scenes to be used
 The web container is mainly used to respond to http requests and static pages. The Dubbo service provider only provides dubbo services externally. It is not suitable to use the web container. As a dubbo service provider alone, it only needs to load a simple spring container through a main method Expose the service.
@@ -57,4 +57,4 @@ java org.apache.dubbo.container.Main -Ddubbo.container=spring,jetty,log4j
 Pass in the container to be loaded through `dubbo.properties` configuration under the classpath
 ```fallback
 dubbo.container=spring,jetty,log4j
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/loadbalance.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/loadbalance.md
index e56624afc64..349b3828b05 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/loadbalance.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/loadbalance.md
@@ -10,7 +10,7 @@ When cluster load balancing, Dubbo provides a variety of balancing strategies, t
 
 In terms of specific implementation, Dubbo provides client load balancing, that is, the Consumer uses the load balancing algorithm to determine which Provider instance to submit the request to.
 
-You can expand the load balancing strategy by yourself, see: [Load Balance Extension](../../../reference-manual/spi/description/load-balance)
+You can expand the load balancing strategy by yourself, see: [Load Balance Extension](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/load-balance)
 
 ## load balancing strategy
 Currently Dubbo has the following built-in load balancing algorithms, which users can directly configure and use:
@@ -102,4 +102,4 @@ Response time here = the average response time of a provider within the window t
 <dubbo:reference interface="...">
     <dubbo:method name="..." loadbalance="roundrobin"/>
 </dubbo:reference>
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/profiler.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/profiler.md
index f61faea1a52..1f39dfb489b 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/profiler.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/profiler.md
@@ -20,7 +20,7 @@ Scenarios that need to collect and analyze the precise time consumption of Dubbo
 
 ## How to use
 
-`simple profiler` is automatically enabled by default, and for requests whose processing time exceeds 3/4 of the timeout time, the slow call information will be printed out through the log. If you need to enable the `detail profiler` mode or modify the timeout alarm ratio, you can refer to the [performance sampling command](../../../reference-manual/qos/profiler/) document.
+`simple profiler` is automatically enabled by default, and for requests whose processing time exceeds 3/4 of the timeout time, the slow call information will be printed out through the log. If you need to enable the `detail profiler` mode or modify the timeout alarm ratio, you can refer to the [performance sampling command](/zh-cn/overview/mannual/java-sdk/reference-manual/qos/profiler/) document.
 
 ### output example
 
@@ -186,4 +186,4 @@ Start time: 285965612316294
                                 +-[ Offset: 1.558545ms; Usage: 804.276436ms, 99% ] Receive request. Server biz impl invoke begin., dubbo version: 3.0.10-SNAPSHOT, current host: xx.xx.xx.xx
 ```
 
-Note: If the log is empty due to the mismatch of the log framework, you can refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) to dynamically modify the log output framework.
\ No newline at end of file
+Note: If the log is empty due to the mismatch of the log framework, you can refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) to dynamically modify the log output framework.
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/result-cache.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/result-cache.md
index 208b13ef264..068bcbc34bf 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/result-cache.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/result-cache.md
@@ -13,7 +13,7 @@ description: "Speed up access by caching results"
 * `threadlocal` The current thread cache, such as a page rendering, uses many portals, and each portal needs to check user information. Through thread caching, this redundant access can be reduced.
 * `jcache` integrates with [JSR107](http://jcp.org/en/jsr/detail?id=107%27) to bridge various cache implementations.
 
-Cache Type Extensible [Cache Extensions](../../../reference-manual/spi/description/cache)
+Cache Type Extensible [Cache Extensions](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/cache)
 
 About [sample code](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-cache)
 
@@ -33,4 +33,4 @@ or:
 <dubbo:reference interface="com.foo.BarService">
     <dubbo:method name="findBar" cache="lru" />
 </dubbo:reference>
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/router-snapshot.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/router-snapshot.md
index f82f1b76a39..9d294101c72 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/router-snapshot.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/router-snapshot.md
@@ -17,7 +17,7 @@ Many of Dubbo's traffic management capabilities are implemented based on Router.
 When Dubbo receives the address change, it will push the address information to all `Routers`, and these `Routers` can calculate the routing packets in advance at this stage and cache them to avoid the need to traverse all provider calculations when calling grouping parameters.
 The `StateRouter` introduced in Dubbo 3 provides the ability to obtain the status of each route in real time through the qos command tool.
 
-The operation and maintenance personnel can obtain the status of the route through the `getRouterSnapshot` command. For specific commands, please refer to the [getRouterSnapshot command](../../../reference-manual/qos/router-snapshot/#getroutersnapshot-command) document.
+The operation and maintenance personnel can obtain the status of the route through the `getRouterSnapshot` command. For specific commands, please refer to the [getRouterSnapshot command](/zh-cn/overview/mannual/java-sdk/reference-manual/qos/router-snapshot/#getroutersnapshot-command) document.
 
 **Note: This feature only supports `StateRoute`, and `StateRouter` needs to implement the `doBuildSnapshot` interface based on `AbstractStateRouter`. **
 
@@ -76,4 +76,4 @@ dubbo>
 ```
 
 #### Notice:
-If the log is empty due to the mismatch of the log framework, you can refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) to dynamically modify the log output framework.
\ No newline at end of file
+If the log is empty due to the mismatch of the log framework, you can refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) to dynamically modify the log output framework.
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/context.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/context.md
index 87271baf416..b84121f0ace 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/context.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/context.md
@@ -6,7 +6,7 @@ weight: 6
 description: "Store the environment information required in the current calling process through the context"
 ---
 ## Feature description
-The context stores the environment information needed in the current calling process. All configuration information will be converted to URL parameters, see the **corresponding URL parameters** column in [schema configuration reference manual](../../../reference-manual/config/properties/).
+The context stores the environment information needed in the current calling process. All configuration information will be converted to URL parameters, see the **corresponding URL parameters** column in [schema configuration reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties//).
 
 RpcContext is a temporary state recorder for ThreadLocal. When RPC requests are received or RPC requests are initiated, the state of RpcContext will change. For example: A tunes B, B then tunes C, then on machine B, before B tunes C, RpcContext records the information of A's tune to B, after B tunes C, RpcContext records the information of B's tune to C.
 
@@ -46,4 +46,4 @@ public class XxxServiceImpl implements XxxService {
         boolean isProviderSide = RpcContext.getServiceContext().isProviderSide();
     }
 }
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/fault-tolerent-strategy.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/fault-tolerent-strategy.md
index 05bd79f3ba8..e8169c44d40 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/fault-tolerent-strategy.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/fault-tolerent-strategy.md
@@ -20,7 +20,7 @@ Each node relationship:
 
 ## Cluster fault tolerance mode
 
-You can expand the cluster fault-tolerant strategy by yourself, see: [Cluster Expansion](../../../reference-manual/spi/description/cluster/)
+You can expand the cluster fault-tolerant strategy by yourself, see: [Cluster Expansion](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/cluster/)
 
 ### Failover Cluster
 
@@ -134,4 +134,4 @@ or
 
 ```xml
 <dubbo:reference cluster="failsafe" />
-```
\ No newline at end of file
+```
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/group-merger.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/group-merger.md
index 3c9772ace08..968b01a6c3c 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/group-merger.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/group-merger.md
@@ -48,7 +48,7 @@ One method does not combine results, others combine results
 ```
 ### Specify merge strategy
 
-Specify the merge strategy, the default is to automatically match according to the return value type, if there are two combiners of the same type, you need to specify the name of the combiner [Merge result extension](../../../reference-manual/spi/ description/merger)
+Specify the merge strategy, the default is to automatically match according to the return value type, if there are two combiners of the same type, you need to specify the name of the combiner [Merge result extension](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/ description/merger)
 
 ```xml
 <dubbo:reference interface="com.xxx.MenuService" group="*">
@@ -66,4 +66,4 @@ Specify the merge method to merge the specified method that returns the result o
 ```
 
 #### hint:
-Supported since `2.1.0` version
\ No newline at end of file
+Supported since `2.1.0` version
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/multi-registry.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/multi-registry.md
index f5464bf998d..7f3d0ec1583 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/multi-registry.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/multi-registry.md
@@ -84,4 +84,4 @@ If only the test environment temporarily needs to connect to two different regis
 </beans>
 ```
 
-[^1]: You can extend the registry by yourself, see: [Registry Extension](../../../reference-manual/spi/description/registry)
\ No newline at end of file
+[^1]: You can extend the registry by yourself, see: [Registry Extension](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/registry)
diff --git a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/parameter-validation.md b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/parameter-validation.md
index 04dfb241480..b32956df1aa 100644
--- a/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/parameter-validation.md
+++ b/content/en/docs3-v2/java-sdk/advanced-features-and-usage/service/parameter-validation.md
@@ -193,4 +193,4 @@ public class ValidationConsumer {
 }
 ```
 
-> **The validation method can be extended, see [Validation Extension](../../../reference-manual/spi/description/validation) in the developer manual for the extension method**
\ No newline at end of file
+> **The validation method can be extended, see [Validation Extension](/zh-cn/overview/mannual/java-sdk/reference-manual/spi/description/validation) in the developer manual for the extension method**
diff --git a/content/en/docs3-v2/java-sdk/faq/0/1.md b/content/en/docs3-v2/java-sdk/faq/0/1.md
index c2d3a7982be..c6726dcefb9 100644
--- a/content/en/docs3-v2/java-sdk/faq/0/1.md
+++ b/content/en/docs3-v2/java-sdk/faq/0/1.md
@@ -19,4 +19,4 @@ By default, the number of business threads on the Dubbo server is 200. If the nu
 
 
 > The FAQ page of this error code refers to ["Dubbo Common Errors and Solutions"](https://github.com/StabilityMan/StabilityGuide/blob/master/docs/diagnosis/plugin/rpc/%E7%B3%BB%E7%BB%9F%E7%A8%B3%E5%AE%9A%E6%80%A7%E2%80%94%E2%80%94Dubbo%E5%B8%B8%E8%A7%81%E9%94%99%E8%AF%AF%E5%8F%8A%E8%A7%A3%E5%86%B3%E6%96%B9%E6%B3%95.md).
-Articles cited are compiled under license [CC-BY-4.0](http://creativecommons.org/licenses/by/4.0/). Thanks to the original author here.
\ No newline at end of file
+Articles cited are compiled under license [CC-BY-4.0](http://creativecommons.org/licenses/by/4.0/). Thanks to the original author here.
diff --git a/content/en/docs3-v2/java-sdk/faq/0/13.md b/content/en/docs3-v2/java-sdk/faq/0/13.md
index 27d0ebd2b3b..80f394792cd 100644
--- a/content/en/docs3-v2/java-sdk/faq/0/13.md
+++ b/content/en/docs3-v2/java-sdk/faq/0/13.md
@@ -12,6 +12,6 @@ An error occurred during the push process of the indicator data, the pushed serv
 
 ### Troubleshooting and resolution steps
 
-Please refer to the configuration item reference manual[configuration item reference manual](/en/docs3-v2/java-sdk/reference-manual/config/properties/#metrics).
+Please refer to the configuration item reference manual[configuration item reference manual](/en/docs3-v2/java-sdk/reference-manual/config/properties/).
 
-<p style="margin-top: 3rem;"> </p>
\ No newline at end of file
+<p style="margin-top: 3rem;"> </p>
diff --git a/content/en/docs3-v2/java-sdk/faq/0/2.md b/content/en/docs3-v2/java-sdk/faq/0/2.md
index db74f760a3c..90b7d0fc07d 100644
--- a/content/en/docs3-v2/java-sdk/faq/0/2.md
+++ b/content/en/docs3-v2/java-sdk/faq/0/2.md
@@ -9,6 +9,6 @@ weight: 2
 This hint means that the value configured by the user does not match the data type required by the attribute itself. For example, the `dubbo.comsumer.threads` attribute can only accept numeric attributes, but the value entered by the user is mixed with letters.
 
 ### Troubleshooting and resolution steps
-According to the [Configuration Item Reference Manual](../../../reference-manual/config/properties), find the wrong configuration item, check the type specified by the item, and check whether there is a type inconsistency.
+According to the [Configuration Item Reference Manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/), find the wrong configuration item, check the type specified by the item, and check whether there is a type inconsistency.
 
-<p style="margin-top: 3rem;"> </p>
\ No newline at end of file
+<p style="margin-top: 3rem;"> </p>
diff --git a/content/en/docs3-v2/java-sdk/faq/1/12.md b/content/en/docs3-v2/java-sdk/faq/1/12.md
index c2b85890099..793be177881 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/12.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/12.md
@@ -12,4 +12,4 @@ During the process of destroying the `unexport` of `Registryprotocol`, the `getR
 
 ### Troubleshooting and resolution steps
 > see also
-[Configuration item reference manual](../../../reference-manual/config/properties)
\ No newline at end of file
+[Configuration item reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
diff --git a/content/en/docs3-v2/java-sdk/faq/1/14.md b/content/en/docs3-v2/java-sdk/faq/1/14.md
index 5188e6e4d44..7bbb3b7af60 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/14.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/14.md
@@ -12,4 +12,4 @@ Please check whether the content or format of the dynamic configuration file is
 
 
 ### See also
-> [Configuration Reference Manual](../../../reference-manual/config/properties)
\ No newline at end of file
+> [Configuration Reference Manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
diff --git a/content/en/docs3-v2/java-sdk/faq/1/17.md b/content/en/docs3-v2/java-sdk/faq/1/17.md
index e89c456f07d..e625f0cfc87 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/17.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/17.md
@@ -13,6 +13,6 @@ It may be that there is a problem with the parameter configuration of metadata,
 2. Check whether the `metadataServicePort` port number conflicts. If the ports configured by Provider and Consumer are in conflict at the same time, a 1-17 error will be generated.
 
 ## see also
-[Configuration item reference manual](../../../reference-manual/config/properties)
+[Configuration item reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
 
-<p style="margin-top: 3rem;"> </p>
\ No newline at end of file
+<p style="margin-top: 3rem;"> </p>
diff --git a/content/en/docs3-v2/java-sdk/faq/1/18.md b/content/en/docs3-v2/java-sdk/faq/1/18.md
index ad70f24f74c..b81501e9248 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/18.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/18.md
@@ -13,6 +13,6 @@ It may be that `metadataType` is in local mode, and `metadataServicePort` is con
 2. Check whether the configuration of `metadataServicePort` on the Provider side is correct, and pay special attention to whether there is any conflict with other application ports.
 
 ## see also
-[Configuration item reference manual](../../../reference-manual/config/properties)
+[Configuration item reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
 
-<p style="margin-top: 3rem;"> </p>
\ No newline at end of file
+<p style="margin-top: 3rem;"> </p>
diff --git a/content/en/docs3-v2/java-sdk/faq/1/3.md b/content/en/docs3-v2/java-sdk/faq/1/3.md
index 9f5491e2177..bd71505ee1f 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/3.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/3.md
@@ -10,4 +10,4 @@ When `FrameworkExecutorRepository` is destroyed, calling `CacheableFailbackRegis
 
 ### Troubleshooting and resolution steps
 
-> See also the [Configuration Items Reference Manual](../../../reference-manual/config/properties)
\ No newline at end of file
+> See also the [Configuration Items Reference Manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
diff --git a/content/en/docs3-v2/java-sdk/faq/1/4.md b/content/en/docs3-v2/java-sdk/faq/1/4.md
index e2f200cc84a..2288b3210e3 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/4.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/4.md
@@ -15,4 +15,4 @@ weight: 4
 3. Check whether `enable-empty-protection` of the registration center is true (the default is true).
 
 > see also
-[Configuration item reference manual](../../../reference-manual/config/properties)
\ No newline at end of file
+[Configuration item reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
diff --git a/content/en/docs3-v2/java-sdk/faq/1/8.md b/content/en/docs3-v2/java-sdk/faq/1/8.md
index 20f1150bc3a..98b866944ff 100644
--- a/content/en/docs3-v2/java-sdk/faq/1/8.md
+++ b/content/en/docs3-v2/java-sdk/faq/1/8.md
@@ -15,4 +15,4 @@ weight: 8
 3. Check whether the provider’s registry-related parameters such as `registry` `config-center` `metadata-report` are configured correctly.
 
 > see also
-[Configuration item reference manual](../../../reference-manual/config/properties)
\ No newline at end of file
+[Configuration item reference manual](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/)
diff --git a/content/en/docs3-v2/java-sdk/reference-manual/protocol/http.md b/content/en/docs3-v2/java-sdk/reference-manual/protocol/http.md
index 53433653774..bb943f4e0e3 100644
--- a/content/en/docs3-v2/java-sdk/reference-manual/protocol/http.md
+++ b/content/en/docs3-v2/java-sdk/reference-manual/protocol/http.md
@@ -6,6 +6,11 @@ weight: 6
 ---
 
 
+{{% alert title="Note" color="warning" %}}
+Since Dubbo 3.3, the rest protocol has been moved to the extensions library, with the triple protocol now providing more comprehensive support for Rest. For details refer to [Triple Rest User Manual](../../tripe-rest-manual/).  
+If you wish to continue using the original rest protocol, please include the corresponding [dubbo-spi-extensions](https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-rpc-extensions/dubbo-rpc-rest) dependency.
+{{% /alert %}}
+
 ## Feature description
 HTTP form-based remote invocation protocol, implemented by Spring's HttpInvoker, supported by versions above `2.3.0`.
 
diff --git a/content/en/docs3-v2/java-sdk/reference-manual/protocol/rest.md b/content/en/docs3-v2/java-sdk/reference-manual/protocol/rest.md
index e20537a33ba..d9acddd826a 100644
--- a/content/en/docs3-v2/java-sdk/reference-manual/protocol/rest.md
+++ b/content/en/docs3-v2/java-sdk/reference-manual/protocol/rest.md
@@ -5,6 +5,11 @@ linkTitle: "Rest protocol"
 weight: 4
 ---
 
+{{% alert title="Note" color="warning" %}}
+Since Dubbo 3.3, the rest protocol has been moved to the extensions library, with the triple protocol now providing more comprehensive support for Rest. For details refer to [Triple Rest User Manual](../../tripe-rest-manual/).  
+If you wish to continue using the original rest protocol, please include the corresponding [dubbo-spi-extensions](https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-rpc-extensions/dubbo-rpc-rest) dependency.
+{{% /alert %}}
+
 Support for REST calls based on the standard Java REST API - JAX-RS 2.0 (short for Java API for RESTful Web Services)
 
 ### Quick Start
diff --git a/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-3.3.md b/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-3.3.md
new file mode 100644
index 00000000000..d87aa6e3de6
--- /dev/null
+++ b/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-3.3.md
@@ -0,0 +1,282 @@
+---
+type: docs
+title: "Tripe 3.3 New Features"
+linkTitle: "Tripe 3.3 New Features"
+weight: 13
+---
+
+<a name="lipv5"></a>
+
+## New Rest Support
+
+### Rest Features
+
+Since Dubbo 3.3, the Triple protocol reuses the existing HTTP stack to fully support RESTful service exports. Without the need for generic or gateway protocol conversion, users can
+directly access backend Triple protocol services via HTTP in a decentralized manner. Additionally, it offers extensive annotation and SPI extension support for advanced REST usage,
+such as path customization, output format customization, and exception handling. Key features include:
+
+- **Triple Protocol Integration**  
+  Reuses the existing Triple HTTP stack, allowing support for HTTP/1, HTTP/2, and HTTP/3 without additional configuration or new ports.
+- **Decentralization**  
+  Exposes Rest APIs directly, eliminating dependency on gateway applications for traffic forwarding, thus improving performance and reducing stability risks caused by gateways.
+  Security concerns can be addressed through internal application extensions, a practice verified in Taobao’s MTOP.
+- **Support for Existing Servlet Infrastructure**  
+  Supports Servlet API and Filter, allowing users to reuse existing security components based on the Servlet API. Integrating OAuth and Spring Security is as simple as implementing
+  a Servlet Filter.
+- **Multiple Dialects**  
+  Considering that most users are accustomed to using SpringMVC or JAX-RS for REST API development, Triple Rest allows continued use of these methods for service definitions and
+  supports most extensions and exception handling mechanisms (with over 80% of the original framework’s functionality). For lightweight users, the Basic dialect is available, and
+  Triple’s out-of-the-box REST capabilities are based on this dialect.
+- **High Extensibility**  
+  Offers more than 20 extension points, enabling users to easily create custom dialects and flexibly customize parameter retrieval, type conversion, error handling, and other
+  logic.
+- **Out-of-the-Box**  
+  REST capabilities are available out of the box; simply enable the Triple protocol to have direct REST access to services.
+- **High-Performance Routing**  
+  The routing component uses an
+  optimized [Radix Tree](https://github.com/apache/dubbo/blob/3.3/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/mapping/RadixTree.java) and Zero
+  Copy technology to improve routing performance.
+- **Seamless OpenAPI Integration (TBD)**  
+  Upcoming OpenAPI integration will allow for out-of-the-box OpenAPI Schema export. With the Swagger dependency, a Web UI can be used for service testing. Using the OpenAPI Schema,
+  API tools like [Postman](https://www.postman.com/) and [Apifox](https://apifox.com/) can manage and test APIs, and the OpenAPI ecosystem can facilitate cross-language calls.
+  Future enhancements will support a Schema First approach, allowing frontend teams to define OpenAPI collaboratively, generate call code and mocks based on OpenAPI, and enable
+  backend development using stubs generated from OpenAPI, greatly improving collaboration efficiency.
+
+<a name="DBA0D"></a>
+
+### Example
+
+<a name="tiFyi"></a>
+
+###### Sample Code
+
+```java
+package org.apache.dubbo.rest.demo;
+
+import org.apache.dubbo.remoting.http12.rest.Mapping;
+import org.apache.dubbo.remoting.http12.rest.Param;
+
+// Service Interface
+public interface DemoService {
+    String hello(String name);
+
+    @Mapping(path = "/hi", method = HttpMethods.POST)
+    String hello(User user, @Param(value = "c", type = ParamType.Header) int count);
+}
+
+// Service Implementation
+@DubboService
+public class DemoServiceImpl implements DemoService {
+    @Override
+    public String hello(String name) {
+        return "Hello " + name;
+    }
+
+    @Override
+    public String hello(User user, int count) {
+        return "Hello " + user.getTitle() + ". " + user.getName() + ", " + count;
+    }
+}
+
+// Model
+@Data
+public class User {
+    private String title;
+    private String name;
+}
+```
+
+<a name="kZqN8"></a>
+
+###### Download and Run Example
+
+```bash
+# Get the example code
+git clone --depth=1 https://github.com/apache/dubbo-samples.git
+cd dubbo-samples/2-advanced/dubbo-samples-triple-rest/dubbo-samples-triple-rest-basic
+# Run
+mvn spring-boot:run
+```
+
+<a name="udlJN"></a>
+
+###### Curl Test
+
+```bash
+curl -v "http://127.0.0.1:8081/org.apache.dubbo.rest.demo.DemoService/hello?name=world"
+# Output
+#> GET /org.apache.dubbo.rest.demo.DemoService/hello?name=world HTTP/1.1
+#>
+#< HTTP/1.1 200 OK
+#< content-type: application/json
+#< content-length: 13
+#<
+#"Hello world"
+#
+# Explanation
+# The output shows "Hello world", with quotes because the default content-type is application/json.
+# This example shows that Triple exports services to the /{serviceInterface}/{methodName} path by default, supporting parameter passing via URL.
+
+curl -v -H "c: 3" -d 'name=Yang' "http://127.0.0.1:8081/org.apache.dubbo.rest.demo.DemoService/hi.txt?title=Mr"
+# Output
+#> POST /org.apache.dubbo.rest.demo.DemoService/hi.txt?title=Mr HTTP/1.1
+#> c: 3
+#> Content-Length: 9
+#> Content-Type: application/x-www-form-urlencoded
+#>
+#< HTTP/1.1 200 OK
+#< content-type: text/plain
+#< content-length: 17
+#<
+#Hello Mr. Yang, 3
+#
+# Explanation
+# The output shows "Hello Mr. Yang, 3", without quotes because the output was specified as text/plain by using the txt suffix.
+# This example shows how to customize paths using the Mapping annotation and customize parameter sources using the Param annotation, supporting parameter passing via post body or URL.
+```
+
+<a name="apMqg"></a>
+
+### Documentation
+
+Please visit the user manual: [Triple Rest Manual](../triple-rest-manual/)
+<a name="pMgxF"></a>
+
+## Support for Servlet Integration
+
+In version 3.3, you can reuse existing Spring Boot servlet listening ports to handle HTTP traffic, eliminating the need for Netty to listen on new ports. This simplifies deployment
+and reduces maintenance costs. By reducing reliance on external ports, it helps to easily pass through enterprise firewalls and gateways, simplifying network deployment and
+enhancing the maintainability and security of enterprise applications.
+<a name="n9HZO"></a>
+
+### Example
+
+<a name="qP23R"></a>
+
+###### Download and Run Example
+
+```bash
+# Get the sample code
+git clone --depth=1 https://github.com/apache/dubbo-samples.git
+cd dubbo-samples/2-advanced/dubbo-samples-triple-servlet
+# Run directly
+mvn spring-boot:run
+```
+
+<a name="RuppW"></a>
+
+###### Curl Test
+
+```shell
+curl --http2-prior-knowledge -v 'http://localhost:50052/org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world'
+# Output
+#* [HTTP/2] [1] OPENED stream for http://localhost:50052/org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world
+#* [HTTP/2] [1] [:method: GET]
+#* [HTTP/2] [1] [:scheme: http]
+#* [HTTP/2] [1] [:authority: localhost:50052]
+#* [HTTP/2] [1] [:path: /org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world]
+#>
+#* Request completely sent off
+#< HTTP/2 200
+#< content-type: application/json
+#< date: Sun, 25 Aug 2024 03:38:12 GMT
+#<
+#"Hello world"
+```
+
+<a name="mC3d4"></a>
+
+### Documentation
+
+Please
+visit: [how-to-enable-servlet-support-for-triple](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-servlet#how-to-enable-servlet-support-for-triple)
+to learn how to configure and enable servlet support.
+<a name="uvvts"></a>
+
+## Support for HTTP/3 Protocol
+
+<a name="anV9K"></a>
+
+### HTTP/3 Features
+
+In version 3.3, Triple implements support for the HTTP/3 protocol, allowing RPC and REST requests to be transmitted via HTTP/3. Using HTTP/3 offers the following benefits:
+
+- **Enhanced Performance**  
+  With HTTP/3 support, the use of the QUIC protocol reduces latency and accelerates request-response times. This significantly boosts overall service
+  performance, especially in high-latency or complex network environments.
+- **Improved Reliability**  
+  HTTP/3 leverages multiplexing and connection migration to avoid head-of-line blocking, maintaining stable connections even under poor network conditions
+  and ensuring reliable service delivery.
+- **Increased Security**  
+  HTTP/3 enforces TLS 1.3 encryption, providing a more secure communication channel compared to the optional encryption in traditional HTTP/2.
+- **Better Adaptation to Weak Networks**  
+  In scenarios with high packet loss or unstable bandwidth, HTTP/3 maintains high connection quality and service performance, improving
+  outcomes in weak network environments.
+
+Since HTTP/3 is based on the QUIC protocol (UDP), it might be blocked by firewalls or gateways. To mitigate this, Triple has implemented HTTP/3 negotiation capabilities and enabled
+it by default. Connections are initially established via HTTP/2, and if the server responds with an [Alt-Svc](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Alt-Svc)
+header indicating HTTP/3 support, the client will automatically switch to HTTP/3.
+<a name="TqXgf"></a>
+
+### Example
+
+<a name="oSP0r"></a>
+
+###### Download and Run Example
+
+```bash
+# Get the sample code
+git clone --depth=1 https://github.com/apache/dubbo-samples.git
+cd dubbo-samples/2-advanced/dubbo-samples-triple-http3
+# Run directly
+mvn spring-boot:run
+```
+
+<a name="fb4sX"></a>
+
+###### Testing with Curl
+
+Note that Curl must be upgraded to a version that supports HTTP/3. Refer to: [https://curl.se/docs/http3.html](https://curl.se/docs/http3.html).
+
+```shell
+
+curl --http3 -vk 'https://localhost:50052/org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world'
+# Output
+#* QUIC cipher selection: TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_CCM_SHA256
+#* Skipped certificate verification
+#* using HTTP/3
+#* [HTTP/3] [0] OPENED stream for https://localhost:50052/org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world
+#* [HTTP/3] [0] [:method: GET]
+#* [HTTP/3] [0] [:scheme: https]
+#* [HTTP/3] [0] [:authority: localhost:50052]
+#* [HTTP/3] [0] [:path: /org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world]
+#>
+#* Request completely sent off
+#< HTTP/3 200
+#< content-type: application/json
+#<
+#"Hello world"
+```
+
+<a name="A7a3w"></a>
+
+### Performance Comparison
+
+#### Impact of Packet Loss on QPS
+
+![http3-qps.jpg](/imgs/v3/manual/java/protocol/http3-qps.jpg)
+
+#### Impact of Packet Loss on RT
+
+![http3-rt.jpg](/imgs/v3/manual/java/protocol/http3-rt.jpg)
+
+<a name="NIoKX"></a>
+
+### Architecture Diagram
+
+![http3-arch.jpg](/imgs/v3/manual/java/protocol/http3-arch.jpg)
+
+### Documentation
+
+For information on how to configure and enable HTTP/3 support, please
+visit: [how-to-enable-http3-support-for-triple](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-http3#how-to-enable-http3-support-for-triple).
diff --git a/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-rest-manual.md b/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-rest-manual.md
new file mode 100644
index 00000000000..d7fd5125944
--- /dev/null
+++ b/content/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-rest-manual.md
@@ -0,0 +1,984 @@
+---
+linkTitle: Triple Rest User Manual
+title: Triple Rest User Manual
+type: docs
+weight: 14
+---
+
+{{% alert title="Note" color="warning" %}}
+Since Dubbo 3.3, the original Rest protocol has been moved to the Extensions library, and the Triple protocol now provides more comprehensive support for Rest. To continue using
+the original Rest protocol, you can add the corresponding [dubbo-spi-extensions](https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-rpc-extensions/dubbo-rpc-rest)
+library dependency.
+{{% /alert %}}
+
+## Introduction
+
+Since Dubbo 3.3, the Triple protocol reuses the existing HTTP stack to fully support RESTful service exports. Without the need for generic or gateway protocol conversion, users can
+directly access backend Triple protocol services via HTTP in a decentralized manner. Additionally, it offers extensive annotation and SPI extension support for advanced REST usage,
+such as path customization, output format customization, and exception handling. Key features include:
+
+- **Triple Protocol Integration**  
+  Reuses the existing Triple HTTP stack, allowing support for HTTP/1, HTTP/2, and HTTP/3 without additional configuration or new ports.
+- **Decentralization**  
+  Exposes Rest APIs directly, eliminating dependency on gateway applications for traffic forwarding, thus improving performance and reducing stability risks caused by gateways.
+  Security concerns can be addressed through internal application extensions, a practice verified in Taobao’s MTOP.
+- **Support for Existing Servlet Infrastructure**  
+  Supports Servlet API and Filter, allowing users to reuse existing security components based on the Servlet API. Integrating OAuth and Spring Security is as simple as implementing
+  a Servlet Filter.
+- **Multiple Dialects**  
+  Considering that most users are accustomed to using SpringMVC or JAX-RS for REST API development, Triple Rest allows continued use of these methods for service definitions and
+  supports most extensions and exception handling mechanisms (with over 80% of the original framework’s functionality). For lightweight users, the Basic dialect is available, and
+  Triple’s out-of-the-box REST capabilities are based on this dialect.
+- **High Extensibility**  
+  Offers more than 20 extension points, enabling users to easily create custom dialects and flexibly customize parameter retrieval, type conversion, error handling, and other
+  logic.
+- **Out-of-the-Box**  
+  REST capabilities are available out of the box; simply enable the Triple protocol to have direct REST access to services.
+- **High-Performance Routing**  
+  The routing component uses an
+  optimized [Radix Tree](https://github.com/apache/dubbo/blob/3.3/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/mapping/RadixTree.java) and Zero
+  Copy technology to improve routing performance.
+- **Seamless OpenAPI Integration (TBD)**  
+  Upcoming OpenAPI integration will allow for out-of-the-box OpenAPI Schema export. With the Swagger dependency, a Web UI can be used for service testing. Using the OpenAPI Schema,
+  API tools like [Postman](https://www.postman.com/) and [Apifox](https://apifox.com/) can manage and test APIs, and the OpenAPI ecosystem can facilitate cross-language calls.
+  Future enhancements will support a Schema First approach, allowing frontend teams to define OpenAPI collaboratively, generate call code and mocks based on OpenAPI, and enable
+  backend development using stubs generated from OpenAPI, greatly improving collaboration efficiency.
+  <a name="eyypL"></a>
+
+## Quick Start
+
+Let's explore Triple Rest with a simple example. You can directly download the existing sample project to get started quickly. Assume you have Java, Maven, and Git installed.
+
+### Download and Run the Example
+
+```bash
+# Get the sample code
+git clone --depth=1 https://github.com/apache/dubbo-samples.git
+cd dubbo-samples/2-advanced/dubbo-samples-triple-rest/dubbo-samples-triple-rest-basic
+# Run directly
+mvn spring-boot:run
+# Or package and run
+mvn clean package -DskipTests
+java -jar target/dubbo-samples-triple-rest-basic-1.0.0-SNAPSHOT.jar
+```
+
+Alternatively, you can import the project into your IDE and directly execute `org.apache.dubbo.rest.demo.BasicRestApplication#main` to run it. You can also debug by setting
+breakpoints to deeply understand the principles.
+
+### Example Code
+
+```java
+// Service Interface
+package org.apache.dubbo.rest.demo;
+
+import org.apache.dubbo.remoting.http12.rest.Mapping;
+import org.apache.dubbo.remoting.http12.rest.Param;
+
+public interface DemoService {
+    String hello(String name);
+
+    @Mapping(path = "/hi", method = HttpMethods.POST)
+    String hello(User user, @Param(value = "c", type = ParamType.Header) int count);
+}
+
+// Service Implementation
+@DubboService
+public class DemoServiceImpl implements DemoService {
+    @Override
+    public String hello(String name) {
+        return "Hello " + name;
+    }
+
+    @Override
+    public String hello(User user, int count) {
+        return "Hello " + user.getTitle() + ". " + user.getName() + ", " + count;
+    }
+}
+
+// Model
+@Data
+public class User {
+    private String title;
+    private String name;
+}
+```
+
+<a name="H68dv"></a>
+
+### Test the Basic Service
+
+```bash
+curl -v "http://127.0.0.1:8081/org.apache.dubbo.rest.demo.DemoService/hello?name=world"
+# Output:
+#> GET /org.apache.dubbo.rest.demo.DemoService/hello?name=world HTTP/1.1
+#> Host: 127.0.0.1:8081
+#> User-Agent: curl/8.7.1
+#> Accept: */*
+#>
+#* Request completely sent off
+#< HTTP/1.1 200 OK
+#< content-type: application/json
+#< alt-svc: h2=":8081"
+#< content-length: 13
+#<
+#"Hello world"
+```
+
+Explanation:<br />You see the output `"Hello world"`. The quotes are because the default content-type is `application/json`. This example demonstrates how Triple exports services
+to the `/{serviceInterface}/{methodName}` path by default and supports passing parameters via URL.
+<a name="vSW6b"></a>
+
+### Test the Advanced Service
+
+```bash
+curl -v -H "c: 3" -d 'name=Yang' "http://127.0.0.1:8081/org.apache.dubbo.rest.demo.DemoService/hi.txt?title=Mr"
+# Output:
+#> POST /org.apache.dubbo.rest.demo.DemoService/hi.txt?title=Mr HTTP/1.1
+#> Host: 127.0.0.1:8081
+#> User-Agent: curl/8.7.1
+#> Accept: */*
+#> c: 3
+#> Content-Length: 9
+#> Content-Type: application/x-www-form-urlencoded
+#>
+#* upload completely sent off: 9 bytes
+#< HTTP/1.1 200 OK
+#< content-type: text/plain
+#< alt-svc: h2=":8081"
+#< content-length: 17
+#<
+#Hello Mr. Yang, 3
+```
+
+Explanation:<br />The output `"Hello Mr. Yang, 3"` has no quotes because the `.txt` suffix was specified to request `text/plain` output. This example shows how to customize paths
+using the `Mapping` annotation, customize parameter sources with the `Param` annotation, and pass parameters via post body or URL. For more details, see
+the [Basic Usage Guide](#GdlnC)
+<a name="KNfuq"></a>
+
+### Observe Logs
+
+Enable debug logging to understand the rest startup and request response process:
+
+```yaml
+logging:
+  level:
+    "org.apache.dubbo.rpc.protocol.tri": debug
+    "org.apache.dubbo.remoting": debug
+```
+
+Once enabled, you can observe the Rest mapping registration and request process:
+
+```
+# Register mapping
+DEBUG o.a.d.r.p.t.TripleProtocol               :  [DUBBO] Register triple grpc mapping: 'org.apache.dubbo.rest.demo.DemoService' -> invoker[tri://192.168.2.216:8081/org.apache.dubbo.rest.demo.DemoService]
+ INFO .r.p.t.r.m.DefaultRequestMappingRegistry :  [DUBBO] BasicRequestMappingResolver resolving rest mappings for ServiceMeta{interface=org.apache.dubbo.rest.demo.DemoService, service=DemoServiceImpl@2a8f6e6} at url [tri://192.168.2.216:8081/org.apache.dubbo.rest.demo.DemoService]
+DEBUG .r.p.t.r.m.DefaultRequestMappingRegistry :  [DUBBO] Register rest mapping: '/org.apache.dubbo.rest.demo.DemoService/hi' -> mapping=RequestMapping{name='DemoServiceImpl#hello', path=PathCondition{paths=[org.apache.dubbo.rest.demo.DemoService/hi]}, methods=MethodsCondition{methods=[POST]}}, method=MethodMeta{method=org.apache.dubbo.rest.demo.DemoService.hello(User, int), service=DemoServiceImpl@2a8f6e6}
+DEBUG .r.p.t.r.m.DefaultRequestMappingRegistry :  [DUBBO] Register rest mapping: '/org.apache.dubbo.rest.demo.DemoService/hello' -> mapping=RequestMapping{name='DemoServiceImpl#hello~S', path=PathCondition{paths=[org.apache.dubbo.rest.demo.DemoService/hello]}}, method=MethodMeta{method=org.apache.dubbo.rest.demo.DemoService.hello(String), service=DemoServiceImpl@2a8f6e6}
+ INFO .r.p.t.r.m.DefaultRequestMappingRegistry :  [DUBBO] Registered 2 REST mappings for service [DemoServiceImpl@44627686] at url [tri://192.168.2.216:8081/org.apache.dubbo.rest.demo.DemoService] in 11ms
+
+# 请求响应
+DEBUG .a.d.r.p.t.r.m.RestRequestHandlerMapping :  [DUBBO] Received http request: DefaultHttpRequest{method='POST', uri='/org.apache.dubbo.rest.demo.DemoService/hi.txt?title=Mr', contentType='application/x-www-form-urlencoded'}
+DEBUG .r.p.t.r.m.DefaultRequestMappingRegistry :  [DUBBO] Matched rest mapping=RequestMapping{name='DemoServiceImpl#hello', path=PathCondition{paths=[/org.apache.dubbo.rest.demo.DemoService/hi]}, methods=MethodsCondition{methods=[POST]}}, method=MethodMeta{method=org.apache.dubbo.rest.demo.DemoService.hello(User, int), service=DemoServiceImpl@2a8f6e6}
+DEBUG .a.d.r.p.t.r.m.RestRequestHandlerMapping :  [DUBBO] Content-type negotiate result: request='application/x-www-form-urlencoded', response='text/plain'
+DEBUG .d.r.h.AbstractServerHttpChannelObserver :  [DUBBO] Http response body is: '"Hello Mr. Yang, 3"'
+DEBUG .d.r.h.AbstractServerHttpChannelObserver :  [DUBBO] Http response headers sent: {:status=[200], content-type=[text/plain], alt-svc=[h2=":8081"], content-length=[17]}
+```
+
+<a name="hx06z"></a>
+
+## General Features
+
+<a name="Q6XyG"></a>
+
+### Path Mapping
+
+The Triple protocol is compatible with both SpringMVC and JAX-RS mapping methods. For more information, refer to:
+
+- [Spring Mapping Requests](https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-controller/ann-requestmapping.html#mvc-ann-requestmapping-uri-templates)
+- [Spring PathPattern](https://docs.spring.io/spring-framework/docs/6.1.12/javadoc-api/org/springframework/web/util/pattern/PathPattern.html)
+- [Spring AntPathMatcher](https://docs.spring.io/spring-framework/docs/6.1.12/javadoc-api/org/springframework/util/AntPathMatcher.html)
+- [JAX-RS Path and regular expression mappings](https://docs.jboss.org/resteasy/docs/6.2.7.Final/userguide/html/ch04.html)
+
+You can also customize path mapping by implementing the SPI `org.apache.dubbo.rpc.protocol.tri.rest.mapping.RequestMappingResolver`.
+<a name="DGIWw"></a>
+
+#### Supported Patterns
+
+1. `books`: A string constant matching a fixed segment.
+2. `?`: Matches a single character.
+3. `*`: Matches zero or more characters within a path segment.
+4. `**`: Matches zero or more path segments until the end of the path.
+5. `{spring}`: Matches a path segment and captures it as a variable named "spring."
+6. `{spring:[a-z]+}`: Uses a regular expression `[a-z]+` to match a path segment and captures it as a variable named "spring."
+7. `{*spring}`: Matches zero or more path segments until the end of the path and captures them as a variable named "spring." `{*}` without a variable name indicates that no
+   capturing is done.
+   <a name="jXGEY"></a>
+
+#### Examples (from Spring Documentation)
+
+- `/pages/t?st.html`: Matches `/pages/test.html` and `/pages/tXst.html`, but not `/pages/toast.html`.
+- `/resources/*.png`: Matches all `.png` files in the `resources` directory.
+- `com/**/test.jsp`: Matches all `test.jsp` files under the `com` path.
+- `org/springframework/**/*.jsp`: Matches all `.jsp` files under the `org/springframework` path.
+- `/resources/**`: Matches all files under the `/resources/` path, including `/resources/image.png` and `/resources/css/spring.css`.
+- `/resources/{*path}`: Matches all files under `/resources/` as well as `/resources` itself, capturing the relative path as the variable "path." For example,
+  `/resources/image.png` would map to "path" → "/image.png", and `/resources/css/spring.css` would map to "path" → "/css/spring.css".
+- `/resources/{filename:\\w+}.dat`: Matches `/resources/spring.dat` and assigns the value "spring" to the `filename` variable.
+- `/{name:[a-z-]+}-{version:\\d\\.\\d\\.\\d}{ext:\\.[a-z]+}`: Matches `/example-2.1.5.html`, with `name` as `example`, `version` as `2.1.5`, and `ext` as `.html`.
+
+Tip: If you do not want the regular expression to span multiple segments, use `{name:[^/]+}`.
+<a name="JK47X"></a>
+
+#### Full Mapping Process
+
+The detailed matching logic is implemented in the following
+code: [DefaultRequestMappingRegistry.java](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/mapping/DefaultRequestMappingRegistry.java#L196), [RequestMapping.java](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/mapping/RequestMapping.java#L127).
+
+1. Normalize the path using `PathUtils.normalize` to remove indirect paths such as `/one/../` or `/one/./`, ensuring the path starts with `/`.
+2. Check if the HTTP method matches.
+3. Check if the path matches.
+4. Check if the parameter matches (not supported by JAX-RS).
+5. Check if the header matches.
+6. Check if the content type matches (Consumes).
+7. Check if the accept header matches (Produces).
+8. Check if `serviceGroup` and `serviceVersion` match.
+9. Check if the method signature matches.
+10. If no match is found, retry after removing the trailing `/` if trailing slash matching is enabled.
+11. If no match is found, retry after removing the extension if extension matching is enabled.
+12. If the last path segment contains `~`, retry with method signature matching enabled.
+13. If no candidates remain, return `null`.
+14. If one candidate remains, return it.
+15. If multiple candidates remain, sort them.
+16. Compare the first and second candidates.
+17. If the result is inconclusive, throw an exception.
+18. If the first candidate wins, return it.
+    <a name="dkeSI"></a>
+
+#### Handling Path Conflicts
+
+Unlike Spring, which raises an error and prevents startup when paths are identical, Triple Rest focuses on out-of-the-box usage. To avoid disrupting existing services, it logs a
+warning by default. At runtime, if it cannot determine the highest priority mapping, an error will be thrown.
+
+<a name="kmCzf"></a>
+
+### Parameter Types
+
+Supported parameter types vary by dialect. Please refer to the specific dialect's guide for more details. You can also customize parameter resolution by implementing the SPI
+`org.apache.dubbo.rpc.protocol.tri.rest.argument.ArgumentResolver`.
+
+#### Common Parameter Types
+
+| Name           | Description             | Basic Annotation            | SpringMVC Annotation | JAX-RS Annotation | Array or Collection Handling                  | Map Handling                     |
+|----------------|-------------------------|-----------------------------|----------------------|-------------------|-----------------------------------------------|----------------------------------|
+| Param          | Query or Form parameter | @Param                      | @RequestParam        | -                 | Multi-value                                   | Map of all parameters            |
+| Query          | URL parameter           | -                           | -                    | @QueryParam       | Multi-value                                   | Map of all Query parameters      |
+| Form           | Form parameter          | -                           | -                    | @FormParam        | Multi-value                                   | Map of all Form parameters       |
+| Header         | HTTP header             | @Param(type=Header)         | @RequestHeader       | @HeaderParam      | Multi-value                                   | Map of all Headers               |
+| Cookie         | Cookie value            | @Param(type=Cookie)         | @CookieValue         | @CookieParam      | Multi-value                                   | Map of all Cookies               |
+| Attribute      | Request attribute       | @Param(type=Attribute)      | @RequestAttribute    | -                 | Multi-value                                   | Map of all Attributes            |
+| Part           | Multipart file          | @Param(type=Part)           | @RequestHeader       | @HeaderParam      | Multi-value                                   | Map of all Parts                 |
+| Body           | Request body            | @Param(type=Body)           | @RequestBody         | @Body             | Attempts to parse as array or collection      | Attempts to parse as target type |
+| PathVariable   | Path variable           | @Param(type=PathVariable)   | @PathVariable        | @PathParam        | Single-value array or collection              | Single-value Map                 |
+| MatrixVariable | Matrix variable         | @Param(type=MatrixVariable) | @MatrixVariable      | @MatrixParam      | Multi-value                                   | Single-value Map                 |
+| Bean           | Java Bean               | No annotation needed        | @ModelAttribute      | @BeanParam        | Attempts to parse as Bean array or collection | -                                |
+
+<a name="fjYQ8"></a>
+
+#### Special Parameter Types
+
+| Type                                            | Description                    | Activation Condition     |
+|-------------------------------------------------|--------------------------------|--------------------------|
+| `org.apache.dubbo.remoting.http12.HttpRequest`  | HttpRequest object             | Activated by default     |
+| `org.apache.dubbo.remoting.http12.HttpResponse` | HttpResponse object            | Activated by default     |
+| `org.apache.dubbo.remoting.http12.HttpMethods`  | HTTP request method            | Activated by default     |
+| `java.util.Locale`                              | Request Locale                 | Activated by default     |
+| `java.io.InputStream`                           | Request InputStream            | Activated by default     |
+| `java.io.OutputStream`                          | Response OutputStream          | Activated by default     |
+| `javax.servlet.http.HttpServletRequest`         | Servlet HttpRequest object     | Requires Servlet API jar |
+| `javax.servlet.http.HttpServletResponse`        | Servlet HttpResponse object    | Same as above            |
+| `javax.servlet.http.HttpSession`                | Servlet HttpSession object     | Same as above            |
+| `javax.servlet.http.Cookie`                     | Servlet Cookie object          | Same as above            |
+| `java.io.Reader`                                | Servlet Request Reader object  | Same as above            |
+| `java.io.Writer`                                | Servlet Response Writer object | Same as above            |
+
+<a name="zS6y1"></a>
+
+#### Parameters without Annotations
+
+The handling varies by dialect; refer to the specific dialect's guide.
+<a name="MikXl"></a>
+
+#### Accessing HTTP Input and Output Parameters without Annotations
+
+You can use `RpcContext` to retrieve them:
+
+```java
+// Dubbo http req/resp
+HttpRequest request = RpcContext.getServiceContext().getRequest(HttpRequest.class);
+HttpResponse response = RpcContext.getServiceContext().getRequest(HttpResponse.class);
+// Servlet http req/resp
+HttpServletRequest request = RpcContext.getServiceContext().getRequest(HttpServletRequest.class);
+HttpServletResponse response = RpcContext.getServiceContext().getRequest(HttpServletResponse.class);
+```
+
+After obtaining the request, you can access some built-in attributes through `attribute`.
+See: [RestConstants.java](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/RestConstants.java#L40)
+<a name="I56vX"></a>
+
+### Parameter Type Conversion
+
+By default, most parameter type conversions from `String` to target types are supported, including:
+
+- JDK built-in types (e.g., basic types, date, `Optional`, etc.)
+- Array types
+- Collection types
+- Map types
+
+Generic types, including complex nesting, are fully supported. For implementation details, refer
+to: [GeneralTypeConverter.java](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/argument/GeneralTypeConverter.java).
+Custom parameter type conversion can also be achieved by implementing SPI `org.apache.dubbo.rpc.protocol.tri.rest.argument.ArgumentConverter`.
+
+| Source Type | Target Type             | Description                      | Default Value |
+|-------------|-------------------------|----------------------------------|---------------|
+| `String`    | `double`                | Converts to a double             | 0.0d          |
+| `String`    | `float`                 | Converts to a float              | 0.0f          |
+| `String`    | `long`                  | Converts to a long               | 0L            |
+| `String`    | `int`                   | Converts to an integer           | 0             |
+| `String`    | `short`                 | Converts to a short              | 0             |
+| `String`    | `char`                  | Converts to a character          | 0             |
+| `String`    | `byte`                  | Converts to a byte               | 0             |
+| `String`    | `boolean`               | Converts to a boolean            | false         |
+| `String`    | `BigInteger`            | Converts to a BigInteger         | null          |
+| `String`    | `BigDecimal`            | Converts to a BigDecimal         | null          |
+| `String`    | `Date`                  | Converts to a Date               | null          |
+| `String`    | `Calendar`              | Converts to a Calendar           | null          |
+| `String`    | `Timestamp`             | Converts to a Timestamp          | null          |
+| `String`    | `Instant`               | Converts to an Instant           | null          |
+| `String`    | `ZonedDateTime`         | Converts to a ZonedDateTime      | null          |
+| `String`    | `LocalDate`             | Converts to a LocalDate          | null          |
+| `String`    | `LocalTime`             | Converts to a LocalTime          | null          |
+| `String`    | `LocalDateTime`         | Converts to a LocalDateTime      | null          |
+| `String`    | `ZoneId`                | Converts to a ZoneId             | null          |
+| `String`    | `TimeZone`              | Converts to a TimeZone           | null          |
+| `String`    | `File`                  | Converts to a File               | null          |
+| `String`    | `Path`                  | Converts to a Path               | null          |
+| `String`    | `Charset`               | Converts to a Charset            | null          |
+| `String`    | `InetAddress`           | Converts to an InetAddress       | null          |
+| `String`    | `URI`                   | Converts to a URI                | null          |
+| `String`    | `URL`                   | Converts to a URL                | null          |
+| `String`    | `UUID`                  | Converts to a UUID               | null          |
+| `String`    | `Locale`                | Converts to a Locale             | null          |
+| `String`    | `Currency`              | Converts to a Currency           | null          |
+| `String`    | `Pattern`               | Converts to a Pattern            | null          |
+| `String`    | `Class`                 | Converts to a Class              | null          |
+| `String`    | `byte[]`                | Converts to a byte array         | null          |
+| `String`    | `char[]`                | Converts to a char array         | null          |
+| `String`    | `OptionalInt`           | Converts to an OptionalInt       | null          |
+| `String`    | `OptionalLong`          | Converts to an OptionalLong      | null          |
+| `String`    | `OptionalDouble`        | Converts to an OptionalDouble    | null          |
+| `String`    | `Enum class`            | Enum.valueOf                     | null          |
+| `String`    | `Array` or `Collection` | Split by comma                   | null          |
+| `String`    | `Specified class`       | Try JSON String to Object        | null          |
+| `String`    | `Specified class`       | Try construct with single String | null          |
+| `String`    | `Specified class`       | Try call static method `valueOf` | null          |
+
+<a name="VxFtB"></a>
+
+### Supported Content-Types
+
+By default, the following Content-Types are supported with corresponding encoding and decoding capabilities. Extension is available by implementing SPI
+`org.apache.dubbo.remoting.http12.message.(HttpMessageDecoderFactory|HttpMessageEncoderFactory)`.
+
+| Media Type                          | Description                |
+|-------------------------------------|----------------------------|
+| `application/json`                  | JSON format                |
+| `application/xml`                   | XML format                 |
+| `application/yaml`                  | YAML format                |
+| `application/octet-stream`          | Binary data                |
+| `application/grpc`                  | gRPC format                |
+| `application/grpc+proto`            | gRPC with Protocol Buffers |
+| `application/x-www-form-urlencoded` | URL-encoded form data      |
+| `multipart/form-data`               | Form data with file upload |
+| `text/json`                         | JSON format as text        |
+| `text/xml`                          | XML format as text         |
+| `text/yaml`                         | YAML format as text        |
+| `text/css`                          | CSS format                 |
+| `text/javascript`                   | JavaScript format as text  |
+| `text/html`                         | HTML format                |
+| `text/plain`                        | Plain text                 |
+
+<a name="qbOvN"></a>
+
+### Content Negotiation
+
+Supports comprehensive content negotiation to determine the output Content-Type based on mapping or input. The process is as follows:
+
+1. Try to read the mediaType specified by Mapping, retrieve the list of mediaTypes specified by Produces, and match wildcard to appropriate Media Type. For example, Spring's:
+   `@RequestMapping(produces = "application/json")`
+2. Try to find mediaType using the Accept header, parse the request's `Accept` header, and match wildcard to appropriate Media Type. For example: `Accept: application/json`
+3. Try to find mediaType using the format parameter, read the format parameter value, and match it to an appropriate Media Type. For example `/hello?format=yml`
+4. Try to find mediaType using the request path extension, match the extension to an appropriate Media Type. For example `/hello.txt`
+5. Try to use the request's Content-Type header as Media Type (excluding two form types). For example `Content-Type: application/json`
+6. Default to `application/json`
+
+<a name="DtUnB"></a>
+
+### CORS Support
+
+Provides full CORS support, enabled by configuring global parameters. Default behavior is consistent with SpringMVC. Fine-grained configuration is also supported through
+`@CrossOrigin` in SpringMVC. For supported CORS configuration items, refer to: [8.4 CORS Configuration](#NLQqj)
+<a name="O4KNd"></a>
+
+### Custom HTTP Output
+
+Custom HTTP output is required in many scenarios, such as 302 redirects or setting HTTP headers. Triple Rest offers the following generic solutions, with dialect-specific
+approaches available in each dialect's user guide:
+
+- Set the return value to: `org.apache.dubbo.remoting.http12.HttpResult` and build using `HttpResult#builder`.
+- Throw a Payload exception: `throws new org.apache.dubbo.remoting.http12.exception.HttpResultPayloadException(HttpResult)`. Example code:
+
+```java
+throw new HttpResult.found("https://a.com").
+
+toPayload();
+```
+
+This exception avoids filling error stacks, has minimal performance impact, and does not require return value logic, making it recommended for customizing output.
+
+- Customize after obtaining HttpResponse. Example code:
+
+```java
+HttpResponse response = RpcContext.getServiceContext().getRequest(HttpResponse.class);
+
+response.
+
+sendRedirect("https://a.com");
+response.
+
+setStatus(404);
+response.
+
+outputStream().
+
+write(data);
+// It is recommended to commit after writing to avoid being modified by other extensions
+response.
+
+commit();
+```
+
+If only adding `http headers`, use this method.
+<a name="OlLbS"></a>
+
+### Custom JSON Serialization
+
+Multiple JSON frameworks are supported, including Jackson, fastjson2, fastjson, and gson. Please ensure that the corresponding jar dependencies have been imported before use.
+
+#### Specifying the JSON Framework to Use
+
+```properties
+dubbo.protocol.triple.rest.json-framework=jackson
+```
+
+#### Customization through JsonUtil SPI
+
+You can customize JSON processing by implementing the SPI `org.apache.dubbo.common.json.JsonUtil`. For specific examples, you can refer to the existing implementations
+in [org/apache/dubbo/common/json/impl](https://github.com/apache/dubbo/tree/3.3/dubbo-common/src/main/java/org/apache/dubbo/common/json/impl). It is recommended to extend an
+existing implementation and override as needed.
+
+<a name="XeDPr"></a>
+
+### Exception Handling
+
+Unhandled exceptions are ultimately converted to the `ErrorResponse` class and encoded for output:
+
+```java
+
+@Data
+public class ErrorResponse {
+    /**
+     * HTTP status code
+     */
+    private String status;
+
+    /**
+     * Exception message
+     */
+    private String message;
+}
+```
+
+Note that for errors with status 500 and above, to avoid disclosing internal server information, the default message output is "Internal Server Error". To customize the message,
+create an exception that extends `org.apache.dubbo.remoting.http12.exception.HttpStatusException` and override the `getDisplayMessage` method.<br />The following general methods
+are available for customizing exception handling:
+
+- Refer to [9.2 Custom Exception Return Results](#zFD9A) for using SPI to customize global exception handling.
+- Use Dubbo's Filter SPI to process and transform exceptions. To access the HTTP context, extend `org.apache.dubbo.rpc.protocol.tri.rest.filter.RestFilterAdapter`.
+- Use SPI `org.apache.dubbo.rpc.protocol.tri.rest.filter.RestFilter` to transform exceptions, which is more lightweight and provides path matching configuration capabilities.
+
+Note that the latter two methods only intercept exceptions occurring in the invoke chain. If exceptions occur during path matching, only method 1 can handle them.
+<a name="GdlnC"></a>
+
+## Basic Usage Guide
+
+See
+example: [dubbo-samples-triple-rest/dubbo-samples-triple-rest-basic](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-rest/dubbo-samples-triple-rest-basic)
+<a name="yCnsD"></a>
+
+### Path Mapping
+
+Basic, as an out-of-the-box REST mapping, will by default map methods to: `/{contextPath}/{serviceInterface}/{methodName}`, where `/{contextPath}` will be ignored if not
+configured, resulting in: `/{serviceInterface}/{methodName}`.<br />Custom mappings are supported through the `org.apache.dubbo.remoting.http12.rest.Mapping` annotation. The
+attribute descriptions are as follows:
+
+| Config Name | Description                                                                            | Default Behavior                   |
+|-------------|----------------------------------------------------------------------------------------|------------------------------------|
+| `value`     | Mapped URL paths, which can be one or more paths.                                      | Empty array                        |
+| `path`      | Mapped URL paths, same as `value`, can be one or more paths.                           | Empty array                        |
+| `method`    | Supported HTTP methods list, such as `GET`, `POST`, etc.                               | Empty array (supports all methods) |
+| `params`    | List of parameters that must be included in the request.                               | Empty array                        |
+| `headers`   | List of headers that must be included in the request.                                  | Empty array                        |
+| `consumes`  | Content types (Content-Type) for processing requests, which can be one or more types.  | Empty array                        |
+| `produces`  | Content types (Content-Type) for generating responses, which can be one or more types. | Empty array                        |
+| `enabled`   | Whether to enable this mapping.                                                        | `true` (enabled)                   |
+
+- Attributes can be configured using placeholders: `@Mapping("${prefix}/hi")`
+- To prevent a specific service or method from being exported as REST, set `@Mapping(enabled = false)`
+  <a name="mnjpv"></a>
+
+### Parameter Types
+
+General parameters are discussed in: [3.2 Parameter Types](#kmCzf)
+
+<a name="pqC9y"></a>
+
+#### Parameters Without Annotations
+
+Basic supports parameters without annotations through the
+class: [FallbackArgumentResolver.java](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/support/basic/FallbackArgumentResolver.java#L41).
+The detailed processing flow is as follows:<br />![rest-arg.jpg](/imgs/v3/manual/java/protocol/rest-arg.jpg)
+<a name="nilSu"></a>
+
+## SpringMVC Usage Guide
+
+See
+example: [dubbo-samples-triple-rest/dubbo-samples-triple-rest-springmvc](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-rest/dubbo-samples-triple-rest-springmvc)
+<a name="m2q2A"></a>
+
+### Path Mapping
+
+Refer directly to the SpringMVC documentation, which supports most
+features, [Mapping Requests :: Spring Framework](https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-controller/ann-requestmapping.html#mvc-ann-requestmapping-uri-templates)<br />
+Note that `@Controller` or `@RestController` annotations are not required; in addition to `@RequestMapping`, the new `@HttpExchange` is also supported.
+<a name="zJiVQ"></a>
+
+### Parameter Types
+
+<a name="p6VR0"></a>
+
+#### General Parameters
+
+See: [3.2 Parameter Types](#kmCzf)
+<a name="Ukbuz"></a>
+
+#### Annotated Parameter Types
+
+See [3.2.1 Annotated Parameter Types](#dCgzz)
+<a name="xuy6I"></a>
+
+#### Special Parameter Types
+
+| Type                                                     | Description             | Activation Condition          |
+|----------------------------------------------------------|-------------------------|-------------------------------|
+| org.springframework.web.context.request.WebRequest       | WebRequest object       | SpringWeb dependency required |
+| org.springframework.web.context.request.NativeWebRequest | NativeWebRequest object | Same as above                 |
+| org.springframework.http.HttpEntity                      | Http entity             | Same as above                 |
+| org.springframework.http.HttpHeaders                     | Http headers            | Same as above                 |
+| org.springframework.util.MultiValueMap                   | Multi-value map         | Same as above                 |
+
+<a name="p64XS"></a>
+
+#### Parameters Without Annotations
+
+- For basic types (as determined
+  by [TypeUtils#isSimpleProperty](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/util/TypeUtils.java#L105)),
+  directly obtained from Parameter
+- For non-basic types,
+  use [@ModelAttribute :: Spring Framework](https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-controller/ann-methods/modelattrib-method-args.html) to bind complex
+  bean type parameters
+  <a name="w0D3L"></a>
+
+### Parameter Type Conversion
+
+Prefer using Spring's `org.springframework.core.convert.ConversionService` to convert parameters. For Spring Boot applications, the default is `mvcConversionService`; otherwise,
+use `org.springframework.core.convert.support.DefaultConversionService#getSharedInstance` to obtain the shared `ConversionService`.<br />If `ConversionService` does not support it,
+it will fall back to general type conversion: [3.3 Parameter Type Conversion](#I56vX)
+<a name="DIwI5"></a>
+
+### Exception Handling
+
+In addition to supporting the methods mentioned in [3.8 Exception Handling](#XeDPr), Spring's `@ExceptionHandler` annotation method is also
+supported, [Exceptions :: Spring Framework](https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-controller/ann-exceptionhandler.html). Note that this method only
+handles exceptions thrown during method calls; other exceptions cannot be captured.
+<a name="twi2x"></a>
+
+### CORS Configuration
+
+In addition to supporting global CORS configuration as described in [8.4 CORS Configuration](#NLQqj), Spring's `@CrossOrigin` allows for fine-grained
+configuration, [CORS :: Spring Framework](https://docs.spring.io/spring-framework/reference/web/webmvc-cors.html#mvc-cors-controller).
+<a name="GSx1f"></a>
+
+### Custom HTTP Output
+
+Supports the following Spring customization methods:
+
+1. Use `@ResponseStatus` annotation
+2. Return `org.springframework.http.ResponseEntity` object
+   <a name="HGZX4"></a>
+
+### Supported Extensions
+
+- org.springframework.web.servlet.HandlerInterceptor<br />Usage is similar to [7.1 Using Filter Extensions](#xCEi3)
+  <a name="cjzUk"></a>
+
+## JAX-RS Usage Guide
+
+See
+example: [dubbo-samples-triple-rest/dubbo-samples-triple-rest-jaxrs](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-rest/dubbo-samples-triple-rest-jaxrs)
+<a name="QxR7G"></a>
+
+### Path Mapping
+
+Services need to explicitly add the @Path annotation, and methods need to add request method annotations like @GET, @POST, @HEAD.<br />Refer directly to the Resteasy documentation,
+which supports most features, [Chapter 4. Using @Path and @GET, @POST, etc.](https://docs.jboss.org/resteasy/docs/6.2.7.Final/userguide/html/ch04.html)
+<a name="TfvLf"></a>
+
+### Parameter Types
+
+<a name="HhsqE"></a>
+
+#### General Parameters
+
+See: [3.2 Parameter Types](#kmCzf)
+<a name="GuQvr"></a>
+
+#### Annotation Type Parameters
+
+| Annotation    | Parameter Location | Description                            |
+|---------------|--------------------|----------------------------------------|
+| @QueryParam   | querystring        | Parameters corresponding to ?a=a&b=b   |
+| @HeaderParam  | header             |                                        |
+| @PathParam    | path               |                                        |
+| @FormParam    | form               | body in key1=value2&key2=value2 format |
+| No annotation | body               | Not explicitly annotated               |
+
+<a name="HmEQe"></a>
+
+#### Special Type Parameters
+
+| Type                            | Description     | Activation Condition       |
+|---------------------------------|-----------------|----------------------------|
+| javax.ws.rs.core.Cookie         | Cookie object   | Requires Jax-rs dependency |
+| javax.ws.rs.core.Form           | Form object     | Same as above              |
+| javax.ws.rs.core.HttpHeaders    | Http headers    | Same as above              |
+| javax.ws.rs.core.MediaType      | Media type      | Same as above              |
+| javax.ws.rs.core.MultivaluedMap | Multivalued Map | Same as above              |
+| javax.ws.rs.core.UriInfo        | Uri information | Same as above              |
+
+<a name="f4wnR"></a>
+
+#### Non-Annotated Parameters
+
+- For basic types (as determined
+  by [TypeUtils#isSimpleProperty](https://github.com/apache/dubbo/blob/dubbo-3.3.0-beta.5/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/protocol/tri/rest/util/TypeUtils.java#L105)),
+  directly retrieved from Parameter
+- For non-basic types, treated as request body to decode the object
+  <a name="iXjJH"></a>
+
+### Parameter Type Conversion
+
+Custom parameter conversion can be extended via the following interfaces:
+
+```
+org.apache.dubbo.rpc.protocol.tri.rest.argument.ArgumentResolver
+javax.ws.rs.ext.ParamConverterProvider
+```
+
+<a name="XRrsZ"></a>
+
+### Exception Handling
+
+Custom exception handling can be extended via the following interfaces:
+
+```
+javax.ws.rs.ext.ExceptionMapper
+org.apache.dubbo.remoting.http12.ExceptionHandler
+```
+
+<a name="rJBUU"></a>
+
+### CORS Configuration
+
+Supports [8.4 CORS Configuration](#NLQqj) global configuration
+<a name="JI88c"></a>
+
+### Custom HTTP Output
+
+Supports the following JAX-RS customizations:
+
+- Returning `javax.ws.rs.core.Response` object
+  <a name="BOh83"></a>
+
+### Supported Extensions
+
+1. javax.ws.rs.container.ContainerRequestFilter<br /> Request filter, allows pre-processing of requests before they reach the resource method.
+2. javax.ws.rs.container.ContainerResponseFilter<br /> Response filter, allows post-processing of responses after they leave the resource method.
+3. javax.ws.rs.ext.ExceptionMapper<br /> Exception mapper, maps thrown exceptions to HTTP responses.
+4. javax.ws.rs.ext.ParamConverterProvider<br /> Parameter converter, allows conversion of request parameters to resource method parameter types.
+5. javax.ws.rs.ext.ReaderInterceptor<br /> Reader interceptor, allows interception and handling when reading request entities.
+6. javax.ws.rs.ext.WriterInterceptor<br /> Writer interceptor, allows interception and handling when writing response entities.
+   <a name="TL2NU"></a>
+
+## Servlet Usage Guide
+
+For both lower version javax and higher version jakarta servlet APIs, jakarta API has higher priority. Simply include the jar to use HttpServletRequest and HttpServletResponse as
+parameters.
+<a name="xCEi3"></a>
+
+### Using Filter Extension
+
+Method 1: Implement `Filter` interface and `org.apache.dubbo.rpc.protocol.tri.rest.filter.RestExtension` interface, then register SPI
+
+```java
+import org.apache.dubbo.rpc.protocol.tri.rest.filter.RestExtension;
+
+import javax.servlet.Filter;
+import javax.servlet.ServletRequest;
+import javax.servlet.ServletResponse;
+
+public class DemoFilter implements Filter, RestExtension {
+    @Override
+    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) {
+        chain.doFilter(request, response);
+    }
+
+    @Override
+    public String[] getPatterns() {
+        return new String[]{"/demo/**", "!/demo/one"};
+    }
+
+    @Override
+    public int getPriority() {
+        return -200;
+    }
+}
+```
+
+Method 2: Implement `Supplier<Filter>` interface and `org.apache.dubbo.rpc.protocol.tri.rest.filter.RestExtension` interface, then register SPI
+
+```java
+public class DemoFilter implements Supplier<Filter>, RestExtension {
+
+    private final Filter filter = new SsoFilter();
+
+    @Override
+    public Filter get() {
+        return filter;
+    }
+}
+```
+
+This method is convenient for reusing existing Filters, and can even obtain Filter instances from Spring Context and register them
+
+```java
+public class DemoFilter implements Supplier<Filter>, RestExtension {
+
+    private final Filter filter = new SsoFilter();
+
+    public DemoFilter(FrameworkModel frameworkModel) {
+        SpringExtensionInjector injector = SpringExtensionInjector.get(frameworkModel.defaultApplication());
+        filter = injector.getInstance(SsoFilter.class, null);
+    }
+
+    @Override
+    public Filter get() {
+        return filter;
+    }
+}
+```
+
+<a name="ZAxSp"></a>
+
+### HttpSession Support
+
+Implement SPI `org.apache.dubbo.rpc.protocol.tri.rest.support.servlet.HttpSessionFactory`
+<a name="qYI1a"></a>
+
+### Unsupported Features
+
+- Wrapping request and response objects in Filter will not work due to the large number of filter types supported by Rest, leading to complex nesting and handling.
+- `request.getRequestDispatcher` is not supported
+  <a name="Sxium"></a>
+
+### Security Configuration
+
+When Rest services open direct access to the public network, there are security risks of potential attacks. Therefore, before exposing services, it's necessary to thoroughly assess
+the risks and choose appropriate authentication methods to ensure security. Triple provides various security authentication mechanisms, and users can also implement their own
+extensions to perform security checks on access.
+
+#### Basic Authentication
+
+To enable Basic Authentication, modify the following configuration:
+
+```yaml
+dubbo:
+  provider:
+    auth: true
+    authenticator: basic
+    username: admin
+    password: admin
+```
+
+Once enabled, all HTTP requests will require Basic Authentication to access.
+
+For RPC calls, you also need to configure the corresponding username and password on the consumer side:
+
+```yaml
+dubbo:
+  consumer:
+    auth: true
+    authenticator: basic
+    username: admin
+    password: admin
+```
+
+With this configuration, communication between provider and consumer will use Basic Authentication to ensure security. Make sure to use strong passwords in production environments
+and consider using HTTPS for encrypted transmission.
+
+### Authentication Extensions
+
+#### Implementing Custom Authenticator
+
+You can customize authentication by implementing the SPI `org.apache.dubbo.auth.spi.Authenticator`, and select the Authenticator to enable through the configuration
+`dubbo.provider.authenticator`.
+
+#### Implementing HTTP Request Filtering
+
+You can customize HTTP filtering logic by implementing the SPI `org.apache.dubbo.rpc.HeaderFilter` or `org.apache.dubbo.rpc.protocol.tri.rest.filter.RestFilter`.
+
+## Global Parameter Configuration
+
+<a name="rerFd"></a>
+
+### Case Sensitivity
+
+Configuration Name: `dubbo.protocol.triple.rest.case-sensitive-match`<br />Whether path matching should be case-sensitive. If enabled, methods mapped to `/users` will not match
+`/Users`<br />Default is `true`
+<a name="f1OJD"></a>
+
+### Trailing Slash Matching
+
+Configuration Name: `dubbo.protocol.triple.rest.trailing-slash-match`<br />Whether path matching should match paths with trailing slashes. If enabled, methods mapped to `/users`
+will also match `/users/`<br />Default is `true`
+<a name="U3mWL"></a>
+
+### Suffix Matching
+
+Configuration Name: `dubbo.protocol.triple.rest.suffix-pattern-match`<br />Whether path matching uses suffix pattern matching (.*). If enabled, methods mapped to `/users` will also
+match `/users.*`, with suffix content negotiation enabled, media types inferred from URL suffix, e.g., `.json` corresponds to `application/json`<br />Default is `true`
+<a name="NLQqj"></a>
+
+### CORS Configuration
+
+| Configuration Name                                  | Description                                                                                        | Default Value                            |
+|-----------------------------------------------------|----------------------------------------------------------------------------------------------------|------------------------------------------|
+| `dubbo.protocol.triple.rest.cors.allowed-origins`   | List of allowed origins for cross-origin requests, can be specific domains or `*` for all origins. | Not set (no origins allowed)             |
+| `dubbo.protocol.triple.rest.cors.allowed-methods`   | List of allowed HTTP methods, e.g., `GET`, `POST`, `PUT`, `*` for all methods.                     | Not set (only `GET` and `HEAD`)          |
+| `dubbo.protocol.triple.rest.cors.allowed-headers`   | List of allowed request headers in preflight requests, `*` for all headers.                        | Not set                                  |
+| `dubbo.protocol.triple.rest.cors.exposed-headers`   | List of response headers exposed to clients, `*` for all headers.                                  | Not set                                  |
+| `dubbo.protocol.triple.rest.cors.allow-credentials` | Whether user credentials are supported.                                                            | Not set (user credentials not supported) |
+| `dubbo.protocol.triple.rest.cors.max-age`           | Time (in seconds) that the client can cache the preflight request response.                        | Not set                                  |
+
+<a name="hAbrw"></a>
+
+## Advanced Usage Guide
+
+<a name="wKrDG"></a>
+
+### Summary of Supported Extensions
+
+1. javax.servlet.Filter<br />Servlet API filter.
+2. org.apache.dubbo.rpc.protocol.tri.rest.support.servlet.HttpSessionFactory<br />Supports HttpSession in Servlet API.
+3. javax.ws.rs.container.ContainerRequestFilter<br />JAX-RS request filter, allows pre-processing of requests before they reach the resource method.
+4. javax.ws.rs.container.ContainerResponseFilter<br />JAX-RS response filter, allows post-processing of responses after they leave the resource method.
+5. javax.ws.rs.ext.ExceptionMapper<br />JAX-RS exception mapper, maps thrown exceptions to HTTP responses.
+6. javax.ws.rs.ext.ParamConverterProvider<br />JAX-RS parameter converter, allows conversion of request parameters to resource method parameter types.
+7. javax.ws.rs.ext.ReaderInterceptor<br />JAX-RS reader interceptor, allows interception and handling when reading request entities.
+8. javax.ws.rs.ext.WriterInterceptor<br />JAX-RS writer interceptor, allows interception and handling when writing response entities.
+9. org.springframework.web.servlet.HandlerInterceptor<br />Spring MVC handler interceptor.
+10. org.apache.dubbo.remoting.http12.ExceptionHandler<br />Provides custom exception handling mechanism.
+11. org.apache.dubbo.remoting.http12.message.HttpMessageAdapterFactory<br />Provides adaptation and conversion functions for HTTP messages.
+12. org.apache.dubbo.remoting.http12.message.HttpMessageDecoderFactory<br />Provides HTTP message decoding functions.
+13. org.apache.dubbo.remoting.http12.message.HttpMessageEncoderFactory<br />Provides HTTP message encoding functions.
+14. org.apache.dubbo.rpc.HeaderFilter<br />Dubbo RPC header filter, allows filtering and handling of request and response headers.
+15. org.apache.dubbo.rpc.protocol.tri.rest.filter.RestHeaderFilterAdapter<br />Header filter adapter providing access to HTTP input and output capabilities.
+16. org.apache.dubbo.rpc.protocol.tri.rest.filter.RestFilterAdapter<br />Dubbo Filter REST adapter, providing access to HTTP input and output capabilities.
+17. org.apache.dubbo.rpc.protocol.tri.route.RequestHandlerMapping<br />Provides request mapping capability in Dubbo Triple.
+18. org.apache.dubbo.rpc.protocol.tri.rest.mapping.RequestMappingResolver<br />Resolves REST request mappings.
+19. org.apache.dubbo.rpc.protocol.tri.rest.util.RestToolKit<br />Provides REST-related tools and utilities.
+20. org.apache.dubbo.rpc.protocol.tri.rest.argument.ArgumentConverter<br />Provides argument type conversion functionality.
+21. org.apache.dubbo.rpc.protocol.tri.rest.argument.ArgumentResolver<br />Provides argument resolution functionality.
+22. org.apache.dubbo.rpc.protocol.tri.rest.filter.RestFilter<br />Provides filtering functionality for REST requests and responses.
+23. org.apache.dubbo.rpc.protocol.tri.rest.filter.RestExtensionAdapter<br />RestExtension adapter providing mapping of existing filter interfaces to RestFilter interfaces.
+    <a name="zFD9A"></a>
+
+### Custom Exception Handling
+
+Custom exception handling logic can be implemented via the SPI `org.apache.dubbo.remoting.http12.ExceptionHandler`
+
+```java
+public interface ExceptionHandler<E extends Throwable, T> {
+    /**
+     * Resolves the log level for a given throwable.
+     */
+    default Level resolveLogLevel(E throwable) {
+        return null;
+    }
+
+    /**
+     * Handle the exception and return a result.
+     */
+    default T handle(E throwable, RequestMetadata metadata, MethodDescriptor descriptor) {
+        return null;
+    }
+}
+```
+
+Implement SPI and specify the exception type E to handle
+
+- resolveLogLevel<br />Dubbo framework will log Rest handling exceptions, customize log level or ignore logs by implementing this method.
+- handle<br />If the result is not null, it will be directly returned; customize output headers and status code by returning `org.apache.dubbo.remoting.http12.HttpResult`.
+  <a name="hvJ5F"></a>
+
+### Enable Debug Logging
+
+```yaml
+logging:
+  level:
+    "org.apache.dubbo.rpc.protocol.tri": debug
+    "org.apache.dubbo.remoting": debug
+```
+
+Enable debug logging will output detailed startup logs and request/response logs for troubleshooting.
+<a name="UlKU9"></a>
+
+### Enable Verbose Output
+
+```yaml
+dubbo:
+  protocol:
+    triple:
+      verbose: true
+```
+
+Enable verbose output will return internal error stack traces to the caller and output more error logs for troubleshooting.
diff --git a/content/en/download/_index.md b/content/en/download/_index.md
index 62ae4183996..a85a11e6189 100644
--- a/content/en/download/_index.md
+++ b/content/en/download/_index.md
@@ -3,7 +3,7 @@ aliases:
     - /en/release/
 description: Download
 layout: basic
-linkTitle: Download
+linkTitle: DOWNLOAD
 menu:
     main:
         weight: 30
diff --git a/content/en/featured-background.jpg b/content/en/featured-background.jpg
index f6a02b9113e..d4bc6b77b85 100644
Binary files a/content/en/featured-background.jpg and b/content/en/featured-background.jpg differ
diff --git a/content/en/overview/_index.md b/content/en/overview/_index.md
index 368b04b18b3..15bab5c8015 100755
--- a/content/en/overview/_index.md
+++ b/content/en/overview/_index.md
@@ -1,7 +1,7 @@
 ---
 type: docs
 title: "Overview"
-linkTitle: "Overview"
+linkTitle: "DOCS"
 no_list: true
 hide_summary: true
 menu:
diff --git a/content/en/overview/demo/_index.md b/content/en/overview/demo/_index.md
new file mode 100644
index 00000000000..df6c58e4d9e
--- /dev/null
+++ b/content/en/overview/demo/_index.md
@@ -0,0 +1,6 @@
+---
+title: "Demo"
+layout: "shortcodes/blocks/demo-en"
+toc_hide: true
+---
+  {{< blocks/demo-en >}}
diff --git a/content/zh-cn/_index.html b/content/zh-cn/_index.html
index 21a7aabd411..28d5ca26677 100644
--- a/content/zh-cn/_index.html
+++ b/content/zh-cn/_index.html
@@ -4,110 +4,14 @@ linkTitle = "Apache Dubbo 官网"
 description = "Apache Dubbo 官网"
 aliases = ["/zh/"]
 +++
-
-{{< blocks/cover title="Apache Dubbo" image_anchor="top" height="min" color="secondary" >}}
-<!--<div class="mt-2 mb-3 font-weight-normal">选择编程语言后快速体验!</div>-->
-
-<!--<div class="github-stat-buttons">-->
-<!--    &lt;!&ndash; Place this tag where you want the button to render. &ndash;&gt;-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Java-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo" data-color-scheme="no-preference: dark_high_contrast; light: light_high_contrast; dark: light;"-->
-<!--       data-icon="octicon-star" data-size="large" data-show-count="true" aria-label="Star apache/dubbo on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:120px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Go-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo-go" data-icon="octicon-star"-->
-<!--       data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--    <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--        Rust-->
-<!--    </a>-->
-<!--    <a class="github-button" href="https://github.com/apache/dubbo-rust" data-icon="octicon-star"-->
-<!--       data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--    <div style="width:130px;float:left;" class="mr-5">-->
-<!--        <a class="btn btn-block btn-info mr-3 mb-2 font-weight-normal rounded" href='docs3-v2/java-sdk/home'>-->
-<!--            Node.js-->
-<!--        </a>-->
-<!--        <a class="github-button" href="https://github.com/apache/dubbo-rust" data-icon="octicon-star"-->
-<!--           data-size="large" data-show-count="true" aria-label="Star apache/dubbo-go on GitHub">Star</a>-->
-<!--    </div>-->
-<!--</div>-->
-
-<!--<div class="mx-auto">-->
-<!--    <p class="display-4 lead font-weight-light">一款易用的、具备高性能 RPC 通信及服务治理能力的微服务开发框架</p>-->
-<!--</div>-->
+{{< blocks/cover title="Apache Dubbo" image_anchor="top" height="min" color="white" >}}
 {{< /blocks/cover >}}
 
-<div id="language">
-    <h1 class="font-weight-normal">选择编程语言后快速体验!</h1>
-    <div class="language-content">
-        <a class="language-card" href='overview/mannual/java-sdk'>
-            <div class="card-title">Java</div>
-            <div class="card-img">
-                <img src="/imgs/language/java.png" alt="java">
-            </div>
-        </a>
-        <a class="language-card" href='overview/mannual/golang-sdk'>
-            <div class="card-title">Go</div>
-            <div class="card-img img-go">
-                <img src="/imgs/language/go.png" alt="golang" >
-            </div>
-        </a>
-        <a class="language-card" href='overview/mannual/rust-sdk'>
-            <div class="card-title">Rust</div>
-            <div class="card-img">
-                <img src="/imgs/language/rust.png" alt="rust">
-            </div>
-        </a>
-        <a class="language-card" target="_blank" href='https://github.com/apache/dubbo-js'>
-            <div class="card-title">Node.js</div>
-            <div class="card-img">
-                <img src="/imgs/language/node.png" alt="node.js">
-            </div>
-        </a>
-        <a class="language-card" target="_blank" href='https://github.com/apache/dubbo-python2'>
-            <div class="card-title">Python</div>
-            <div class="card-img">
-                <img src="/imgs/language/python.png" alt="python2">
-            </div>
-        </a>
-        <a class="language-card" href='overview/mannual/dubbo-go-pixiu'>
-            <div class="language-card-more"> 更多</div>
-        </a>
-    </div>
-
-
-</div>
 
 {{% blocks/lead color="white" height="min" id="whyDubbo" %}}
 <h1 class="font-weight-normal">Why Dubbo?</h1>
-<!--<p class="font-weight-light">-->
-<!--    Apache Dubbo 首先是一款 rpc 框架,通过可扩展的传输协议(二进制、基于 HTTP/2 的流式通信、HTTP+JSON 等)为微服务组件提供高性能通信,并通过 SDK 为每种语言提供易于使用的微服务配置、API 与编程范式。孵化于阿里巴巴电商应用场景,Dubbo 核心架构充分考虑了超大规模微服务集群实践诉求,历经众多行业标杆企业生产级流量考验,其构建的企业级微服务治理能力如服务发现、流量治理、可观测、认证鉴权、Service Mesh部署方案可以很好的解决企业微服务实践问题。-->
-<!--</p>-->
-<!--<p class="font-weight-light">-->
-<!--    Apache Dubbo 是一款支持多语言的、易用的 web 和 rpc 框架,同时为构建企业级微服务提供服务发现、流量治理、可观测、认证鉴权等能力、工具与最佳实践。-->
-<!--</p>-->
 {{% /blocks/lead %}}
 
-<!--{{% blocks/lead color="white" height="min" id="whyDubbo2" %}}-->
-<!--<h2>Why Dubbo?</h2>-->
-<!--&lt;!&ndash;<br/>&ndash;&gt;-->
-<!--&lt;!&ndash;<p class="font-weight-light">&ndash;&gt;-->
-<!--&lt;!&ndash;    Apache Dubbo 首先是一款 rpc 框架,通过可扩展的传输协议(二进制、基于 HTTP/2 的流式通信、HTTP+JSON 等)为微服务组件提供高性能通信,并通过 SDK 为每种语言提供易于使用的微服务配置、API 与编程范式。孵化于阿里巴巴电商应用场景,Dubbo 核心架构充分考虑了超大规模微服务集群实践诉求,历经众多行业标杆企业生产级流量考验,其构建的企业级微服务治理能力如服务发现、流量治理、可观测、认证鉴权、Service Mesh部署方案可以很好的解决企业微服务实践问题。&ndash;&gt;-->
-<!--&lt;!&ndash;</p>&ndash;&gt;-->
-<!--&lt;!&ndash;<p class="font-weight-light">&ndash;&gt;-->
-<!--&lt;!&ndash;    gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services.&ndash;&gt;-->
-<!--&lt;!&ndash;    <a href='{{< relref "/users/" >}}'>用户案例</a>&ndash;&gt;-->
-<!--&lt;!&ndash;</p>&ndash;&gt;-->
-<!--{{% /blocks/lead %}}-->
-
 {{< blocks/section id="oceanNodes" >}}
 {{% blocks/feature image="framework" url="./overview/what/advantages/usability/" %}}
 #### [快速上手](./overview/what/advantages/usability/),让开发者专注业务开发
@@ -148,65 +52,9 @@ aliases = ["/zh/"]
 </div>
 
 <div id="videoPlayer">
-    <iframe data-url="//player.bilibili.com/player.html?aid=598998096&bvid=BV1vB4y1C7wL&cid=787938568&page=1" scrolling="no" border="0" frameborder="no" framespacing="0" frameborder="0" allowfullscreen="true"></iframe>
+    <iframe data-url="//player.bilibili.com/player.html?aid=737424422&bvid=BV1YD4y1g7Qk&cid=1024306839&page=1" scrolling="no" border="0" frameborder="no" framespacing="0" frameborder="0" allowfullscreen="true"></iframe>
     <button id="closeButton"></button>
 </div>
 {{< /blocks/section >}}
 
 {{< blocks/dubbo-features >}}
-
-<div id="resources" class="community-section">
-    <h2>关注社区</h2>
-
-    <p class="community-simple">请通过以下任一或多个渠道关注社区动态,与社区开发者保持密切沟通.</p>
-
-    <div class="container">
-        <div class="community-resource">
-            <a href="/">
-                <img src="/imgs/contacts/wechat-account.jpg" alt="Wechat">
-            </a>
-            <a href="/">微信公众号</a>
-            <p>官方微信公众号(Apache Dubbo)</p>
-        </div>
-        <div id="slack" class="community-resource">
-            <a href="/">
-                <img src="/imgs/contacts/dingtalk.png" alt="Dingtalk">
-            </a>
-            <a href="/">钉钉群组</a>
-            <p>定期举办线上社区会议或开发者双周会</p>
-        </div>
-        <div id="twitter" class="community-resource">
-            <a href="https://twitter.com/apachedubbo">
-                <img src="/imgs/contacts/twitter.png" alt="Twitter">
-            </a>
-            <a href="https://twitter.com/apachedubbo">Twitter&nbsp;&#9654;</a>
-            <p><em>#apachedubbo</em></p>
-            <p>关于 Apache Dubbo 项目的国际社区动态与业界国际资讯</p>
-        </div>
-
-        <div id="github" class="community-resource">
-            <a href="https://github.com/apache/dubbo-awesome">
-                <img src="/imgs/contacts/github.png" alt="GitHub">
-            </a>
-            <a href="https://github.com/apache/dubbo-awesome">GitHub&nbsp;&#9654;</a>
-            <p>找到对应语言实现或生态项目的 GitHub 地址,即刻参与 Dubbo 项目源码贡献</p>
-        </div>
-    </div>
-</div>
-
-<!--{{< blocks/contact-us >}}-->
-
-
-<!--{{< blocks/section color="primary" >}}-->
-<!--{{% blocks/feature icon="far fa-envelope" title="订阅邮件组" %}}-->
-<!--dev@dubbo.apache.org 参与社区的讨论-->
-<!--{{% /blocks/feature %}}-->
-
-<!--{{% blocks/feature icon="fab fa-github" title="欢迎参与贡献!" url="https://github.com/apache/dubbo#contributing" %}}-->
-<!--我们通过 [Pull Request](https://github.com/apache/dubbo/pulls) 在 **GitHub** 上协作。我们期待您的加入!-->
-<!--{{% /blocks/feature %}}-->
-
-<!--{{% blocks/feature icon="fas fa-bullhorn" title="请关注我们的技术博客!" url="/zh/blog" %}}-->
-<!--我们会在第一时间分享 Dubbo 新发布的特性和使用心得-->
-<!--{{% /blocks/feature %}}-->
-<!--{{< /blocks/section >}}-->
diff --git a/content/zh-cn/blog/ web/_index.md b/content/zh-cn/blog/ web/_index.md
new file mode 100644
index 00000000000..2a29d4c05e1
--- /dev/null
+++ b/content/zh-cn/blog/ web/_index.md	
@@ -0,0 +1,9 @@
+
+---
+title: "Web"
+linkTitle: "Web"
+weight: 32
+description: "使用 Javascript 开发运行在浏览器上的 Dubbo Web 应用"
+---
+
+
diff --git a/content/zh-cn/blog/_index.md b/content/zh-cn/blog/_index.md
index 18eb94a4672..decb5322eae 100644
--- a/content/zh-cn/blog/_index.md
+++ b/content/zh-cn/blog/_index.md
@@ -3,7 +3,7 @@ title: "Apache Dubbo 博客"
 linkTitle: "博客"
 menu:
   main:
-    weight: 20
+    weight: 3
 ---
 
 
diff --git a/content/zh-cn/blog/integration/dubbo-triple-with-apisix-gateway.md b/content/zh-cn/blog/integration/dubbo-triple-with-apisix-gateway.md
new file mode 100644
index 00000000000..cb147591fbc
--- /dev/null
+++ b/content/zh-cn/blog/integration/dubbo-triple-with-apisix-gateway.md
@@ -0,0 +1,154 @@
+---
+description: |
+    本文为大家介绍了如何借助 Apache APISIX 实现 triple 协议代理,使用 nacos 作为注册中心。
+linkTitle: 使用 Apache APISIX 代理 Dubbo 服务(triple协议)
+title: 使用 Apache APISIX 代理 Dubbo 服务(triple协议)
+type: docs
+date: 2024-04-22
+weight: 2
+---
+
+关于如何用网关代理 triple 协议服务的原理介绍,请参见 [HTTP 网关接入](/zh-cn/overview/mannual/java-sdk/tasks/gateway/triple/) 一节文档。
+
+本文我们使用 `Apache APISIX + triple 协议 + Nacos 注册中心` 的组合,演示如何使用 Apache APISIX 代理 Dubbo 服务。
+
+## 示例应用说明
+
+本示例完整源码与部署资源文件可查看 [dubbo-samples-gateway-triple-apisix](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-apisix/dubbo-samples-gateway-apisix-triple),示例架构图如下:
+
+<img style="max-width:800px;height:auto;" src="/imgs/v3/tasks/gateway/apisix-nacos-dubbo.png"/>
+
+在该示例中定义并发布了一个 `org.apache.dubbo.samples.gateway.apisix.DemoService` 的 triple 服务,接口定义为:
+
+```java
+public interface DemoService {
+	String sayHello(String name);
+}
+```
+
+接口实现如下:
+
+```java
+@DubboService
+public class DemoServiceImpl implements DemoService {
+    @Override
+    public String sayHello(String name) {
+        return "Hello " + name;
+    }
+}
+```
+
+Dubbo服务相关配置:
+
+```yaml
+dubbo:
+    application:
+        name: gateway-apisix-triple
+    registry:
+        address: nacos://${nacos.address:127.0.0.1}:8848
+        username: nacos
+        password: nacos
+    protocol:
+        name: tri
+        port: 50052
+```
+
+## 部署应用
+
+1. 在 [本地下载并启动 Nacos](/zh-cn/overview/reference/integrations/nacos/#本地下载)
+
+2. 运行以下命令,启动 Dubbo 应用。
+
+下载源码:
+
+```shell
+$ git clone -b main --depth 1 https://github.com/apache/dubbo-samples
+$ cd dubbo-samples/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-apisix/dubbo-samples-gateway-apisix-triple
+```
+
+在 `dubbo-samples-gateway-apisix-triple` 目录,运行以下命令启动应用:
+
+```shell
+$ mvn compile exec:java -Dexec.mainClass="org.apache.dubbo.samples.gateway.apisix.ProviderApplication"
+```
+
+运行以下命令,测试服务已经正常启动:
+
+```shell
+curl \
+    --header "Content-Type: application/json" \
+    --data '["dubbo"]' \
+    http://localhost:50052/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/
+```
+
+## 接入 APISIX 网关
+
+本文档使用 Docker 安装 APISIX。确保本地先安装 [Docker](https://www.docker.com/) 和 [Docker Compose](https://docs.docker.com/compose/)。
+
+首先,下载 [apisix-docker](https://github.com/apache/apisix-docker) 仓库。
+
+```shell
+$ git clone https://github.com/apache/apisix-docker.git
+$ cd apisix-docker/example
+```
+
+由于本示例要接入到 Nacos 注册中心,因此需要修改 `apisix-docker/example` 目录下安装用的 `docker-compose.yaml`,添加如下 docker compose 配置内容:
+
+```yaml
+  nacos:
+    image: nacos/nacos-server:v2.1.1
+    container_name: nacos-standalone
+    environment:
+    - PREFER_HOST_MODE=hostname
+    - MODE=standalone
+    ports:
+    - "8848:8848"
+    - "9848:9848"
+    networks:
+      apisix:
+```
+
+启动 APISIX 前,在 `conf/config.yaml` 文件中增加如下配置,[让 APISIX 连接到 Nacos 注册中心](https://apisix.apache.org/docs/apisix/discovery/nacos/#service-discovery-via-nacos):
+
+```yaml
+discovery:
+  nacos:
+    host:
+      - "http://192.168.33.1:8848"
+```
+
+最后使用 `docker-compose` 启用 APISIX:`docker-compose -p docker-apisix up -d`。
+
+### 配置服务源与路由
+
+在 APISIX 中配置 Nacos upstream 及路由,即可实现后端实例地址自动发现(假设 APISIX 端口是 9080):
+
+```shell
+curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
+{
+    "uri": "/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/",
+    "upstream": {
+        "service_name": "gateway-apisix-triple",
+        "type": "roundrobin",
+        "discovery_type": "nacos"
+    }
+}'
+```
+
+> 在上述命令中,请求头 X-API-KEY 是 Admin API 的访问 token,可以在 conf/config.yaml 文件中的 apisix.admin_key.key 查看。
+
+### 验证服务调用
+
+使用以下命令发送请求至需要配置的路由:
+
+```shell
+curl -i http://127.0.0.1:9080/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/
+```
+
+### REST 模式
+
+如果您觉得 `/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/` 这样的 http 端口对于网关访问不够友好,可参考 [为 triple 协议发布 rest 风格 http 接口](/zh-cn/overview/mannual/java-sdk/tasks/gateway/triple/#rest-风格接口)。
+
+
+
+
diff --git a/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md b/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
index d624aba7ec1..b715b624b50 100644
--- a/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
+++ b/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
@@ -1,7 +1,7 @@
 ---
-title: "从原理到操作,让你在 Apache APISIX 中代理 Dubbo 服务更便捷"
+title: "使用 Apache APISIX 代理 Dubbo 服务 (dubbo 协议)"
 linkTitle: "从原理到操作,让你在 Apache APISIX 中代理 Dubbo 服务更便捷"
-date: 2022-01-18
+date: 2024-04-25
 tags: ["网关", "生态", "Java"]
 description: >
     本文为大家介绍了如何借助 Apache APISIX 实现 Dubbo Service 的代理,通过引入 dubbo-proxy 插件便可为 Dubbo 框架的后端系统构建更简单更高效的流量链路
@@ -10,32 +10,79 @@ aliases:
     - /zh/overview/what/gateway/higress/
 ---
 
-## 背景
+{{% alert title="注意" color="warning" %}}
+本文仅适用于 dubbo 协议通信场景。如果您是 Dubbo3 用户,建议您使用 triple 协议,可参见 [使用 Apache APISIX 代理 Dubbo 服务(triple协议)](/zh-cn/blog/2024/04/22/使用-apache-apisix-代理-dubbo-服务triple协议/) 学习具体示例。
+{{% /alert %}}
 
-[Apache Dubbo](/zh-cn/) 是由阿里巴巴开源并捐赠给 Apache 的微服务开发框架,它提供了 RPC 通信与微服务治理两大关键能力。不仅经过了阿里电商场景中海量流量的验证,也在国内的技术公司中被广泛落地。
-
-在实际应用场景中,Apache Dubbo 一般会作为后端系统间 RPC 调用的实现框架,当需要提供 HTTP 接口给到前端时,会通过一个「胶水层」将 Dubbo Service 包装成 HTTP 接口,再交付到前端系统。
 
 [Apache APISIX](https://apisix.apache.org/) 是 Apache 软件基金会的顶级开源项目,也是当前最活跃的开源网关项目。作为一个动态、实时、高性能的开源 API 网关,Apache APISIX 提供了负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。
 
-得益于 Apache Dubbo 的应用场景优势,Apache APISIX 基于开源项目 tengine/mod_dubbo 模块为 Apache Dubbo 服务配备了HTTP 网关能力。通过 dubbo-proxy 插件,可以轻松地将 Dubbo Service 发布为 HTTP 服务。
+Apache APISIX 基于开源项目 tengine/mod_dubbo 模块为 Apache Dubbo 服务配备了HTTP 网关能力。通过 dubbo-proxy 插件,可以轻松地将 Dubbo Service 发布为 HTTP 服务。
 
 ![架构图](/imgs/blog/apisix-plugin/1.png)
 
-## 如何使用
 
-### 入门篇:安装使用
+## 入门篇
+
+### 安装 APISIX
+
+本文档使用 Docker 安装 APISIX。确保本地先安装 [Docker](https://www.docker.com/) 和 [Docker Compose](https://docs.docker.com/compose/)。
+
+首先,下载 [apisix-docker](https://github.com/apache/apisix-docker) 仓库。
+
+```shell
+$ git clone https://github.com/apache/apisix-docker.git
+$ cd apisix-docker/example
+```
+
+由于本示例要接入到 Nacos 注册中心,因此 `apisix-docker/example` 目录下安装用的 `docker-compose.yaml`,添加如下内容:
+
+```yaml
+  nacos:
+    image: nacos/nacos-server:v2.1.1
+    container_name: nacos-standalone
+    environment:
+    - PREFER_HOST_MODE=hostname
+    - MODE=standalone
+    ports:
+    - "8848:8848"
+    - "9848:9848"
+    networks:
+      apisix:
+```
+
+在 config.yaml 文件中增加 nacos 注册中心配置:
+
+```yaml
+discovery:
+  nacos:
+    host:
+      - "http://192.168.33.1:8848"
+```
+
+在 config.yaml 文件中进行 dubbo-proxy 插件启用:
+
+```yaml
+# Add this in config.yaml
+plugins:
+  - ... # plugin you need
+  - dubbo-proxy
+```
 
->这里我们建议使用 Apache APISIX 2.11 版本镜像进行安装。该版本的 APISIX-Base 中已默认编译了 Dubbo 模块,可直接使用 `dubbo-proxy` 插件。
+> 如果你使用了 Apache APISIX 2.11 版本镜像,则可以省去 `dubbo-proxy` 配置环节,该版本的 APISIX-Base 中已默认编译了 Dubbo 模块,可直接使用。
 
-在接下来的操作中,我们将使用 [`dubbo-samples`](https://github.com/apache/dubbo-samples) 项目进行部分展示。该项目是一些使用 Apache Dubbo 实现的 Demo 应用,本文中我们采用其中的一个子模块作为 Dubbo Provider。
+最后,使用 `docker-compose` 启用 APISIX:`docker-compose -p docker-apisix up -d`
+
+### 示例说明
+
+在接下来的操作中,我们将使用 [dubbo-samples-gateway-triple-apisix](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-apisix/dubbo-samples-gateway-apisix-dubbo) 项目进行部分展示。
 
 在进入正式操作前,我们先简单看下 Dubbo 接口的定义、配置以及相关实现。
 
 #### 接口实现一览
 
 ```java
-public interface DemoService {
+public interface ApisixService {
 
     /**
      * standard samples dubbo infterace demo
@@ -48,20 +95,10 @@ public interface DemoService {
 
 如上所示,Dubbo 接口的定义是固定的。即方法参数中 `Map` 表示 APISIX 传递给 Dubbo Provider 关于 HTTP request 的一些信息(如:header、body...)。而方法返回值的 `Map` 表示 Dubbo Provider 传递给 APISIX 要如何返回 HTTP response 的一些信息。
 
-接口信息配置好之后可通过 XML 配置方式发布 DemoService。
-
-```xml
-<!-- service implementation, as same as regular local bean -->
-<bean id="demoService" class="org.apache.dubbo.samples.provider.DemoServiceImpl"/>
-
-<!-- declare the service interface to be exported -->
-<dubbo:service interface="org.apache.dubbo.samples.apisix.DemoService" ref="demoService"/>
-```
-
-通过上述配置后,Consumer 可通过 `org.apache.dubbo.samples.apisix.DemoService` 访问其中的`apisixDubbo` 方法。具体接口实现如下:
+通过上述配置后,Consumer 可通过 `org.apache.dubbo.samples.gateway.apisix.dubbo.api.ApisixService` 访问其中的`apisixDubbo` 方法。具体接口实现如下:
 
 ```java
-public class DemoServiceImpl implements DemoService {
+public class ApisixServiceImpl implements ApisixService {
     @Override
     public Map<String, Object> apisixDubbo(Map<String, Object> httpRequestContext) {
         for (Map.Entry<String, Object> entry : httpRequestContext.entrySet()) {
@@ -78,29 +115,33 @@ public class DemoServiceImpl implements DemoService {
 }
 ```
 
-上述代码中,`DemoServiceImpl` 会打印接收到的 `httpRequestContext`,并通过返回包含有指定 Key 的 Map 对象去描述该 Dubbo 请求的 HTTP 响应。
+上述代码中,`ApisixServiceImpl` 会打印接收到的 `httpRequestContext`,并通过返回包含有指定 Key 的 Map 对象去描述该 Dubbo 请求的 HTTP 响应。
 
-#### 操作步骤
+在 `dubbo-samples-gateway-apisix-dubbo` 目录,运行以下命令启动应用(或者选择使用 IDE 启动应用):
 
-1. 启动 [`dubbo-samples`](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-tengine#install-dubbo)。
-2. 在 `config.yaml` 文件中进行 `dubbo-proxy` 插件启用。
+```shell
+$ git clone -b main --depth 1 https://github.com/apache/dubbo-samples
+$ cd dubbo-samples/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-apisix/dubbo-samples-gateway-apisix-dubbo
 
-```yaml
-# Add this in config.yaml
-plugins:
-  - ... # plugin you need
-  - dubbo-proxy
+$ mvn compile exec:java -Dexec.mainClass="org.apache.dubbo.samples.gateway.apisix.dubbo.provider.ProviderApplication"
 ```
 
-3. 创建指向 Dubbo Provider 的 Upstream。
+启动 consumer 进程,验证服务正常启动,可以被调用:
+
+```shell
+$ mvn compile exec:java -Dexec.mainClass="org.apache.dubbo.samples.gateway.apisix.dubbo.consumer.ConsumerApplication"
+```
+
+### 接入APISIX
+
+1. 创建指向 Dubbo 服务的 Upstream。
 
 ```shell
 curl http://127.0.0.1:9180/apisix/admin/upstreams/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
 {
-    "nodes": {
-        "127.0.0.1:20880": 1
-    },
-    "type": "roundrobin"
+    "service_name": "gateway-apisix-dubbo",
+	"type": "roundrobin",
+	"discovery_type": "nacos"
 }'
 ```
 
@@ -109,14 +150,12 @@ curl http://127.0.0.1:9180/apisix/admin/upstreams/1  -H 'X-API-KEY: edd1c9f03433
 ```shell
 curl http://127.0.0.1:9180/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
 {
-    "host": "example.org"
     "uris": [
         "/demo"
     ],
     "plugins": {
         "dubbo-proxy": {
-            "service_name": "org.apache.dubbo.samples.apisix.DemoService",
-            "service_version": "0.0.0",
+            "service_name": "org.apache.dubbo.samples.gateway.apisix.dubbo.api.ApisixService",
             "method": "apisixDubbo"
         }
     },
@@ -171,7 +210,7 @@ Key = user-agent, Value = curl/7.80.0
 
 这样就可以将 Apache APISIX 的 「HTTP to Dubbo」 能力进一步加强,并应用到所有已存在的 Dubbo Service 中。具体操作可参考下方:
 
-1. 为已有项目增加一个 Dubbo Service 用来统一处理 HTTP to Dubbo 的转化。
+1. 为已有项目增加一个 Dubbo Service 用来统一处理 HTTP to Dubbo 的转化。方法定义如下:
 
 ```java
 public class DubboInvocationParameter {
@@ -188,9 +227,12 @@ public class DubboInvocation {
 public interface HTTP2DubboService {
     Map<String, Object> invoke(Map<String, Object> context)  throws Exception;
 }
+```
 
+2. 提供服务实现并将其发布为标准的 Dubbo 服务。网关将所有流量都转发到这个服务,由这个服务在后端进程内完成调用转发。
 
-@Component
+```java
+@DubboService
 public class HTTP2DubboServiceImpl implements HTTP2DubboService {
 
     @Autowired
@@ -216,12 +258,12 @@ public class HTTP2DubboServiceImpl implements HTTP2DubboService {
 }
 ```
 
-2. 通过如下命令请求来发起相关调用。
+3. 在 APISIX 中为 `HTTP2DubboService` 服务配置路由规则(此处省略)。接下来,就可以通过类似如下方式发起对后端 Dubbo 服务的调用了:
 
 ```shell
 curl http://127.0.0.1:9080/demo  -H "Host: example.org"  -X POST --data '
 {
-    "service": "org.apache.dubbo.samples.apisix.DemoService",
+    "service": "org.apache.dubbo.samples.apisix.UserService",
     "method": "createUser",
     "parameters": [
         {
@@ -237,3 +279,5 @@ curl http://127.0.0.1:9080/demo  -H "Host: example.org"  -X POST --data '
 本文为大家介绍了如何借助 Apache APISIX 实现 Dubbo Service 的代理,通过引入 `dubbo-proxy` 插件便可为 Dubbo 框架的后端系统构建更简单更高效的流量链路。
 
 希望通过上述操作步骤和用例场景分享,能为大家在相关场景的使用提供借鉴思路。更多关于 `dubbo-proxy` 插件的介绍与使用可参考[官方文档](https://apisix.apache.org/docs/apisix/plugins/dubbo-proxy/)。
+
+关于这部分的更多示例,还可以参考 https://github.com/chickenlj/APISIX-Dubbo-Nacos
diff --git a/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-higress.md b/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-higress.md
index 5cf17a63ce7..c20a2b32425 100644
--- a/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-higress.md
+++ b/content/zh-cn/blog/integration/how-to-proxy-dubbo-in-higress.md
@@ -1,20 +1,25 @@
 ---
 aliases:
     - /zh/overview/what/ecosystem/gateway/higress/
-description: "使用 Higress 作为 Dubbo 网关"
+description: "使用 Higress 作为 Dubbo 网关,代理 dubbo 协议服务。"
 linkTitle: 如何通过 Higress 网关代理 Dubbo 服务
 title: 如何通过 Higress 网关代理 Dubbo 服务
-date: 2023-04-01
+date: 2024-04-01
 tags: ["网关", "生态"]
 ---
+{{% alert title="注意" color="warning" %}}
+本文仅适用于 dubbo 协议通信场景。如果您是 Dubbo3 用户,建议您使用 triple 协议,具体可参见 [使用 Apache APISIX 代理 Dubbo 服务(triple协议)](/zh-cn/overview/mannual/java-sdk/tasks/gateway/triple/) 学习具体示例。
+{{% /alert %}}
 
-# Higress 对接 Dubbo 服务
 
 Higress提供了从HTTP协议到Dubbo协议进行转换的功能,用户通过配置协议转换,可以将一个Dubbo服务以HTTP接口暴露出来,从而用HTTP请求实现对Dubbo接口的调用。本文将通过一个示例来介绍如何用Higress配置HTTP到Dubbo的协议转换。该示例会引导您轻松地部署一个Nacos server和一个Dubbo服务,然后通过Ingress将HTTP请求转发到注册在Nacos上的Dubbo服务,并通过Higress的协议转换能力完成对Dubbo服务的HTTP调用。
 
+<img style="max-width:800px;height:auto;" src="/imgs/v3/tasks/gateway/http-to-dubbo.png"/>
+
+以下是一个使用 `Higress + dubbo协议 + Nacos注册中心` 的完整示例:[dubbo-samples-gateway-higress-dubbo](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-higress/dubbo-samples-gateway-higress-dubbo)。
+
 ## 前提条件
-1. Higress目前支持的Dubbo框架的版本为2.x。若您使用Dubbo3.0,要求使用dubbo协议(目前暂不支持Triple协议)。
-2. 已安装Higress,并开启了对Istio CRD的支持,参考[Higress安装部署文档](https://higress.io/zh-cn/docs/ops/deploy-by-helm)。
+1. 已安装Higress,并开启了对Istio CRD的支持,参考[Higress安装部署文档](https://higress.io/zh-cn/docs/ops/deploy-by-helm)。
 
 ## 部署Nacos和Dubbo服务
 
@@ -65,7 +70,7 @@ spec:
     app: nacos-server
   type: ClusterIP
 ```
-在K8s集群中apply以下资源,以部署一个Dubbo服务,该Dubbo服务将注册到上述的Naocs中。
+在 K8s 集群中 apply 以下资源,以部署一个Dubbo服务,该 Dubbo 服务将注册到上述的 Naocs 中(你可以选择重新打包,我们接下来直接使用社区提前准备好的镜像包)。
 ```yaml
 apiVersion: apps/v1
 kind: Deployment
@@ -91,59 +96,44 @@ spec:
             - name: DUBBO_REGISTRY_ADDRESS
               value: nacos-server.default.svc.cluster.local
 ```
-该Dubbo服务的代码可以在Nacos的[示例代码](https://github.com/nacos-group/nacos-examples/tree/master/nacos-dubbo-example)仓库中找到,其接口定义为:
+该Dubbo服务的代码可以在 [dubbo-samples-gateway-higress-dubbo](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-higress/dubbo-samples-gateway-higress-dubbo) 仓库中找到,其接口定义为:
 
 ```java
-package com.alibaba.nacos.example.dubbo.service;
+package org.apache.dubbo.samples.gateway.api;
 
 public interface DemoService {
-    String sayName(String name);
+    String sayHello(String name);
 }
 ```
 接口实现如下:
 
 ```java
-package com.alibaba.nacos.example.dubbo.service;
-
-import com.alibaba.dubbo.config.annotation.Service;
-import com.alibaba.dubbo.rpc.RpcContext;
-import org.springframework.beans.factory.annotation.Value;
-
-/**
- * Default {@link DemoService}
- *  https://nacos.io/zh-cn/docs/use-nacos-with-dubbo.html
- * @since 2.6.5
- */
 @Service(version = "${demo.service.version}", group = "${demo.service.group}")
-public class DefaultService implements DemoService {
-
-    @Value("${demo.service.name}")
-    private String serviceName;
-
-    public String sayName(String name) {
-        RpcContext rpcContext = RpcContext.getContext();
-        return String.format("Service [name :%s , port : %d] %s(\"%s\") : Hello,%s",
-                serviceName,
-                rpcContext.getLocalPort(),
-                rpcContext.getMethodName(),
-                name,
-                name);
+public class DemoServiceImpl implements DemoService {
+    @Override
+    public String sayHello(String name) {
+        return "Hello " + name;
     }
 }
 ```
-在本示例中,该Dubbo服务的服务名为com.alibaba.nacos.example.dubbo.service.DemoService,服务版本为1.0.0,服务分组为dev。
+在本示例中,该Dubbo服务的服务名为 `org.apache.dubbo.samples.gateway.api.DemoService`,服务版本为 `1.0.0`,服务分组为 `dev`。
+
+为了测试方便,我们可以通过运行以下命令来将我们部署在 K8S 集群中的 Naocs 服务映射到本地端口:
 
-为了测试方便,我们可以通过运行以下命令来将我们部署在K8s集群中的Naocs服务映射到本地端口:
 ```bash
 kubectl port-forward svc/nacos-server 8848:8848 --address='0.0.0.0' 
 ```
+
 然后请求Nacos的服务发现接口,可以查看到我们Dubbo服务的元数据信息,从而对以上部署进行验证。
+
 ```bash
-$curl -X GET 'http://127.0.0.1:8848/nacos/v1/ns/instance/list?serviceName=providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev'
+$ curl -X GET 'http://127.0.0.1:8848/nacos/v1/ns/instance/list?serviceName=providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev'
+
 {"name":"DEFAULT_GROUP@@providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev","groupName":"DEFAULT_GROUP","clusters":"","cacheMillis":10000,"hosts":[{"ip":"10.244.0.58","port":20880,"weight":1.0,"healthy":true,"enabled":true,"ephemeral":true,"clusterName":"DEFAULT","serviceName":"DEFAULT_GROUP@@providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev","metadata":{"side":"provider","release":"dubbo_demo","methods":"sayName","deprecated":"false","dubbo":"2 [...]
 ```
 ## 通过Ingress转发请求到Dubbo服务
-Higress可以通过McpBridge来对接Nacos作为服务来源,在K8s集群中apply以下资源来配置McpBridge
+Higress 可以通过 McpBridge 来对接 Nacos 作为服务来源,在 K8s 集群中 apply 以下资源来配置 McpBridge
+
 ```yaml
 apiVersion: networking.higress.io/v1
 kind: McpBridge
@@ -159,15 +149,17 @@ spec:
     port: 8848
     type: nacos2
 ```
+
 通过McpBridge,我们可以直接从Nacos中发现Dubbo服务,并为其创建路由,而无需为每一个Dubbo服务创建service资源。
 
 接下来我们创建如下Ingress,从而创建一条指向Dubbo服务的HTTP路由:
+
 ```yaml
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   annotations:
-    higress.io/destination: providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev.DEFAULT-GROUP.public.nacos
+    higress.io/destination: gateway-higress-dubbo-provider.DEFAULT-GROUP.public.nacos
   name: demo
   namespace: higress-system
 spec:
@@ -183,12 +175,24 @@ spec:
         path: /dubbo
         pathType: Prefix
 ```
-这样,path前缀为/dubbo的请求就会被路由到我们刚刚创建的Dubbo服务上。
+
+这样,path前缀为 `/dubbo` 的请求就会被路由到我们刚刚创建的 Dubbo 服务上。
+
+
+{{% alert title="注意" color="info" %}}
+以上 `higress.io/destination` 用来指定本路由的地址来源,它使用 `服务名称.服务分组.命名空间ID.nacos` 的固定格式,其中,
+* `服务名称` 可以是应用名或者接口名,Dubbo3 建议直接配置应用名,只有使用接口级服务发现时配置接口名,其格式为完整 `nacos dataid`,如 `providers:{service-name}:{version}:{group}`
+* `服务分组`,nacos 分组,未明确设置时,使用 `DEFAULT-GROUP` 即可。注意这里需要遵循 DNS 域名格式,因此服务分组中的下划线'_'被转换成了横杠'-'
+* `命名空间ID`,nacos 命空间,未明确设置时,使用 `public` 即可
+* `nacos`,使用固定值 `nacos` 代表数据来源
+{{% /alert %}}
 
 ## 通过EnvoyFilter配置HTTP到Dubbo的协议转换规则
+
 经过上述步骤,我们已经在K8s环境下部署了一套Naocs和Dubbo,并通过Ingress将path前缀为/dubbo的请求路由到我们配好的Dubbo服务上。但光是这样是无法正常通信的,因为Dubbo服务使用的是定制的Dubbo协议,无法天然与HTTP协议进行兼容。因此接下来我们将通过EnvoyFilter来配置HTTP到Dubbo的协议转换规则,从而实现用HTTP请求来调用Dubbo服务。
 
 在K8s集群中apply以下资源,要注意的是,EnvoyFilter是属于Istio的CRD,因此需要参照前提条件中的第2点来开启Higress对Istio CRD的支持。
+
 ```yaml
 apiVersion: networking.istio.io/v1alpha3
 kind: EnvoyFilter
@@ -249,13 +253,13 @@ spec:
                   path_matcher:
                     match_http_method_spec: ALL_GET
                     match_pattern: /dubbo/hello
-                name: com.alibaba.nacos.example.dubbo.service.DemoService
+                name: org.apache.dubbo.samples.gateway.api.DemoService
                 version: 1.0.0
               url_unescape_spec: ALL_CHARACTERS_EXCEPT_RESERVED
   - applyTo: CLUSTER
     match:
       cluster:
-        service: providers:com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev.DEFAULT-GROUP.public.nacos
+        service: gateway-higress-dubbo.DEFAULT-GROUP.public.nacos
       context: GATEWAY
     patch:
       operation: MERGE
@@ -269,11 +273,14 @@ spec:
 在以上EnvoyFilter中,我们配置了将path为/dubbo/hello的HTTP请求转发到Dubbo服务com.alibaba.nacos.example.dubbo.service.DemoService:1.0.0:dev中,并调用其sayName方法,而该方法的参数则通过HTTP url中的的query参数p来指定。
 
 ## 请求验证
+
 通过以上配置,我们就可以执行以下curl命令来调用这个dubbo服务了:
 ```bash
 $curl "localhost/dubbo/hello?p=abc" 
 {"result":"Service [name :demoService , port : 20880] sayName(\"abc\") : Hello,abc"}
 ```
 
-## 配置参考
-EnvoyFilter的相关配置项参考[HTTP转Dubbo配置说明](https://higress.io/zh-cn/docs/user/dubbo-envoyfilter)
\ No newline at end of file
+## 参考资料
+
+* EnvoyFilter的相关配置项参考[HTTP转Dubbo配置说明](https://higress.io/zh-cn/docs/user/dubbo-envoyfilter)
+* 完整示例源码 [dubbo-samples-gateway-higress-dubbo](https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-gateway/dubbo-samples-gateway-higress/dubbo-samples-gateway-higress-dubbo)
\ No newline at end of file
diff --git a/content/zh-cn/blog/java/codeanalysis/multiple-protocols-on-one-port.md b/content/zh-cn/blog/java/codeanalysis/multiple-protocols-on-one-port.md
new file mode 100644
index 00000000000..0e7e83f2503
--- /dev/null
+++ b/content/zh-cn/blog/java/codeanalysis/multiple-protocols-on-one-port.md
@@ -0,0 +1,135 @@
+---
+aliases:
+    - /zh/overview/tasks/protocols/multi-protocols/
+    - /zh-cn/overview/tasks/protocols/multi-protocols/
+description: ""
+linkTitle: 单端口多协议
+title: 发布使用不同协议的多个服务,通过单端口监听
+date: 2024-3-19
+author: 陈景明
+tags: ["源码解析", "协议"]
+description: >
+  Dubbo3 框架支持在单个端口发布多个不同的协议,比如可以同时发布 dubbo、triple 协议,本文介绍 Dubbo 是如何实现单端口多协议发布的。
+---
+
+
+通过对protocol进行配置,dubbo3可以支持端口的协议复用。
+比如使用Triple协议启动端口复用后,可以在相同的端口上为服务增加
+Dubbo协议支持,以及Qos协议支持。这些协议的识别都是由一个统一的端口复用
+服务器进行处理的,可以用于服务的协议迁移,并且可以节约端口以及相关的资源,减少运维的复杂性。
+
+![pu-server-image1](/imgs/blog/pu-server/pu-server-flow.png)
+
+- 在服务的创建阶段,通过从Config层获取到服务导出的协议配置从而创建不同的Protocol对象进行导出。在导出的过程
+中,如果不是第一次创建端口复用的Server,那么Exchanger会将Protcol层传递的数据保存到Server,用于后续处理该协议类型的消息。
+
+- 当客户端的消息传递过来后,首先会通过Server传递给ProtocolDetector,如果完成了识别,那么就会标记该客户端为对应的协议。并通过WireProtocol配置对应的处理逻辑,最后交给ChannelOperator完成底层的IO框架和对应的Dubbo框架的处理逻辑的绑定。
+
+- 以上的协议识别完成之后,Channel已经确定了如何处理远程的客户端消息,通过对应的ServerPipeline进行处理即可(在处理的过程中也会根据配置信息决定消息的处理线程)。
+
+## 使用方式
+在同一主机上部署多个服务或需要通过负载均衡器访问多个服务。
+
+## 参考用例
+[https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-port-unification](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-port-unification)
+
+
+## 配置方式
+
+关于Dubbo支持的配置方式,可以参考[配置说明](/zh-cn/overview/mannual/java-sdk/reference-manual/config/)
+
+### 服务多协议导出
+
+ext-protocol参数支持配置多个不同的协议,协议之间通过","进行分隔。
+
+#### xml 配置
+
+```xml
+<dubbo:protocol name="dubbo" port="-1" ext-protocol="tri,"/>
+
+<bean id="greetingService" class="org.apache.dubbo.demo.provider.GreetingServiceImpl"/>
+
+<dubbo:service delay="5000" version="1.0.0" group="greeting" timeout="5000" interface="org.apache.dubbo.demo.GreetingService" ref="greetingService" protocol="dubbo"/>
+
+```
+
+#### API 配置
+
+```java
+ProtocolConfig config = new ProtocolConfig(CommonConstants.TRIPLE, -1);
+
+config.setExtProtocol(CommonConstants.DUBBO+",");
+```
+
+#### yaml 配置
+
+``` yaml
+dubbo:
+  application:
+    name: dubbo-springboot-demo-provider
+  protocol:
+    name: tri
+    port: -1
+    ext-protocol: dubbo,
+```
+
+#### properties 配置
+```properties
+dubbo.protocol.name=tri
+dubbo.protocol.ext-protocol=dubbo,
+dubbo.protocol.port=20880
+```
+
+### Qos接入
+
+#### Qos模块导入
+
+```xml
+<dependency>
+    <groupId>org.apache.dubbo</groupId>
+    <artifactId>dubbo-qos</artifactId>
+</dependency>
+```
+
+完成Qos模块的导入之后,相关的配置项可参考[Qos操作手册](/zh-cn/overview/mannual/java-sdk/reference-manual/qos/overview/)进行配置。
+
+默认情况下,基于端口复用的Qos服务在模块导入后是启动的。
+
+## 使用方式
+
+### Qos使用
+
+将Qos协议接入到端口复用的场景下,需要在建立连接之后,客户端先向服务端发送消息,对比将Qos协议通过单个端口提供服务,端口复用版的Qos协议在处理telnet连接的情况下需要用户执行一些操作,完成协议识别(二选一)。
+
+1. 直接调用命令
+
+    直接调用telnet支持的命令也可以完成识别,在用户不熟悉的情况下可以调用help指令完成识别
+
+    ![pu-server-image2](/imgs/blog/pu-server/qos-telnet-directcall.png)
+
+2. 发送telnet命令识别
+
+   通过telnet命令建立连接之后,执行以下几个步骤:
+
+   1. 使用 crtl + "]" 进入到telnet交互界面(telnet默认的escape character)
+   2. 调用 "send ayt" 向服务端发送特殊识别字段(为telnet协议的一个特殊字段)
+   3. 回车完成消息发送并进入到dubbo的交互界面
+
+   ![pu-server-imgs3](/imgs/blog/pu-server/qos-telnet-sendayt.png)
+
+
+### 服务引用
+
+以[dubbo-samples-port-unification](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-port-unification)中的例子作为基础, 引用不同协议的服务和非端口复用情况下的配置是一致的,下面通过Consumer端的InvokerListener输出调用过程中的URL信息。
+
+```java
+ReferenceConfig<GreetingService> reference = new ReferenceConfig<>();
+reference.setInterface(GreetingService.class);
+reference.setListener("consumer");
+reference.setProtocol(this.protocol);
+// reference.setProtocol(CommonConstants.DUBBO);
+// reference.setProtocol(CommonConstants.TRIPLE);
+```
+
+![pu-server-imgs4](/imgs/blog/pu-server/reference-service.png)
+
diff --git a/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md b/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
index 4fba2d8bd7a..59688dee84e 100644
--- a/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
+++ b/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
@@ -228,7 +228,7 @@ pluginArtifact 指定了 Dubbo 定制版本的 Java Protobuf Compiler 插件,
  <pluginArtifact>org.apache.dubbo:protoc-gen-dubbo-java:1.19.0-SNAPSHOT:exe:${os.detected.classifier}</pluginArtifact>
 ```
 
-由于 `protoc-gen-dubbo-java` 支持 gRPC 和 Dubbo 两种协议,可生成的 stub 类型,默认值是 gRPC,关于 dubbo 协议的使用可参见 [使用 Protobuf 开发 Dubbo 服务](/zh-cn/overview/mannual/java-sdk/quick-start/idl/)。
+由于 `protoc-gen-dubbo-java` 支持 gRPC 和 Dubbo 两种协议,可生成的 stub 类型,默认值是 gRPC,关于 dubbo 协议的使用可参见 [使用 Protobuf 开发 Dubbo 服务](/zh-cn/overview/mannual/java-sdk/quick-start/)。
 
 ```xml
 <pluginParameter>grpc</pluginParameter>
@@ -515,7 +515,7 @@ default=org.apache.dubbo.samples.basic.comtomize.MyGrpcConfigurator
 
 **三、TLS 配置**
 
-配置方式和 Dubbo 提供的通用的 [TLS 支持](/zh-cn/overview/mannual/java-sdk/advanced-features-and-usage/security/tls/)一致,具体请参见文档
+配置方式和 Dubbo 提供的通用的 [TLS 支持](/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/tls/)一致,具体请参见文档
 
 
 
diff --git a/content/zh-cn/blog/java/demos/hystrix.md b/content/zh-cn/blog/java/demos/hystrix.md
new file mode 100644
index 00000000000..3551eace375
--- /dev/null
+++ b/content/zh-cn/blog/java/demos/hystrix.md
@@ -0,0 +1,189 @@
+---
+aliases:
+    - /zh-cn/overview/what/ecosystem/rate-limit/hystrix/
+    - /zh/overview/tasks/rate-limit/hystrix/
+    - /zh-cn/overview/tasks/rate-limit/hystrix/
+description: "使用 Hystrix 对 Dubbo 服务进行熔断限流保护"
+linkTitle: 待整合-Hystrix 熔断降级
+title: 使用 Hystrix 对 Dubbo 服务进行熔断限流保护
+tags: ["Java", "Hystrix", "限流降级"]
+date: 2023-12-14
+---
+
+## 背景
+
+Hystrix 旨在通过控制那些访问远程系统、服务和第三方库的节点,从而对延迟和故障提供更强大的容错能力。Hystrix具备拥有回退机制和断路器功能的线程和信号隔离,请求缓存和请求打包,以及监控和配置等功能。
+
+本文介绍在spring应用里,怎么把 Dubbo 和 Hystrix 结合起来使用。
+
+- <https://github.com/Netflix/Hystrix>
+- <https://github.com/apache/dubbo>
+
+## Spring Boot应用
+
+Demo 地址: <https://github.com/dubbo/dubbo-samples/tree/master/4-governance/dubbo-samples-spring-boot-hystrix>
+
+### 生成dubbo集成spring boot的应用
+
+对于不熟悉dubbo 集成spring boot应用的同学,可以在这里直接生成dubbo + spring boot的工程: <http://start.dubbo.apache.org/bootstrap.html/>
+
+### 配置spring-cloud-starter-netflix-hystrix
+
+spring boot官方提供了对hystrix的集成,直接在pom.xml里加入依赖:
+
+```xml
+        <dependency>
+            <groupId>org.springframework.cloud</groupId>
+            <artifactId>spring-cloud-starter-netflix-hystrix</artifactId>
+            <version>1.4.4.RELEASE</version>
+        </dependency>
+```
+
+然后在Application类上增加`@EnableHystrix`来启用hystrix starter:
+
+```java
+@SpringBootApplication
+@EnableHystrix
+public class ProviderApplication {
+```
+### 配置Provider端
+在Dubbo的Provider上增加`@HystrixCommand`配置,这样子调用就会经过Hystrix代理。
+```java
+@Service(version = "1.0.0")
+public class HelloServiceImpl implements HelloService {
+    @HystrixCommand(commandProperties = {
+                    @HystrixProperty(name = "circuitBreaker.requestVolumeThreshold", value = "10"),
+                    @HystrixProperty(name = "execution.isolation.thread.timeoutInMilliseconds", value = "2000") })
+    @Override
+    public String sayHello(String name) {
+        // System.out.println("async provider received: " + name);
+        // return "annotation: hello, " + name;
+        throw new RuntimeException("Exception to show hystrix enabled.");
+    }
+}
+```
+### 配置Consumer端
+对于Consumer端,则可以增加一层method调用,并在method上配置`@HystrixCommand`。当调用出错时,会走到`fallbackMethod = "reliable"`的调用里。
+```java
+    @Reference(version = "1.0.0")
+    private HelloService demoService;
+    @HystrixCommand(fallbackMethod = "reliable")
+    public String doSayHello(String name) {
+        return demoService.sayHello(name);
+    }
+    public String reliable(String name) {
+        return "hystrix fallback value";
+    }
+```
+通过上面的配置,很简单地就完成了Spring Boot里Dubbo + Hystrix的集成。
+## 传统Spring Annotation应用
+Demo地址: <https://github.com/dubbo/dubbo-samples/tree/master/4-governance/dubbo-samples-spring-hystrix>
+传统spring annotation应用的配置其实也很简单,和spring boot应用不同的是:
+1. 显式配置Spring AOP支持:`@EnableAspectJAutoProxy`
+2. 显式通过`@Configuration`配置`HystrixCommandAspect` Bean。
+```java
+    @Configuration
+    @EnableDubbo(scanBasePackages = "com.alibaba.dubbo.samples.annotation.action")
+    @PropertySource("classpath:/spring/dubbo-consumer.properties")
+    @ComponentScan(value = {"com.alibaba.dubbo.samples.annotation.action"})
+    @EnableAspectJAutoProxy
+    static public class ConsumerConfiguration {
+        @Bean
+        public HystrixCommandAspect hystrixCommandAspect() {
+            return new HystrixCommandAspect();
+        }
+    }
+```
+## Hystrix集成Spring AOP原理
+在上面的例子里可以看到,Hystrix对Spring的集成是通过Spring AOP来实现的。下面简单分析下实现。
+```java
+@Aspect
+public class HystrixCommandAspect {
+    @Pointcut("@annotation(com.netflix.hystrix.contrib.javanica.annotation.HystrixCommand)")
+    public void hystrixCommandAnnotationPointcut() {
+    }
+    @Pointcut("@annotation(com.netflix.hystrix.contrib.javanica.annotation.HystrixCollapser)")
+    public void hystrixCollapserAnnotationPointcut() {
+    }
+    @Around("hystrixCommandAnnotationPointcut() || hystrixCollapserAnnotationPointcut()")
+    public Object methodsAnnotatedWithHystrixCommand(final ProceedingJoinPoint joinPoint) throws Throwable {
+        Method method = getMethodFromTarget(joinPoint);
+        Validate.notNull(method, "failed to get method from joinPoint: %s", joinPoint);
+        if (method.isAnnotationPresent(HystrixCommand.class) && method.isAnnotationPresent(HystrixCollapser.class)) {
+            throw new IllegalStateException("method cannot be annotated with HystrixCommand and HystrixCollapser " +
+                    "annotations at the same time");
+        }
+        MetaHolderFactory metaHolderFactory = META_HOLDER_FACTORY_MAP.get(HystrixPointcutType.of(method));
+        MetaHolder metaHolder = metaHolderFactory.create(joinPoint);
+        HystrixInvokable invokable = HystrixCommandFactory.getInstance().create(metaHolder);
+        ExecutionType executionType = metaHolder.isCollapserAnnotationPresent() ?
+                metaHolder.getCollapserExecutionType() : metaHolder.getExecutionType();
+        Object result;
+        try {
+            if (!metaHolder.isObservable()) {
+                result = CommandExecutor.execute(invokable, executionType, metaHolder);
+            } else {
+                result = executeObservable(invokable, executionType, metaHolder);
+            }
+        } catch (HystrixBadRequestException e) {
+            throw e.getCause() != null ? e.getCause() : e;
+        } catch (HystrixRuntimeException e) {
+            throw hystrixRuntimeExceptionToThrowable(metaHolder, e);
+        }
+        return result;
+    }
+```
+1. `HystrixCommandAspect`里定义了两个注解的AspectJ Pointcut:`@HystrixCommand`, `@HystrixCollapser`。所有带这两个注解的spring bean都会经过AOP处理
+2. 在`@Around` AOP处理函数里,可以看到Hystrix会创建出`HystrixInvokable`,再通过`CommandExecutor`来执行
+## spring-cloud-starter-netflix-hystrix的代码分析
+1. `@EnableHystrix` 引入了`@EnableCircuitBreaker`,`@EnableCircuitBreaker`引入了`EnableCircuitBreakerImportSelector`
+   ```java
+   @EnableCircuitBreaker
+   public @interface EnableHystrix {
+   }
+
+   @Import(EnableCircuitBreakerImportSelector.class)
+   public @interface EnableCircuitBreaker {
+   }
+   ```
+2. `EnableCircuitBreakerImportSelector`继承了`SpringFactoryImportSelector<EnableCircuitBreaker>`,使spring加载`META-INF/spring.factories`里的`EnableCircuitBreaker`声明的配置
+   在`META-INF/spring.factories`里可以找到下面的配置,也就是引入了`HystrixCircuitBreakerConfiguration`。
+   ```properties
+   org.springframework.cloud.client.circuitbreaker.EnableCircuitBreaker=\
+   org.springframework.cloud.netflix.hystrix.HystrixCircuitBreakerConfiguration
+   ```
+3. 在`HystrixCircuitBreakerConfiguration`里可以发现创建了`HystrixCommandAspect`
+   ```java
+   @Configuration
+   public class HystrixCircuitBreakerConfiguration {
+
+       @Bean
+       public HystrixCommandAspect hystrixCommandAspect() {
+           return new HystrixCommandAspect();
+       }
+   ```
+可见`spring-cloud-starter-netflix-hystrix`实际上也是创建了`HystrixCommandAspect`来集成Hystrix。
+另外`spring-cloud-starter-netflix-hystrix`里还有metrics, health, dashboard等集成。
+
+## 总结
+- 对于dubbo provider的`@Service`是一个spring bean,直接在上面配置`@HystrixCommand`即可
+- 对于dubbo consumer的`@Reference`,可以通过加一层简单的spring method包装,配置`@HystrixCommand`即可
+- Hystrix本身提供`HystrixCommandAspect`来集成Spring AOP,配置了`@HystrixCommand`和`@HystrixCollapser`的spring method都会被Hystrix处理
+
+### Sentinel 与 Hystrix 的比较
+
+目前业界常用的熔断降级/隔离的库是 Netflix 的 [Hystrix](https://github.com/Netflix/Hystrix),那么 Sentinel 与 Hystrix 有什么异同呢?Hystrix 的关注点在于以 _隔离_ 和 _熔断_ 为主的容错机制,而 Sentinel 的侧重点在于多样化的流量控制、熔断降级、系统负载保护、实时监控和控制台,可以看到解决的问题还是有比较大的不同的。
+
+Hystrix 采用命令模式封装资源调用逻辑,并且资源的定义与隔离规则是强依赖的,即在创建 HystrixCommand 的时候就要指定隔离规则(因其执行模型依赖于隔离模式)。Sentinel 的设计更为简单,不关注资源是如何执行的,资源的定义与规则的配置相分离。用户可以先定义好资源,然后在需要的时候配置规则即可。Sentinel 的原则非常简单:根据对应资源配置的规则来为资源执行相应的限流/降级/负载保护策略,若规则未配置则仅进行统计。从 0.1.1 版本开始,Sentinel 还引入了[注解支持](https://github.com/alibaba/Sentinel/wiki/%E6%B3%A8%E8%A7%A3%E6%94%AF%E6%8C%81),可以更方便地定义资源。
+
+隔离是 Hystrix 的核心功能。Hystrix 通过线程池或信号量的方式来对依赖(即 Sentinel 中对应的资源)进行隔离,其中最常用的是资源隔离。Hystrix 线程池隔离的好处是比较彻底,但是不足之处在于要开很多线程池,在应用本身线程数目比较多的时候上下文切换的 overhead 会非常大;Hystrix 的信号量隔离模式可以限制调用的并发数而不显式创建线程,这样的方式比较轻量级,但缺点是无法对慢调用自动进行降级,只能等待客户端自己超时,因此仍然可能会出现级联阻塞的情况。Sentinel 可以通过并发线程数模式的流量控制来提供信号量隔离的功能。并且结合基于响应时间的熔断降级模式,可以在不稳定资源的平均响应时间比较高的时候自动降级,防止过多的慢调用占满并发数,影响整个系统。
+
+Hystrix 熔断降级功能采用熔断器模式,在某个服务失败比率高时自动进行熔断。Sentinel 的熔断降级功能更为通用,支持平均响应时间与失败比率两个指标。Sentinel 还提供各种调用链路关系和流量控制效果支持,同时还可以根据系统负载去实时地调整流量来保护系统,应用场景更为丰富。同时,Sentinel 还提供了实时的监控 API 和控制台,可以方便用户快速了解目前系统的状态,对服务的稳定性了如指掌。
+
+更详细的对比请参见 [Sentinel 与 Hystrix 的对比](https://github.com/alibaba/Sentinel/wiki/Sentinel-%E4%B8%8E-Hystrix-%E7%9A%84%E5%AF%B9%E6%AF%94)。
+
+### 链接
+- <https://github.com/Netflix/Hystrix>
+- <https://github.com/apache/dubbo>
+- <http://start.dubbo.io/>
+- <https://cloud.spring.io/spring-cloud-netflix/single/spring-cloud-netflix.html#_circuit_breaker_hystrix_clients>
diff --git a/content/zh-cn/blog/java/demos/resilience4j.md b/content/zh-cn/blog/java/demos/resilience4j.md
new file mode 100644
index 00000000000..797b88f1925
--- /dev/null
+++ b/content/zh-cn/blog/java/demos/resilience4j.md
@@ -0,0 +1,14 @@
+---
+aliases:
+  - /zh/overview/tasks/rate-limit/resilience4j/
+  - /zh-cn/overview/tasks/rate-limit/resilience4j/
+description: "使用 Resilience4j 断路器、限流器、重试、隔离机制保护 Dubbo 应用"
+linkTitle: Resilience4j
+title: 使用 Resilience4j 断路器、限流器、重试、隔离机制保护 Dubbo 应用
+tags: ["Java", "Resilience4j", "限流降级"]
+date: 2023-12-14
+---
+
+Resilience4j 提供了一组高阶函数(装饰器),包括断路器,限流器,重试,隔离,可以对任何的函数式接口,lambda表达式,或方法的引用进行增强,并且这些装饰器可以进行叠加。这样做的好处是,你可以根据需要选择特定的装饰器进行组合。
+
+关于 Resilience4j 与 Dubbo 集成的使用示例请参见 [dubbo-samples-resilience4j](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-resilience4j)
diff --git a/content/zh-cn/blog/java/proposals/_index.md b/content/zh-cn/blog/java/proposals/_index.md
new file mode 100644
index 00000000000..cfafe94c7d7
--- /dev/null
+++ b/content/zh-cn/blog/java/proposals/_index.md
@@ -0,0 +1,7 @@
+---
+title: "方案设计"
+linkTitle: "方案设计"
+weight: 30
+---
+
+
diff --git a/content/zh-cn/blog/java/proposals/service-discovery-migration.md b/content/zh-cn/blog/java/proposals/service-discovery-migration.md
new file mode 100644
index 00000000000..9716a859dbf
--- /dev/null
+++ b/content/zh-cn/blog/java/proposals/service-discovery-migration.md
@@ -0,0 +1,401 @@
+---
+aliases:
+  - /zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/migration-service-discovery/
+title: "如果从接口级服务发现平滑迁移到应用级服务发现"
+linkTitle: "Dubbo3 服务发现平滑迁移步骤与原理"
+tags: ["Java","服务发现"]
+date: 2024-05-13
+description: >
+   "Dubbo3 应用级服务发现迁移详情,如果从接口级服务发现平滑迁移到应用级服务发现,迁移规则详情与工作原理。"
+---
+
+总体上来说,在地址注册与发现环节,`3.x` 是完全兼容 `2.x` 版本的,这意味着,用户可以选择将集群内任意数量的应用或机器升级到 `3.x`,同时在这个过程中保持与 `2.x` 版本的互操作性。
+
+> 如关心迁移背后工作原理,请参考 [迁移规则详情与工作原理](../service-discovery-rule)
+
+## 1 快速升级步骤
+
+简单的修改 pom.xml 到最新版本就可以完成升级,如果要迁移到应用级地址,只需要调整开关控制 3.x 版本的默认行为。
+
+1. 升级 Provider 应用到最新 3.x 版本依赖,配置双注册开关`dubbo.application.register-mode=all`(建议通过全局配置中心设置,默认已自动开启),完成应用发布。
+2. 升级 Consumer 应用到最新 3.x 版本依赖,配置双订阅开关`dubbo.application.service-discovery.migration=APPLICATION_FIRST`(建议通过全局配置中心设置,默认已自动开启),完成应用发布。
+3. 在确认 Provider 的上有 Consumer 全部完成应用级地址迁移后,Provider 切到应用级地址单注册。完成升级
+
+
+
+以下是关于迁移流程的详细描述。
+
+## 2 Provider 端升级过程详解
+
+在不改变任何 Dubbo 配置的情况下,可以将一个应用或实例升级到 3.x 版本,升级后的 Dubbo 实例会默保保证与 2.x 版本的兼容性,即会正常注册 2.x 格式的地址到注册中心,因此升级后的实例仍会对整个集群仍保持可见状态。
+
+同时新的地址发现模型(注册应用级别的地址)也将会自动注册。
+
+![//imgs/v3/migration/provider-registration.png](/imgs/v3/migration/provider-registration.png)
+
+1. 全局开关
+
+应用配置(可以通过配置文件或者 -D 指定)`dubbo.application.register-mode` 为 instance(只注册应用级)、all(接口级+应用级均注册)开启全局的注册开关,配置此开关后,默认会向所有的注册中心中注册应用级的地址,供消费端服务发现使用。
+
+```
+# 双注册
+dubbo.application.register-mode=all
+```
+```
+# 仅应用级注册
+dubbo.application.register-mode=instance
+```
+通过 -D 参数,可以指定 provider 启动时的注册行为
+
+```text
+-Ddubbo.application.register-mode=all
+# 可选值 interface、instance、all,默认是 all,即接口级地址、应用级地址都注册
+```
+
+另外,可以在配置中心修改全局默认行为,来控制所有 3.x 实例注册行为。其中,全局性开关的优先级低于 -D 参数。
+
+2. 注册中心地址参数配置
+
+注册中心的地址上可以配置 `registry-type=service` 来显示指定该注册中心为应用级服务发现的注册中心,带上此配置的注册中心将只进行应用级服务发现。
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/dubbo-provider.xml)
+
+```xml
+<dubbo:registry address="nacos://${nacos.address:127.0.0.1}:8848?registry-type=service"/>
+```
+
+为了保证平滑迁移,即升级到 3.x 的实例能同时被 2.x 与 3.x 的消费者实例发现,3.x 实例需要开启双注册;当所有上游的消费端都迁移到 3.x 的地址模型后,提供端就可以切换到 instance 模式(只注册应用级地址)。对于如何升级消费端到 3.x 请参见下一小节。
+
+### 2.1 双注册带来的资源消耗
+
+双注册不可避免的会带来额外的注册中心存储压力,但考虑到应用级地址发现模型的数据量在存储方面的极大优势,即使对于一些超大规模集群的用户而言,新增的数据量也并不会带来存储问题。总体来说,对于一个普通集群而言,数据增长可控制在之前数据总量的 1/100 ~ 1/1000
+
+以一个中等规模的集群实例来说: 2000 实例、50个应用(500 个 Dubbo 接口,平均每个应用 10 个接口)。
+
+​	假设每个接口级 URL 地址平均大小为 5kb,每个应用级 URL 平均大小为 0.5kb
+
+​	老的接口级地址量:2000 * 500 * 5kb ≈ 4.8G
+
+​	新的应用级地址量:2000 * 50 * 0.5kb  ≈ 48M
+
+​	双注册后仅仅增加了 48M 的数据量。
+
+
+
+## 3 Consumer 端升级过程
+
+对于 2.x 的消费者实例,它们看到的自然都是 2.x 版本的提供者地址列表;
+
+对于 3.x 的消费者,它具备同时发现 2.x 与 3.x 提供者地址列表的能力。在默认情况下,如果集群中存在可以消费的 3.x 的地址,将自动消费 3.x 的地址,如果不存在新地址则自动消费 2.x 的地址。Dubbo3 提供了开关来控制这个行为:
+
+```text
+dubbo.application.service-discovery.migration=APPLICATION_FIRST
+# 可选值
+# FORCE_INTERFACE,只消费接口级地址,如无地址则报错,单订阅 2.x 地址
+# APPLICATION_FIRST,智能决策接口级/应用级地址,双订阅
+# FORCE_APPLICATION,只消费应用级地址,如无地址则报错,单订阅 3.x 地址
+```
+
+![//imgs/v3/migration/consumer-subscription.png](/imgs/v3/migration/consumer-subscription.png)
+
+1. 默认配置(不需要配置)
+
+升级到 Dubbo 3.0 后默认行为为接口级+应用级多订阅,如果应用级能订阅到地址就使用应用级的订阅,如果订阅不到地址则使用接口级的订阅,以此保证最大的兼容性。
+
+2. 订阅参数配置
+
+应用配置(可以通过配置文件或者 -D 指定)`dubbo.application.service-discovery.migration` 为 `APPLICATION_FIRST` 可以开启多订阅模式,配置为 `FORCE_APPLICATION` 可以强制为仅应用级订阅模式。
+具体接口订阅可以在 `ReferenceConfig` 中的 `parameters` 中配置 Key 为 `migration.step`,Value 为 `APPLICATION_FIRST` 或 `FORCE_APPLICATION` 的键值对来对单一订阅进行配置。
+
+`dubbo.application.service-discovery.migration ` 支持通过 `-D` 以及 `全局配置中心` 两种方式进行配置。
+
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
+
+```java
+System.setProperty("dubbo.application.service-discovery.migration", "APPLICATION_FIRST");
+```
+```java
+ReferenceConfig<DemoService> referenceConfig = new ReferenceConfig<>(applicationModel.newModule());
+referenceConfig.setInterface(DemoService.class);
+referenceConfig.setParameters(new HashMap<>());
+referenceConfig.getParameters().put("migration.step", mode);
+return referenceConfig.get();
+```
+
+3. 动态配置(优先级最高,可以在运行时修改配置)
+
+此配置需要基于配置中心进行推送,Key 为应用名 + `.migration` (如 `demo-application.migraion`),Group 为 `DUBBO_SERVICEDISCOVERY_MIGRATION`。规则体配置详见[接口级服务发现迁移至应用级服务发现指南](../migration-service-discovery/)。
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
+
+```java
+step: FORCE_INTERFACE
+```
+
+
+接下来,我们就具体看一下,如何通过双订阅模式(APPLICATION_FIRST)让升级到 3.x 的消费端迁移到应用级别的地址。在具体展开之前,先明确一条消费端的选址行为:**对于双订阅的场景,消费端虽然可同时持有 2.x 地址与 3.x 地址,但选址过程中两份地址是完全隔离的:要么用 2.x 地址,要么用 3.x 地址,不存在两份地址混合调用的情况,这个决策过程是在收到第一次地址通知后就完成了的。**
+
+
+
+下面,我们看一个`APPLICATION_FIRST`策略的具体操作过程。
+
+首先,提前在全局配置中心 Nacos 配置一条配置项(所有消费端都将默认执行这个选址策略):
+
+![//imgs/v3/migration/nacos-migration-item.png](/imgs/v3/migration/nacos-migration-item.png)
+
+
+
+紧接着,升级消费端到 3.x 版本并启动,这时消费端读取到`APPLICATION_FIRST`配置后,执行双订阅逻辑(订阅 2.x 接口级地址与 3.x 应用级地址)
+
+
+
+至此,升级操作就完成了,剩下的就是框架内部的执行了。在调用发生前,框架在消费端会有一个“选址过程”,注意这里的选址和之前 2.x 版本是有区别的,选址过程包含了两层筛选:
+
+* 先进行地址列表(ClusterInvoker)筛选(接口级地址 or 应用级地址)
+* 再进行实际的 provider 地址(Invoker)筛选。
+
+![//imgs/v3/migration/migration-cluster-item.png](/imgs/v3/migration/migration-cluster-invoker.png)
+
+ClusterInvoker 筛选的依据,可以通过 MigrationAddressComparator SPI 自行定义,目前官方提供了一个简单的地址数量比对策略,即当 `应用级地址数量 == 接口级地址数量` 满足时则进行迁移。
+
+> 其实 FORCE_INTERFACE、APPLICATION_FIRST、FORCE_APPLICATION 控制的都是这里的 ClusterInvoker 类型的筛选策略
+
+
+
+### 3.1 双订阅带来的资源消耗
+
+双订阅不可避免的会增加消费端的内存消耗,但由于应用级地址发现在地址总量方面的优势,这个过程通常是可接受的,我们从两个方面进行分析:
+
+1. 双订阅带来的地址推送数据量增长。这点我们在 ”双注册资源消耗“ 一节中做过介绍,应用级服务发现带来的注册中心数据量增长非常有限。
+2. 双订阅带来的消费端内存增长。要注意双订阅只存在于启动瞬态,在ClusterInvoker选址决策之后其中一份地址就会被完全销毁;对单个服务来说,启动阶段双订阅带来的内存增长大概能控制在原内存量的 30% ~ 40%,随后就会下降到单订阅水平,如果切到应用级地址,能实现内存 50% 的下降。
+
+
+
+### 3.2 消费端更细粒度的控制
+
+除了全局的迁移策略之外,Dubbo 在消费端提供了更细粒度的迁移策略支持。控制单位可以是某一个消费者应用,它消费的服务A、服务B可以有各自独立的迁移策略,具体是用方式是在消费端配置迁移规则:
+
+
+```yaml
+key: demo-consumer
+step: APPLICATION_FIRST
+applications:
+ - name: demo-provider
+   step: FORCE_APPLICATION
+services:
+ - serviceKey: org.apache.dubbo.config.api.DemoService:1.0.0
+   step: FORCE_INTERFACE
+```
+
+使用这种方式能做到比较精细迁移控制,但是当下及后续的改造成本会比较高,除了一些特别场景,我们不太推荐启用这种配置方式。
+[迁移指南](../service-discovery-rule/)官方推荐使用的全局的开关式的迁移策略,让消费端实例在启动阶段自行决策使用哪份可用的地址列表。
+
+
+
+## 4 迁移状态的收敛
+
+为了同时兼容 2.x 版本,升级到 3.x 版本的应用在一段时间内要么处在双注册状态,要么处在双订阅状态。
+
+解决这个问题,我们还是从 Provider 视角来看,当所有的 Provider 都切换到应用级地址注册之后,也就不存在双订阅的问题了。
+
+### 4.1 不同的升级策略影响很大
+
+毫无疑问越早越彻底的升级,就能尽快摆脱这个局面。设想,如果可以将组织内所有的应用都升级到 3.x 版本,则版本收敛就变的非常简单:升级过程中 Provider 始终保持双注册,当所有的应用都升级到 3.x 之后,就可以调整全局默认行为,让 Provider 都变成应用级地址单注册了,这个过程并不会给 Consumer 应用带来困扰,因为它们已经是可以识别应用级地址的 3.x 版本了。
+
+如果没有办法做到应用的全量升级,甚至在相当长的时间内只能升级一部分应用,则不可避免的迁移状态要持续比较长的时间。
+在这种情况下,我们追求的只能是尽量保持已升级应用的上下游实现版本及功能收敛。推动某些 Provider 的上游消费者都升级到 Dubbo3,这样就可以解除这部分 Provider 的双注册,要做到这一点,可能需要一些辅助统计工具的支持。
+
+1. 要能分析出应用间的依赖关系,比如一个 Provdier 应用被哪些消费端应用消费,这可以通过 Dubbo 提供的服务元数据上报能力来实现。
+2. 要能知道每个应用当前使用的 dubbo 版本,可以通过扫描或者主动上报手段。
+
+## 5. 迁移状态模型
+
+在 Dubbo 3 之前地址注册模型是以接口级粒度注册到注册中心的,而 Dubbo 3 全新的应用级注册模型注册到注册中心的粒度是应用级的。从注册中心的实现上来说是几乎不一样的,这导致了对于从接口级注册模型获取到的 invokers 是无法与从应用级注册模型获取到的 invokers 进行合并的。为了帮助用户从接口级往应用级迁移,Dubbo 3 设计了 Migration 机制,基于三个状态的切换实现实际调用中地址模型的切换。
+
+![//imgs/v3/migration/migration-1.png](/imgs/v3/migration/migration-1.png)
+
+当前共存在三种状态,FORCE_INTERFACE(强制接口级),APPLICATION_FIRST(应用级优先)、FORCE_APPLICATION(强制应用级)。
+
+
+FORCE_INTERFACE:只启用兼容模式下接口级服务发现的注册中心逻辑,调用流量 100% 走原有流程
+APPLICATION_FIRST:开启接口级、应用级双订阅,运行时根据阈值和灰度流量比例动态决定调用流量走向
+FORCE_APPLICATION:只启用新模式下应用级服务发现的注册中心逻辑,调用流量 100% 走应用级订阅的地址
+
+
+### 5.1 规则体说明
+
+
+规则采用 yaml 格式配置,具体配置下参考如下:
+```yaml
+key: 消费者应用名(必填)
+step: 状态名(必填)
+threshold: 决策阈值(默认1.0)
+proportion: 灰度比例(默认100)
+delay: 延迟决策时间(默认0)
+force: 强制切换(默认 false)
+interfaces: 接口粒度配置(可选)
+  - serviceKey: 接口名(接口 + : + 版本号)(必填)
+    threshold: 决策阈值
+    proportion: 灰度比例
+    delay: 延迟决策时间
+    force: 强制切换
+    step: 状态名(必填)
+  - serviceKey: 接口名(接口 + : + 版本号)
+    step: 状态名
+applications: 应用粒度配置(可选)
+  - serviceKey: 应用名(消费的上游应用名)(必填)
+    threshold: 决策阈值
+    proportion: 灰度比例
+    delay: 延迟决策时间
+    force: 强制切换
+    step: 状态名(必填)
+```
+
+
+- key: 消费者应用名
+- step: 状态名(FORCE_INTERFACE、APPLICATION_FIRST、FORCE_APPLICATION)
+- threshold: 决策阈值(浮点数,具体含义参考后文)
+- proportion: 灰度比例(0~100,决定调用次数比例)
+- delay: 延迟决策时间(延迟决策的时间,实际等待时间为 1~2 倍 delay 时间,取决于注册中心第一次通知的时间,对于目前 Dubbo 的注册中心实现次配置项保留 0 即可)
+- force: 强制切换(对于 FORCE_INTERFACE、FORCE_APPLICATION 是否不考虑决策直接切换,可能导致无地址调用失败问题)
+- interfaces: 接口粒度配置
+
+
+
+参考配置示例如下:
+```yaml
+key: demo-consumer
+step: APPLICATION_FIRST
+threshold: 1.0
+proportion: 60
+delay: 0
+force: false
+interfaces:
+  - serviceKey: DemoService:1.0.0
+    threshold: 0.5
+    proportion: 30
+    delay: 0
+    force: true
+    step: APPLICATION_FIRST
+  - serviceKey: GreetingService:1.0.0
+    step: FORCE_APPLICATION
+```
+
+
+### 5.1 配置方式说明
+#### 1. 配置中心配置文件下发(推荐)
+
+
+- Key:    消费者应用名 + ".migration"
+- Group: DUBBO_SERVICEDISCOVERY_MIGRATION
+
+
+配置项内容参考上一节
+
+
+程序启动时会拉取此配置作为最高优先级启动项,当配置项为启动项时不执行检查操作,直接按状态信息达到终态。
+程序运行过程中收到新配置项将执行迁移操作,过程中根据配置信息进行检查,如果检查失败将回滚为迁移前状态。迁移是按接口粒度执行的,也即是如果一个应用有 10 个接口,其中 8 个迁移成功,2 个失败,那终态 8 个迁移成功的接口将执行新的行为,2 个失败的仍为旧状态。如果需要重新触发迁移可以通过重新下发规则达到。
+
+
+注:如果程序在迁移时由于检查失败回滚了,由于程序无回写配置项行为,所以如果此时程序重启了,那么程序会直接按照新的行为不检查直接初始化。
+
+
+#### 2. 启动参数配置
+
+
+- 配置项名:dubbo.application.service-discovery.migration
+- 允许值范围:FORCE_INTERFACE、APPLICATION_FIRST、FORCE_APPLICATION
+
+
+
+此配置项可以通过环境变量或者配置中心传入,启动时优先级比配置文件低,也即是当配置中心的配置文件不存在时读取此配置项作为启动状态。
+
+
+#### 3. 本地文件配置
+
+
+
+| 配置项名 | 默认值 | 说明 |
+| --- | --- | --- |
+| dubbo.migration.file | dubbo-migration.yaml | 本地配置文件路径 |
+| dubbo.application.migration.delay | 60000 | 配置文件延迟生效时间(毫秒) |
+
+配置文件中格式与前文提到的规则一致
+
+
+本地文件配置方式本质上是一个延时配置通知的方式,本地文件不会影响默认启动方式,当达到延时时间后触发推送一条内容和本地文件一致的通知。这里的延时时间与规则体中的 delay 字段无关联。
+本地文件配置方式可以保证启动以默认行为初始化,当达到延时时触发迁移操作,执行对应的检查,避免启动时就以终态方式启动。
+
+
+### 5.2 决策说明
+##### 1. 阈值探测
+
+
+阈值机制旨在进行流量切换前的地址数检查,如果应用级的可使用地址数与接口级的可用地址数对比后没达到阈值将检查失败。
+
+
+核心代码如下:
+```java
+if (((float) newAddressSize / (float) oldAddressSize) >= threshold) {
+    return true;
+}
+return false;
+```
+
+
+同时 MigrationAddressComparator 也是一个 SPI 拓展点,用户可以自行拓展,所有检查的结果取交集。
+
+
+##### 2. 灰度比例
+
+
+灰度比例功能仅在应用级优先状态下生效。此功能可以让用户自行决定调用往新模式应用级注册中心地址的调用数比例。灰度生效的前提是满足了阈值探测,在应用级优先状态下,如果阈值探测通过,`currentAvailableInvoker` 将被切换为对应应用级地址的 invoker;如果探测失败 `currentAvailableInvoker` 仍为原有接口级地址的 invoker。
+
+
+流程图如下:
+探测阶段
+![//imgs/v3/migration/migration-2.png](/imgs/v3/migration/migration-2.png)
+调用阶段
+![//imgs/v3/migration/migration-3.png](/imgs/v3/migration/migration-3.png)
+
+
+核心代码如下:
+```java
+// currentAvailableInvoker is based on MigrationAddressComparator's result
+if (currentAvailableInvoker != null) {
+    if (step == APPLICATION_FIRST) {
+        // call ratio calculation based on random value
+        if (ThreadLocalRandom.current().nextDouble(100) > promotion) {
+            return invoker.invoke(invocation);
+        }
+    }
+    return currentAvailableInvoker.invoke(invocation);
+}
+
+```
+
+
+### 5.3 切换过程说明
+
+
+地址迁移过程中涉及到了三种状态的切换,为了保证平滑迁移,共有 6 条切换路径需要支持,可以总结为从强制接口级、强制应用级往应用级优先切换;应用级优先往强制接口级、强制应用级切换;还有强制接口级和强制应用级互相切换。
+对于同一接口切换的过程总是同步的,如果前一个规则还未处理完就收到新规则则回进行等待。
+
+
+###### 1. 切换到应用级优先
+
+
+从强制接口级、强制应用级往应用级优先切换本质上是从某一单订阅往双订阅切换,保留原有的订阅并创建另外一种订阅的过程。这个切换模式下规则体中配置的 delay 配置不会生效,也即是创建完订阅后马上进行阈值探测并决策选择某一组订阅进行实际优先调用。由于应用级优先模式是支持运行时动态进行阈值探测,所以对于部分注册中心无法启动时即获取全量地址的场景在全部地址通知完也会重新计算阈值并切换。
+应用级优先模式下的动态切换是基于服务目录(Directory)的地址监听器实现的。
+![//imgs/v3/migration/migration-4.png](/imgs/v3/migration/migration-4.png)
+
+
+###### 2. 应用级优先切换到强制
+
+
+应用级优先往强制接口级、强制应用级切换的过程是对双订阅的地址进行检查,如果满足则对另外一份订阅进行销毁,如果不满足则回滚保留原来的应用级优先状态。
+如果用户希望这个切换过程不经过检查直接切换可以通过配置 force 参数实现。
+![//imgs/v3/migration/migration-5.png](/imgs/v3/migration/migration-5.png)
+###### 3. 强制接口级和强制应用级互相切换
+
+
+强制接口级和强制应用级互相切换需要临时创建一份新的订阅,判断新的订阅(即阈值计算时使用新订阅的地址数去除旧订阅的地址数)是否达标,如果达标则进行切换,如果不达标会销毁这份新的订阅并且回滚到之前的状态。
+![//imgs/v3/migration/migration-6.png](/imgs/v3/migration/migration-6.png)
diff --git a/content/zh-cn/blog/java/proposals/service-discovery-rule.md b/content/zh-cn/blog/java/proposals/service-discovery-rule.md
new file mode 100644
index 00000000000..f89e8ad74e4
Binary files /dev/null and b/content/zh-cn/blog/java/proposals/service-discovery-rule.md differ
diff --git a/content/zh-cn/blog/java/proposals/service-discovery-samples.md b/content/zh-cn/blog/java/proposals/service-discovery-samples.md
new file mode 100644
index 00000000000..876f291d395
--- /dev/null
+++ b/content/zh-cn/blog/java/proposals/service-discovery-samples.md
@@ -0,0 +1,87 @@
+---
+aliases:
+    - /zh/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples/
+    - /zh-cn/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples/
+    - /zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples/
+linkTitle: 应用级服务发现迁移示例
+title: 应用级服务发现迁移示例
+tags: ["Java","服务发现"]
+date: 2024-05-13
+---
+
+
+
+
+
+
+应用级服务发现为应用间服务发现的协议,因此使用应用级服务发现需要消费端和服务端均升级到 Dubbo 3.0 版本并开启新特性(默认开启)才能在链路中使用应用级服务发现,真正发挥应用级服务发现的优点。
+## 开启方式
+### 服务端
+应用升级到 Dubbo 3.0 后,服务端自动开启接口级 + 应用级双注册功能,默认无需开发者修改任何配置
+
+### 消费端
+应用升级到 Dubbo 3.0 后,消费端自动始接口级 + 应用级双订阅功能,默认无需开发者修改任何配置。建议在服务端都升级到 Dubbo 3.0 并开启应用级注册以后通过规则配置消费端关闭接口级订阅,释放对应的内存空间。
+
+## 详细说明
+### 服务端配置
+
+1. 全局开关
+
+应用配置(可以通过配置文件或者 -D 指定)`dubbo.application.register-mode` 为 instance(只注册应用级)、all(接口级+应用级均注册)开启全局的注册开关,配置此开关后,默认会向所有的注册中心中注册应用级的地址,供消费端服务发现使用。
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider1/src/main/resources/application.yml)
+
+```
+# 双注册
+dubbo:
+    registry:
+        register-mode: all
+```
+```
+# 仅应用级注册
+dubbo:
+    registry:
+        register-mode: instance
+```
+
+2. 注册中心地址参数配置
+
+注册中心的地址上可以配置 `registry-type=service` 来显示指定该注册中心为应用级服务发现的注册中心,带上此配置的注册中心将只进行应用级服务发现。
+
+```xml
+<dubbo:registry address="nacos://${nacos.address:127.0.0.1}:8848?registry-type=service"/>
+```
+### 消费端订阅模式
+FORCE_INTERFACE:仅接口级订阅,行为和 Dubbo 2.7 及以前版本一致。
+APPLICATION_FIRST:接口级 + 应用级多订阅,如果应用级能订阅到地址就使用应用级的订阅,如果订阅不到地址则使用接口级的订阅,以此保证迁移过程中最大的兼容性。(注:由于存在同时进行订阅的行为,此模式下内存占用会有一定的增长,因此在所有服务端都升级到 Dubbo 3.0 以后建议迁移到 FORCE_APPLICATION 模式降低内存占用)
+FORCE_APPLICATION:仅应用级订阅,将只采用全新的服务发现模型。
+### 消费端配置
+
+1. 默认配置(不需要配置)
+
+升级到 Dubbo 3.0 后默认行为为接口级+应用级多订阅,如果应用级能订阅到地址就使用应用级的订阅,如果订阅不到地址则使用接口级的订阅,以此保证最大的兼容性。
+
+2. 订阅参数配置
+
+应用配置(可以通过配置文件或者 -D 指定)`dubbo.application.service-discovery.migration` 为 `APPLICATION_FIRST` 可以开启多订阅模式,配置为 `FORCE_APPLICATION` 可以强制为仅应用级订阅模式。
+具体接口订阅可以在 `ReferenceConfig` 中的 `parameters` 中配置 Key 为 `migration.step`,Value 为 `APPLICATION_FIRST` 或 `FORCE_APPLICATION` 的键值对来对单一订阅进行配置。
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
+
+```java
+System.setProperty("dubbo.application.service-discovery.migration", "APPLICATION_FIRST");
+```
+```java
+ReferenceConfig<DemoService> referenceConfig = new ReferenceConfig<>(applicationModel.newModule());
+referenceConfig.setInterface(DemoService.class);
+referenceConfig.setParameters(new HashMap<>());
+referenceConfig.getParameters().put("migration.step", mode);
+return referenceConfig.get();
+```
+
+3. 动态配置(优先级最高,可以在运行时修改配置)
+
+此配置需要基于配置中心进行推送,Key 为应用名 + `.migration` (如 `demo-application.migraion`),Group 为 `DUBBO_SERVICEDISCOVERY_MIGRATION`。规则体配置详见[接口级服务发现迁移至应用级服务发现指南](../migration-service-discovery/)。
+> [参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
+
+```java
+step: FORCE_INTERFACE
+```
diff --git a/content/zh-cn/blog/news/20230130-release.md b/content/zh-cn/blog/news/20230130-release.md
index d8a56fa3112..8d7114700b5 100644
--- a/content/zh-cn/blog/news/20230130-release.md
+++ b/content/zh-cn/blog/news/20230130-release.md
@@ -46,7 +46,7 @@ Dubbo 3.1.5 版本是目前 Dubbo 3 的最新稳定版本,我们建议所有
 
 ### FAQ
 
-本次发布中有 5 个提交涉及异常日志 FAQ 的完善。关于错误码机制请参考官网[错误码机制介绍](/zh-cn/overview/mannual/java-sdk/faq/intro/)一文。
+本次发布中有 5 个提交涉及异常日志 FAQ 的完善。关于错误码机制请参考官网[错误码机制介绍](/zh-cn/overview/java-sdk/reference-manual/faq/intro/)一文。
 
 ### 代码优化
 
diff --git a/content/zh-cn/blog/news/apache-33-release.md b/content/zh-cn/blog/news/apache-33-release.md
new file mode 100644
index 00000000000..901bddf0021
--- /dev/null
+++ b/content/zh-cn/blog/news/apache-33-release.md
@@ -0,0 +1,192 @@
+---
+title: "Apache Dubbo 3.3 全新发布:Triple X 领衔,开启微服务通信新时代"
+linkTitle: "Apache Dubbo 3.3 全新发布"
+date: 2024-09-11
+tags: ["新闻动态"]
+description: >
+  在 Apache Dubbo 突破 4w Star 之际,Apache Dubbo 团队正式宣布,Dubbo 3.3 正式发布!作为全球领先的开源微服务框架,Dubbo 一直致力于为开发者提供高性能、可扩展且灵活的分布式服务解决方案。此次发布的 Dubbo 3.3,通过 Triple X 的全新升级,突破了以往局限,实现了对南北向与东西向流量的全面支持,并提升了对云原生架构的友好性。
+---
+
+在 Apache Dubbo 突破 4w Star 之际,Apache Dubbo 团队正式宣布,Dubbo 3.3 正式发布!作为全球领先的开源微服务框架,Dubbo 一直致力于为开发者提供高性能、可扩展且灵活的分布式服务解决方案。此次发布的 Dubbo 3.3,通过 Triple X 的全新升级,突破了以往局限,实现了对南北向与东西向流量的全面支持,并提升了对云原生架构的友好性。
+
+## Dubbo 的基础介绍
+
+**Apache Dubbo** 是一个高性能、轻量级的微服务框架,最初由 Java 开发,但现在已扩展支持 **Go、Rust、Python** 等多种语言,为全球企业构建跨语言、跨平台的分布式系统提供了强有力的支持。Dubbo 提供了丰富的服务治理能力,包括服务注册与发现、负载均衡、容错机制和调用链追踪,帮助开发者构建高效、灵活的微服务架构。
+
+随着 Dubbo 逐渐演进,其通信性能、服务治理能力和跨语言兼容性得到了大幅提升,成为支持现代微服务架构的理想工具。
+
+## Triple X 全新升级背景
+
+在 Dubbo 的早期应用中,虽然其在数据中心内部的服务互通中展现了卓越的性能,但随着技术演进和应用场景的扩展,原有架构逐渐暴露出了一些瓶颈。这些瓶颈在跨区域、跨云的环境中尤为明显,尤其是在 Web 框架与 RPC 框架之间的频繁切换中,开发复杂性和系统性能都受到了影响。
+
+**传统架构的痛点主要体现在:**
+
+1.  **局限于数据中心内的应用场景**:在跨地域或跨云应用中,Dubbo 的传统架构缺乏对广域环境的原生支持,导致开发者需要在多种协议和框架中切换,增加了复杂性。
+
+2.  **南北向与东西向流量的双重挑战**:在现代微服务架构下,传统的 RPC 框架往往更侧重南北向流量优化,而服务间(东西向)通信的性能要求日益增加,对传统 Dubbo 架构提出了新的挑战。
+
+3.  **云原生与跨语言互操作性要求**:随着云原生技术的普及,系统需要对 HTTP 协议有更深层次的支持,并具备跨语言的通信能力,然而传统 Dubbo 在这一点上并未原生优化。
+
+
+**Triple X 的变革和突破:** Triple X 的诞生,直接回应了这些痛点,它不仅延续了 Dubbo 一贯的高性能通信能力,还实现了与 gRPC 协议的全面兼容,通过支持 HTTP/1、HTTP/2、HTTP/3 等协议,为跨云、跨区域的广泛应用场景提供了更具灵活性和高效性的解决方案。
+
+![image.png](/imgs/blog/33-release/ee5812e0-a90b-4a02-abab-b658cdddefc1.png)
+
+## Triple X 核心能力概述
+
+*   **全面支持南北向与东西向流量**:Triple X 无缝支持从客户端到服务器的南北向流量及服务间通信的东西向流量,并确保灵活转换,提升通信链路的整体效率。
+
+*   **遵循 gRPC 协议标准**:Triple X 遵循了 gRPC 协议标准,支持通过 Protobuf 进行通信,与 gRPC 服务无缝交互,扩展了 Dubbo 的跨语言、跨平台通信能力。
+
+*   **基于 HTTP 协议,原生支持云原生架构**:Triple X 构建于 HTTP/1、HTTP/2 和 HTTP/3 协议栈之上,全面优化了网络通信性能,并与现代云原生基础设施无缝集成,支持各种网关和服务网格。
+
+*   **高性能优化**:Triple X 提供了极致的性能提升,尤其在高并发和弱网环境下表现卓越,极大提高了系统吞吐量与响应速度。
+
+*   **平滑迁移与框架兼容**:支持从现有的 Spring Web 项目无缝迁移,开发者无需更改现有代码即可切换至 Triple X,提升性能,并保留对 Spring MVC 等框架的支持。
+
+*   **高扩展性**:Triple X 新引入 20+ SPI 扩展点,支持自定义核心行为,包括路由映射、参数解析、序列化及异常处理等。显著提升框架的灵活性和可定制性,使开发者能够根据特定业务需求和场景自定义行为,提高开发效率并降低定制化成本。
+
+
+## Triple X 使用场景
+
+**Triple X** 在 Dubbo 3.3 中为微服务架构提供了灵活的接入方式,能够适应不同场景下的系统需求。根据系统架构的不同,Triple X 提供了 **中心化接入方式** 和 **去中心化接入方式**,适用于多种应用场景。
+
+### 1. 中心化接入方式
+
+在 **中心化接入方式** 中,外部流量通过一个统一的服务网关进入 Dubbo 后端服务。网关负责处理 HTTP 流量的解析、转发,并将请求路由到合适的后端服务中。这种方式适用于对流量统一管理、流量控制、权限校验等有较高要求的系统,能够集中式地控制流量的进入点。
+
+![lQLPJxkYhOcUzFfNA3bNC0Sw5rRkqBkcwQ4GwaypwVc_AA_2884_886.png](/imgs/blog/33-release/78d6744b-928a-41d4-857c-ff91ad69c896.png)
+
+*   **使用场景**:当系统需要集中管理外部请求、对流量进行监控和限流等操作时,Triple X 能够通过服务网关处理 HTTP/1、HTTP/2 和 HTTP/3 的流量,并高效地转发给 Dubbo 服务进行处理。
+
+*   **优势**:集中化控制、易于管理,适合大规模系统中的统一流量治理。
+
+
+### 2. 去中心化接入方式
+
+在 **去中心化接入方式** 中,外部客户端可以直接通过 HTTP 协议访问后端 Dubbo 服务,而不需要依赖中间的网关层。这种方式适合对性能和低延迟有较高要求的系统,通过减少网关的转发,直接将流量路由到服务节点,从而降低通信开销,提升系统响应速度。网关节点的消除,能避免网关故障造成的系统不可用,简化部署架构,提升系统稳定性。
+
+![lQLPJw7B47rI7FfNAzjNCYiwStDS2ladC3oGwaypwZe9AA_2440_824.png](/imgs/blog/33-release/68b69954-9df2-48b2-bd63-fe07ba8cb25b.png)
+
+*   **使用场景**:当系统希望通过直接的 HTTP 流量接入 Dubbo 服务,减少中间环节,提高系统的响应速度时,Triple X 提供了直接暴露 REST API 的能力,无需借助网关即可完成服务导出。
+
+*   **优势**:去除中间环节,提升性能和响应速度,简化了架构,适合对低延迟有需求的应用场景。
+
+
+## Triple X 核心能力拆解说明
+
+### 1. 支持全面的流量管理与高效通信
+
+在复杂的微服务架构中,南北向流量(客户端到服务器)和东西向流量(服务间通信)需要采用不同的技术进行处理,系统往往面临性能瓶颈与复杂的开发和运维问题。
+
+Triple X 协议通过统一的通信协议,同时支持南北向与东西向流量。无需在 Web 框架与 RPC 框架之间切换,简化了开发流程,提升了系统的整体性能和可维护性。
+
+开发者可以通过 Triple X 实现全方位的流量支持,无论是用户发起的请求,还是服务间的通信,均可通过 Triple X 实现高效传输。
+
+```java
+package org.apache.test;
+
+@DubboService
+public class UserServiceImpl implements UserService {
+    // 处理东西向请求
+}
+
+// Triple X 也支持南北向流量处理
+@DubboService
+public class OrderService {
+    @GetMapping("/order/{orderId}")
+    public Order getOrderById(@PathVariable("orderId") String orderId) {}
+}
+```
+
+调用方式:
+
+1.  Dubbo Client 直接发起 RPC 调用
+
+2.  前端使用 HTTP 直接请求,目标路径为 `http://server:50051/order/{orderId}`
+
+3.  使用 Dubbo 默认发布的路径进行请求,目标路径为 `http://server:50051/org.apache.test.OrderService/getOrderById?orderId=xxx`
+
+
+### 2. 遵循 gRPC 协议标准
+
+跨语言服务之间的通信经常成为分布式系统中的难题,gRPC 是常用的解决方案之一,但传统 Dubbo 需要借助额外工具实现与 gRPC 的互操作性。
+
+Triple X 遵循 **gRPC 协议标准**,通过 Protobuf 实现与 gRPC 的无缝交互,简化了开发流程,增强了跨语言和跨平台通信能力。
+
+使用 Triple X 的服务可直接与基于 gRPC 的服务进行互通,无需额外适配,系统之间即可高效互访。
+
+### 3. 基于 HTTP 协议,原生支持云原生架构
+
+在云原生环境下,服务需要与各种网络设施(如 API 网关、服务网格)进行高效集成,同时支持多种 HTTP 协议以优化网络性能。
+
+Triple X 同时支持 **HTTP/1、HTTP/2 和 HTTP/3** 协议,开发者无需进行额外配置即可利用这些协议的优势,包括长连接、多路复用和头部压缩,从而实现高效的网络通信。使用 **HTTP/3** 还能彻底解决队头阻塞问题,同时基于 UDP 的通讯方式,在弱网下能够维持较高的连接质量和服务性能,同等环境 TCP 在高丢包率下可能已不可用。
+
+Triple X 支持复用 Spring Boot 现有 **Servlet** 端口接入 HTTP 流量,无需新增 Netty 监听端口。网络架构的简化,可以降低使用和维护成本,提升安全性,流量易于通过企业防火墙和网关。
+
+![image.png](/imgs/blog/33-release/0e6b75c3-3340-4bed-a566-88c46a03ada6.png)
+
+### 4. 高性能优化,提升 5 倍 QPS
+
+在高并发场景中,传统通信协议并未做深度优化,容易造成瓶颈,影响系统的整体响应时间和吞吐量。
+
+Triple X 通过 **Radix Tree** 和 **Zero Copy** 等技术降低了 CPU 使用和内存用量,显著提升了系统性能,尤其在高并发和弱网环境下表现突出:
+
+*   **高效路由**:采用 Radix Tree 前缀树结构进行路由匹配,优化 key hash 算法并支持动态更新,减少内存占用,提高匹配效率。
+
+*   **内存使用优化**:结合 Zero Copy 技术和对象复用技术,减少数据复制和对象创建开销,降低垃圾回收压力,提升吞吐量。
+
+*   **HTTP/3 支持**:引入基于 QUIC 的 HTTP/3 协议,显著提升弱网环境下的性能表现,解决队头阻塞问题,减少延迟并提高连接可靠性。
+
+*   **多协议压测优化**:Dubbo 团队对各种协议进行了全面压测,基于测试结果进行了多轮性能优化,确保在不同场景下都能达到最佳表现。
+
+
+经过压测,简单 Rest 服务相较于传统 Spring Boot REST 服务,Triple X 服务的平均响应时间降低至 1/3,高压力下 QPS 提升 5 倍,同时内存分配量减少 50%,显著提升了系统整体性能和资源利用效率。
+
+![image.png](/imgs/blog/33-release/c7d4f983-f619-4d39-94b6-5d62fd5a430e.png)
+
+![image.png](/imgs/blog/33-release/53a6f3c7-20ad-49f6-abc0-4e2d80a9597d.png)
+
+![image.png](/imgs/blog/33-release/7e4f3ced-9932-472f-bb8f-272ec97a7fbe.png)
+
+![image.png](/imgs/blog/33-release/5f8ebef5-08f3-463a-bb86-14b32a09ebb2.png)
+
+### 5. 平滑迁移与框架兼容
+
+此外,Triple X 还支持对于已有 Spring Web 的项目,在不大幅修改代码的前提下提升性能,向微服务架构迁移。
+
+Triple X 支持零侵入式的迁移方案,开发者无需更改现有代码即可将现有的 Spring Web 项目迁移至 Triple X,同时保留对 Spring MVC 等框架的支持。
+
+```java
+@DubboService    // 仅需添加服务发布配置
+@RestController
+public class DemoController {
+
+    @GetMapping("/spring-test")
+    public String sayHello(@RequestParam("name") String name) {
+        return "Hello " + name;
+    }
+}
+```
+
+## 此次版本升级其他的能力优化概述
+
+### 1. Native Image AOT 支持
+
+Dubbo 3.3 引入了对 **Native Image AOT(Ahead-of-Time 编译)** 的支持,开发者可以将 Dubbo 应用编译为原生二进制文件,极大缩短启动时间,降低内存占用,特别适合无服务器(Serverless)场景。
+
+### 2. Project Loom 支持
+
+Dubbo 3.3 提供了对 **Project Loom** 的支持,通过虚拟线程优化了高并发场景下的线程管理,简化了异步编程模型,提升了并发处理能力。
+
+### 3. 全新路由规则
+
+在路由机制上,Dubbo 3.3 引入了全新的路由规则,支持更加灵活的流量控制和服务治理,增强了微服务系统在大规模部署中的适应性。
+
+## 总结
+
+**Apache Dubbo 3.3** 的发布标志着微服务通信技术迈向新高度。通过 **Triple X**,Dubbo 不仅实现了对南北向与东西向流量的全面支持,还通过与 gRPC 的无缝集成、基于 HTTP 协议的云原生支持以及高性能优化,为开发者提供了更强大、灵活的工具,帮助他们构建现代分布式系统。
+
+无论是提升服务间通信的高效性、实现跨语言兼容,还是优化云原生环境下的通信性能,Dubbo 3.3 都是开发者应对现代分布式系统挑战的理想选择。立即升级至 Dubbo 3.3,体验 **Triple X** 带来的变革,开启微服务通信的新时代!
+
+更多升级指南和兼容性说明,请参考[Dubbo 3.2 升级 3.3 指南](/zh-cn/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/3.2-to-3.3-compatibility-guide/)。
diff --git a/content/zh-cn/blog/news/dubbo-initializer.md b/content/zh-cn/blog/news/dubbo-initializer.md
new file mode 100644
index 00000000000..3cb2c3b16dc
--- /dev/null
+++ b/content/zh-cn/blog/news/dubbo-initializer.md
@@ -0,0 +1,64 @@
+---
+aliases:
+    - /zh/overview/tasks/develop/template/
+    - /zh-cn/overview/tasks/develop/template/
+    - /zh-cn/overview/mannual/java-sdk/tasks/develop/template/
+title: "通过模板生成项目脚手架"
+linkTitle: "通过模板生成项目脚手架"
+date: 2023-12-31
+tags: ["新闻动态"]
+description: >
+  本文介绍 dubbo initializer 的基本使用,使用 start.dubbo.apache.org 快速生成 Dubbo 项目(应用)。
+---
+
+<a href="https://start.dubbo.apache.org/bootstrap.html" target="_blank">Dubbo Initializer</a> 可用来快速生成 Java 项目脚手架,帮助简化微服务项目搭建、基本配置、组件依赖管理等。
+
+> Initializer 仍在持续更新中,更多 Dubbo Feature 的支持将会陆续发布。
+
+## 选择 Dubbo 版本
+Initializer 将使用 `dubbo-spring-boot-starter` 创建 Spring Boot 项目,因此我们首先需要选择 Dubbo 与 Spring Boot 的版本。
+
+![initializer-choose-version](/imgs/v3/tasks/develop/initializer-choose-version.png)
+
+## 录入项目基本信息
+接下来,填入项目基本信息,包括项目坐标、项目名称、包名、JDK 版本等。
+
+![initializer-project-info](/imgs/v3/tasks/develop/initializer-project-info.png)
+
+## 选择项目结构
+有两种项目结构可共选择,分别是 `单模块` 和 `多模块`,在这个示例中我们选择 `单模块`。
+
+![initializer-project-architecture](/imgs/v3/tasks/develop/initializer-project-architecture.png)
+
+* 单模块,所有组件代码存放在一个 module 中,特点是结构简单。
+* 多模块,生成的项目有 `API`、`Service` 两个模块,其中 `API` 用于存放 Dubbo 服务定义,`Service` 用于存放服务实现或调用逻辑。通常多模块更有利于服务定义的单独管理与发布。
+
+## 选择依赖组件
+我们为模板默认选择如下几个依赖组件:
+* Dubbo 组件
+    * Java Interface
+    * 注册中心,zookeeper
+    * 协议 TCP
+* 常用微服务组件
+    * Web
+    * Mybatis
+    * 模版引擎
+
+![initializer-dependencies](/imgs/v3/tasks/develop/initializer-dependencies.png)
+
+基于以上选项,生成的项目将以 Zookeeper 为注册中心,以高性能 Dubbo2 TCP 协议为 RPC 通信协议,并且增加了 Web、Mybatis 等组件依赖和示例。
+
+> 注意:上面选中的 Dubbo 组件也都是默认选项,即在不手动添加任何依赖的情况下,打开页面后直接点击代码生成,生成的代码即包含以上 Dubbo 组件。
+>
+> 如手动添加依赖组件,请注意 Dubbo 各个依赖组件之间的隐含组合关系限制,比如
+> * 如果选择了【Dubbo Service API】-【IDL】,则目前仅支持选择 【Dubbo Protocol】中的 【HTTP/2】或 【gRPC】 协议。
+> * 同一个依赖分组下,相同类型的依赖只能选择一个,比如 【Dubbo Registry&Config&Metadata】分组下,从注册中心视角【Zookeeper】、【Nacos】只能选一个,如果要设置多注册中心,请在生成的代码中手动修改配置。但注册中心、配置中心可以分别选一个,比如 Zookeeper 和 Apollo 可同时选中。
+
+## 生成项目模板
+* 点击 “浏览代码” 可在线浏览项目结构与代码
+* 点击 “获取代码” 生成项目下载地址
+
+![initializer-preview](/imgs/v3/tasks/develop/initializer-preview.png)
+
+项目下载到本地后,解压并导入 IDE 后即可根据需要开发定制 Dubbo 应用。
+
diff --git a/content/zh-cn/blog/news/releases/3.1.4.md b/content/zh-cn/blog/news/releases/3.1.4.md
index 54f4401cadf..94164461c6f 100644
--- a/content/zh-cn/blog/news/releases/3.1.4.md
+++ b/content/zh-cn/blog/news/releases/3.1.4.md
@@ -38,7 +38,7 @@ Dubbo 3.1.4 版本是目前 Dubbo 3 的最新稳定版本,我们建议所有
 
 ### FAQ
 
-本次发布中有 3 个提交涉及异常日志 FAQ 的完善。关于错误码机制请参考官网错误码机制介绍一文。(https://cn.dubbo.apache.org/zh-cn/overview/mannual/java-sdk/faq/intro/)
+本次发布中有 3 个提交涉及异常日志 FAQ 的完善。关于错误码机制请参考官网错误码机制介绍一文。(https://cn.dubbo.apache.org/zh-cn/overview/java-sdk/reference-manual/faq/intro/)
 
 ### 代码优化
 
diff --git a/content/zh-cn/blog/nodejs/_index.md b/content/zh-cn/blog/nodejs/_index.md
new file mode 100644
index 00000000000..a19aad2ce1e
--- /dev/null
+++ b/content/zh-cn/blog/nodejs/_index.md
@@ -0,0 +1,9 @@
+
+---
+title: "Node.js"
+linkTitle: "Node.js"
+weight: 11
+description: "使用 Node.js 开发 Dubbo 应用与微服务"
+---
+
+
diff --git a/content/zh-cn/contact/_index.md b/content/zh-cn/contact/_index.md
index 60d309bc36c..d2cde263b28 100755
--- a/content/zh-cn/contact/_index.md
+++ b/content/zh-cn/contact/_index.md
@@ -4,9 +4,9 @@ aliases:
     - /zh/contribution-guidelines/
 description: 联系社区,Dubbo 社区贡献指南
 linkTitle: 联系社区
-menu:
-    main:
-        weight: 40
+# menu:
+#     main:
+#         weight: 40
 title: 联系社区
 type: docs
 ---
diff --git a/content/zh-cn/demo/_index.md b/content/zh-cn/demo/_index.md
new file mode 100755
index 00000000000..4249f2952dd
--- /dev/null
+++ b/content/zh-cn/demo/_index.md
@@ -0,0 +1,31 @@
+---
+title: "使用 Dubbo 开发的完整商城系统示例"
+linkTitle: "商城示例"
+---
+
+<section id="github" class="row td-cover-block td-cover-block--height-sm js-td-cover td-overlay  -bg-primary">
+</section>
+
+<div class="container l-container--padded">
+
+<div class="row">
+{{< page/toc collapsed=true placement="inline" >}}
+</div>
+
+<div class="row">
+<div class="col-12 col-lg-12">
+<p class="my-4">
+1. 示例提供了运行以下命令部署到本地Kubernetes集群:
+
+	```shell
+	kubectl apply -f xxx/kubernetes-manifests.yaml
+	```
+
+2. 示例提供了 Java 和 Go 语言实现,点击链接查看源码。
+</p>
+
+<img src="/imgs/demo/online-boutique-arch.png" style="max-width:1000px;height:auto;" >
+
+</div>
+</div>
+</div>
diff --git a/content/zh-cn/docs/advanced/service-container.md b/content/zh-cn/docs/advanced/service-container.md
index ca32fd694aa..864b2ebb35b 100644
--- a/content/zh-cn/docs/advanced/service-container.md
+++ b/content/zh-cn/docs/advanced/service-container.md
@@ -10,7 +10,7 @@ weight: 40
 
 
 
-{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。如果想要查看最新版本的文档,请参阅[最新版本](/zh-cn/overview/mannual/java-sdk/advanced-features-and-usage/others/service-container/)。
+{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。
 {{% /pageinfo %}}
 
 服务容器是一个 standalone 的启动程序,因为后台服务不需要 Tomcat 或 JBoss 等 Web 容器的功能,如果硬要用 Web 容器去加载服务提供方,增加复杂性,也浪费资源。
diff --git a/content/zh-cn/docs/advanced/static-service.md b/content/zh-cn/docs/advanced/static-service.md
index 73663d7b5e1..440d4229b71 100644
--- a/content/zh-cn/docs/advanced/static-service.md
+++ b/content/zh-cn/docs/advanced/static-service.md
@@ -10,7 +10,7 @@ weight: 11
 
 
 
-{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。如果想要查看最新版本的文档,请参阅[最新版本](/zh-cn/overview/mannual/java-sdk/reference-manual/registry/simple/)。
+{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。
 {{% /pageinfo %}}
 
 有时候希望人工管理服务提供者的上线和下线,此时需将注册中心标识为非动态管理模式。
diff --git a/content/zh-cn/docs/references/registry/simple.md b/content/zh-cn/docs/references/registry/simple.md
index a0bae65cd7e..2a01f468e7e 100644
--- a/content/zh-cn/docs/references/registry/simple.md
+++ b/content/zh-cn/docs/references/registry/simple.md
@@ -10,7 +10,7 @@ weight: 4
 
 
 
-{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。如果想要查看最新版本的文档,请参阅[最新版本](/zh-cn/overview/mannual/java-sdk/reference-manual/registry/simple/)。
+{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。
 {{% /pageinfo %}}
 
 Simple 注册中心本身就是一个普通的 Dubbo 服务,可以减少第三方依赖,使整体通讯方式一致。
diff --git a/content/zh-cn/download/_index.md b/content/zh-cn/download/_index.md
index 9a37f886781..f41f15cb3fc 100644
--- a/content/zh-cn/download/_index.md
+++ b/content/zh-cn/download/_index.md
@@ -3,10 +3,10 @@ aliases:
     - /zh/download/
 description: 版本发布
 layout: basic
-linkTitle: 版本发布
+linkTitle: 下载
 menu:
     main:
-        weight: 30
+        weight: 4
 no_list: true
 title: 版本发布
 type: docs
diff --git a/content/zh-cn/featured-background.jpg b/content/zh-cn/featured-background.jpg
index f6a02b9113e..d4bc6b77b85 100644
Binary files a/content/zh-cn/featured-background.jpg and b/content/zh-cn/featured-background.jpg differ
diff --git a/content/zh-cn/github/_index.md b/content/zh-cn/github/_index.md
index 3283ffe0d3d..7ad9af01227 100755
--- a/content/zh-cn/github/_index.md
+++ b/content/zh-cn/github/_index.md
@@ -1,10 +1,10 @@
 ---
 title: "Github"
 linkTitle: "Github"
-menu:
-  main:
-    post: <i class='fa-brands fa-github'></i>
-    weight: 70
+# menu:
+#   main:
+#     post: <i class='fa-brands fa-github'></i>
+#     weight: 70
 ---
 
 <section id="github" class="row td-cover-block td-cover-block--height-sm js-td-cover td-overlay  -bg-primary">
diff --git a/content/zh-cn/overview/core-features/_index.md b/content/zh-cn/overview/core-features/_index.md
deleted file mode 100755
index 04b79971c1a..00000000000
--- a/content/zh-cn/overview/core-features/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/
-description: Dubbo 核心特性
-linkTitle: 功能
-title: Dubbo 核心特性
-type: docs
-weight: 4
----
diff --git a/content/zh-cn/overview/core-features/ecosystem.md b/content/zh-cn/overview/core-features/ecosystem.md
deleted file mode 100644
index bbc0e7f8dbd..00000000000
--- a/content/zh-cn/overview/core-features/ecosystem.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-aliases:
-    - /zh-cn/overview/what/ecosystem/
-description: 微服务生态
-feature:
-    description: |
-        一站式微服务生态适配:注册中心、网关、限流降级、负载均衡、一致性事务、异步消息、Tracing 等。
-    title: 丰富生态
-linkTitle: 微服务生态
-title: 微服务生态
-type: docs
-weight: 10
----
-
-Dubbo 社区和众多优秀的开源项目一起围绕 Dubbo 建立了丰富的微服务生态支持,这让开发者从选型 Dubbo 作为开发框架的第一天,就无需担心后续的服务治理诉求,Dubbo 对每一个常见问题均提供了生产级的解决方案。
-
-以下表格为基于最新 Dubbo Java 3.2.x 版本统计的生态组件支持情况,后续将根据开发进展持续更新。同时每个语言支持的组件完善度会有一定差异,具体请参见各个 [语言参考手册](../../mannual/) 内的详细说明
-
-| 功能 | 组件列表 | 组件列表 | 组件列表 | 组件列表 | 组件列表 |
-| --- | --- | --- | --- | --- | --- |
-| 服务发现 | [Zookeeper](../../mannual/java-sdk/reference-manual/registry/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/registry/nacos) | [Kubernetes Service](/) | DNS【开发中】 | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-registry-extensions" target="_blank">更多</a> |
-| 动态配置 | [Zookeeper](../../mannual/java-sdk/reference-manual/config-center/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/config-center/nacos) | [Apollo](../../mannual/java-sdk/reference-manual/config-center/apollo) | Kubernetes【开发中】| <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-configcenter-extensions" target="_blank">更多</a> |
-| 元数据管理 | [Zookeeper](../../mannual/java-sdk/reference-manual/metadata-center/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/metadata-center/nacos)  | [Redis](../../mannual/java-sdk/reference-manual/metadata-center/redis)  | Kubernetes【开发中】 | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-metadata-report-extensions" target="_blank">更多</a> |
-| RPC 协议 | [HTTP/2 (Triple)](../../reference/protocols/triple) | [TCP](../../reference/protocols/tcp) | [HTTP/REST【Alpha】](../../reference/protocols/http) | [gRPC](../../reference/protocols/triple) | [更多](../../reference/protocols/) |
-| 可视化观测平台 | [Admin](../../tasks/observability/admin/) | [Grafana](../../tasks/observability/grafana/) | [Prometheus](../../tasks/observability/prometheus/) | - | - |
-| 全链路追踪 | [Zipkin](../../tasks/observability/tracing/zipkin/) | [Skywalking](../../tasks/observability/tracing/skywalking/) | <a href="https://github.com/apache/dubbo-samples/tree/master/4-governance/dubbo-samples-spring-boot3-tracing#2-adding-micrometer-tracing-bridge-to-your-project" target="_blank">OpenTelemetry</a> | - | - |
-| 限流降级 | [Sentinel](../../tasks/rate-limit/sentinel) | [Resilience4j](../../tasks/rate-limit/resilience4j) | [Hystrix](../../tasks/rate-limit/hystrix) | - | - |
-| 分布式事务 | [Seata](../../tasks/ecosystem/transaction/) | - | - | - | - |
-| 网关 | [Higress]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-higress" >}}) | [APISIX](../../tasks/ecosystem/gateway/) | [Shenyu]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-apache-shenyu" >}}) | [Envoy](https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/dubbo_proxy_filter) | - |
-| 服务网格 | Istio【开发中】 | <a href="https://www.aeraki.net/" target="_blank">Aeraka</a> | OpenSergo【开发中】 | Proxyless【Alpha】 | 更多 |
-
-
-## 微服务生态示例架构
-
-{{< mse >}}
-
-{{< blocks/section color="white" height="auto" >}}
-<div class="msemap-section">
- <div class="msemap-container">
-    <div id="mse-arc-container"></div>
-  </div>
-</div>
-{{< /blocks/section >}}
-
-
diff --git a/content/zh-cn/overview/core-features/extensibility.md b/content/zh-cn/overview/core-features/extensibility.md
deleted file mode 100644
index dd13e4cda21..00000000000
--- a/content/zh-cn/overview/core-features/extensibility.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/extensibility/
-description: 扩展适配
-feature:
-    description: |
-        一切皆可扩展,通过扩展 (Filter、Router、Service Discovery、Configuration 等) 自定义调用、管控行为,适配开源微服务生态。
-    title: 可扩展性
-linkTitle: 扩展适配
-title: 扩展适配
-type: docs
-weight: 6
----
-
-
-
-Dubbo 从设计上是高度可扩展的,通过这些扩展点你可以做到:
-* 拦截流量并控制流量行为
-* 按需调优 Dubbo 的一些默认策略与实现
-* 将 Dubbo 服务适配到公司内部微服务集群或其他主流的开源组件
-
-## 一切皆可扩展
-
-Dubbo 扩展能力使得 Dubbo 项目很方便的切分成一个一个的子模块,实现热插拔特性。用户完全可以基于自身需求,替换 Dubbo 原生实现,来满足自身业务需求。
-
-![Admin 效果图](/imgs/v3/advantages/extensibility.png)
-
-* **协议与编码扩展**。通信协议、序列化编码协议等
-* **流量管控扩展**。集群容错策略、路由规则、负载均衡、限流降级、熔断策略等
-* **服务治理扩展**。注册中心、配置中心、元数据中心、分布式事务、全链路追踪、监控系统等
-* **诊断与调优扩展**。流量统计、线程池策略、日志、QoS 运维命令、健康检查、配置加载等
-
-
-## 基于扩展点的微服务生态
-众多的扩展点与抽象,是 Dubbo 与众多微服务生态组件对接、实现微服务治理能力的基础。
-
-* [全链路追踪](../../tasks/observability/tracing/)
-* [数据一致性](../../tasks/ecosystem/transaction/)
-* [限流降级](../../core-features/traffic/circuit-breaking/)
-
-Dubbo 的各语言 sdk 实现都是采用的 "微内核+插件" 的设计模式,几乎所有流程中的核心节点都被定义为扩展点,官方发布的组件也是以扩展点的实现形式发布,因此 Dubbo 可以平等的对待所有官方与第三方组件扩展。
-* 扩展适配能力是实现 Dubbo 微服务生态的关键,Dubbo 生态组件如全链路追踪、注册中心实现等的适配都是基于 Filter、Registry、DynamicConfiguration 等扩展点实现。
-* 扩展适配给用户带来最大的灵活性,开发者可以随时接入公司内部组件、按需定制核心能力等。
-
-![extensibility-echosystem.png](/imgs/v3/feature/extensibility/arc.png)
-
-以上是按架构层次划分的 Dubbo 内的一些核心扩展点定义及实现,从三个层次来展开:
-* 协议通信层
-* 流量管控层
-* 服务治理层
-
-## 协议通信层
-在通信协议一节我们强调过,Dubbo 不绑定任何协议,用户可以选择 Triple、gRPC、Dubbo2、REST、自定义协议等任一 RPC 远程通信协议,除此之外,RPC 协议之上的数据编码格式 (即序列化协议) 也是通过扩展点定义,用户可以灵活选择 RPC 与序列化的通信协议组合。
-
-![协议与编码原理图](/imgs/v3/feature/extensibility/protocol.png)
-
-### Protocol
-Protocol 扩展点定义对应的是 RPC 协议,利用这个扩展点可以让 Dubbo 作为统一的微服务开发和治理框架,而在下层通信协议上实现灵活切换。官方发布了对大多数主流 RPC 通信协议的适配,你可以通过几条简单的配置直接使用,如果你想使用公司自定义的 RPC 通信协议,请通过 Protocol 提供自定义扩展实现。
-
-### Serialization
-Serialization 扩展点定义了序列化协议扩展,Dubbo 官方提供了 Fastjson、Protobuf、Hessian2、Kryo、FST 等序列化协议适配。
-
-## 流量管控层
-Dubbo 在服务调用链路上预置了大量扩展点,通过这些扩展点用户可以控制运行态的流量走向、改变运行时调用行为等,包括 Dubbo 内置的一些负载均衡策略、流量路由策略、超时等很多流量管控能力都是通过这类扩展点实现的。
-
-![协议与编码原理图](/imgs/v3/feature/extensibility/traffic.png)
-
-### Filter
-Filter 流量拦截器是 Dubbo 服务调用之上的 AOP 设计模式,Filter 用来对每次服务调用做一些预处理、后处理动作,使用 Filter 可以完成访问日志、加解密、流量统计、参数验证等任务,Dubbo 中的很多生态适配如限流降级 Sentinel、全链路追踪 Tracing 等都是通过 Fitler 扩展实现的。一次请求过程中可以植入多个 Filter,Filter 之间相互独立没有依赖。
-* 从消费端视角,它在请求发起前基于请求参数等做一些预处理工作,在接收到响应后,对响应结果做一些后置处理;
-* 从提供者视角则,在接收到访问请求后,在返回响应结果前做一些预处理,
-
-### Router
-Router 路由器是 Dubbo 中流量管控的关键组件,它将符合一定条件的流量转发到特定分组的地址子集,是 Dubbo 流量管控中一些关键能力如按比例流量转发、流量隔离等的基础。每次服务调用请求都会流经一组路由器 (路由链),每个路由器根据预先设定好的规则、全量地址列表以及当前请求上下文计算出一个地址子集,再传给下一个路由器,重复这一过程直到最后得出一个有效的地址子集。
-
-Dubbo 官方发布版本预置了丰富的流量管控规则与 router 实现,如 [流量管控](../traffic/) 一文中阐述的,用户通过下发规则即可实现各种模式的流量管控。如果有其他流量管控诉求,可以通过提供自定义的 router 扩展实现。
-
-### Load Balance
-在 Dubbo 中,Load Balance 负载均衡工作在 router 之后,对于每次服务调用,负载均衡负责在 router 链输出的地址子集中选择一台机器实例进行访问,保证一段时间内的调用都均匀的分布在地址子集的所有机器上。
-
-Dubbo 官方提供了加权随机、加权轮询、一致性哈希、最小活跃度优先、最短响应时间优先等负载均衡策略,还提供了根据集群负载自适应调度的负载均衡算法。
-
-## 服务治理层
-以下是 Dubbo 部署的经典架构图,由注册中心 (服务发现)、配置中心和元数据中心构成了整个服务治理的核心。
-
-![服务治理架构图](/imgs/v3/concepts/threecenters.png)
-
-这里我们主要从架构、实现的视角来分析了 Dubbo 服务治理,Dubbo 很多服务治理的核心能力都是通过上图描述的几个关键组件实现的,用户通过控制面或者 Admin 下发的各种规则与配置、各类微服务集群状态的展示等都是直接与注册中心、配置中心和元数据中心交互。
-
-在具体实现或者部署上,注册中心、配置中心和元数据中心可以是同一组件,比如 Zookeeper 可同时作为注册、配置和元数据中心,Nacos 也是如此。因此,三个中心只是从架构职责上的划分,你甚至可以用同一个 Zookeeper 集群来承担所有三个职责,只需要在应用里将他们设置为同一个集群地址就可以了。
-
-> 在云原生部署架构下,随着 Kubernetes、Service Mesh 架构的流行,微服务基础设施呈现下沉趋势,注册、配置和元数据中心的职责正被 Kubernetes、Istio 等组件取代,具体可参见 [服务网格](../service-mesh/) 一节的描述。
-
-### Registry
-注册中心是 Dubbo 实现服务发现能力的基础,Dubbo 官方支持 Zookeeper、Nacos、Etcd、Consul、Eureka 等注册中心。
-
-通过对 Consul、Eureka 的支持,Dubbo 也实现了与 Spring Cloud 体系在地址和通信层面的互通,让用户同时部署 Dubbo 与 Spring Cloud,或者从 Spring Cloud 迁移到 Dubbo 变得更容易。
-
-### Config Center
-配置中心是用户实现动态控制 Dubbo 行为的关键组件,我们在 [流量管控](../../tasks/traffic-management) 任务中下发的所有规则,都是先下发到配置中心保存起来,进而 Dubbo 实例通过监听配置中心的变化,收到路由规则并达到控制流量的行为。
-
-Dubbo 官方支持 Zookeeper、Nacos、Etcd、Redis、Apollo 等配置中心实现。
-
-### Metadata Center
-与配置中心相反,从用户视角来看元数据中心是只读的,元数据中心唯一的写入方是 Dubbo 进程实例,Dubbo 实例会在启动之后将一些内部状态(如服务列表、服务配置、服务定义格式等)上报到元数据中心,供一些治理能力作为数据来源,如服务测试、文档管理、服务状态展示等。
-
-Dubbo 官方支持 Zookeeper、Nacos、Etcd、Redis 等元数据中心实现。
-
-## 自定义扩展示例
-
-以下示例演示了如何扩展 Dubbo 来解决实际问题,可以跟随示例学习。
-
-* [自定义 RPC 协议](../../tasks/extensibility/protocol/)
-* [自定义流量路由规则](../../tasks/extensibility/router/)
-* [自定义注册中心](../../tasks/extensibility/registry/)
-* [自定义拦截器](../../tasks/extensibility/filter/)
-
-## 更多扩展点
-本文列出了 Dubbo 常用的一些扩展点,但还有大量的扩展点可供灵活定制,并且不同语言 sdk 的扩展定义和配置方式上也存在差异,以下是 Dubbo SDK 的扩展点手册。
-
-* [Java 扩展点手册](../../mannual/java-sdk/reference-manual/spi/description/)
-* [Go 扩展点手册](../../mannual/golang-sdk/preface/design/aop_and_extension/)
diff --git a/content/zh-cn/overview/core-features/load-balance.md b/content/zh-cn/overview/core-features/load-balance.md
deleted file mode 100644
index 5392d2eb5aa..00000000000
--- a/content/zh-cn/overview/core-features/load-balance.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/load-balance/
-description: 负载均衡
-linkTitle: 负载均衡
-title: 负载均衡
-type: docs
-weight: 3
----
-
-
-
-在集群负载均衡时,Dubbo 提供了多种均衡策略,缺省为 `weighted random` 基于权重的随机负载均衡策略。
-
-具体实现上,Dubbo 提供的是客户端负载均衡,即由 Consumer 通过负载均衡算法得出需要将请求提交到哪个 Provider 实例。
-
-## 负载均衡策略
-目前 Dubbo 内置了如下负载均衡算法,可通过调整配置项启用。
-
-| 算法                        | 特性                    | 备注                                            |
-| :-------------------------- | :---------------------- | :---------------------------------------------- |
-| Weighted Random LoadBalance           | 加权随机                | 默认算法,默认权重相同              |
-| RoundRobin LoadBalance       | 加权轮询                | 借鉴于 Nginx 的平滑加权轮询算法,默认权重相同, |
-| LeastActive LoadBalance      | 最少活跃优先 + 加权随机 | 背后是能者多劳的思想                           |
-| Shortest-Response LoadBalance | 最短响应优先 + 加权随机 | 更加关注响应速度                             |
-| ConsistentHash LoadBalance   | 一致性哈希             | 确定的入参,确定的提供者,适用于有状态请求        |
-| P2C LoadBalance   | Power of Two Choice    | 随机选择两个节点后,继续选择“连接数”较小的那个节点。         |
-| Adaptive LoadBalance   | 自适应负载均衡       | 在 P2C 算法基础上,选择二者中 load 最小的那个节点         |
-
-### Weighted Random
-
-* **加权随机**,按权重设置随机概率。
-* 在一个截面上碰撞的概率高,但调用量越大分布越均匀,而且按概率使用权重后也比较均匀,有利于动态调整提供者权重。
-* 缺点:存在慢的提供者累积请求的问题,比如:第二台机器很慢,但没挂,当请求调到第二台时就卡在那,久而久之,所有请求都卡在调到第二台上。
-
-### RoundRobin
-* **加权轮询**,按公约后的权重设置轮询比率,循环调用节点
-* 缺点:同样存在慢的提供者累积请求的问题。
-
-加权轮询过程中,如果某节点权重过大,会存在某段时间内调用过于集中的问题。
-例如 ABC 三节点有如下权重:`{A: 3, B: 2, C: 1}`
-那么按照最原始的轮询算法,调用过程将变成:`A A A B B C`
-
-对此,Dubbo 借鉴 Nginx 的平滑加权轮询算法,对此做了优化,调用过程可抽象成下表:
-
-| 轮前加和权重        | 本轮胜者 | 合计权重 | 轮后权重(胜者减去合计权重) |
-| :------------------ | :------- | :------- | :--------------------------- |
-| 起始轮              | \        | \        | `A(0), B(0), C(0)`           |
-| `A(3), B(2), C(1)`  | A        | 6        | `A(-3), B(2), C(1)`          |
-| `A(0), B(4), C(2)`  | B        | 6        | `A(0), B(-2), C(2)`          |
-| `A(3), B(0), C(3)`  | A        | 6        | `A(-3), B(0), C(3)`          |
-| `A(0), B(2), C(4)`  | C        | 6        | `A(0), B(2), C(-2)`          |
-| `A(3), B(4), C(-1)` | B        | 6        | `A(3), B(-2), C(-1)`         |
-| `A(6), B(0), C(0)`  | A        | 6        | `A(0), B(0), C(0)`           |
-
-我们发现经过合计权重(3+2+1)轮次后,循环又回到了起点,整个过程中节点流量是平滑的,且哪怕在很短的时间周期内,概率都是按期望分布的。
-
-如果用户有加权轮询的需求,可放心使用该算法。
-
-### LeastActive
-* **加权最少活跃调用优先**,活跃数越低,越优先调用,相同活跃数的进行加权随机。活跃数指调用前后计数差(针对特定提供者:请求发送数 - 响应返回数),表示特定提供者的任务堆积量,活跃数越低,代表该提供者处理能力越强。
-* 使慢的提供者收到更少请求,因为越慢的提供者的调用前后计数差会越大;相对的,处理能力越强的节点,处理更多的请求。
-
-### ShortestResponse
-* **加权最短响应优先**,在最近一个滑动窗口中,响应时间越短,越优先调用。相同响应时间的进行加权随机。
-* 使得响应时间越快的提供者,处理更多的请求。
-* 缺点:可能会造成流量过于集中于高性能节点的问题。
-
-这里的响应时间 = 某个提供者在窗口时间内的平均响应时间,窗口时间默认是 30s。
-
-
-### ConsistentHash
-* **一致性 Hash**,相同参数的请求总是发到同一提供者。
-* 当某一台提供者挂时,原本发往该提供者的请求,基于虚拟节点,平摊到其它提供者,不会引起剧烈变动。
-* 算法参见:[Consistent Hashing | WIKIPEDIA](http://en.wikipedia.org/wiki/Consistent_hashing)
-* 缺省只对第一个参数 Hash,如果要修改,请配置 `<dubbo:parameter key="hash.arguments" value="0,1" />`
-* 缺省用 160 份虚拟节点,如果要修改,请配置 `<dubbo:parameter key="hash.nodes" value="320" />`
-
-### P2C Load Balance
-Power of Two Choice 算法简单但是经典,主要思路如下:
-
-1. 对于每次调用,从可用的provider列表中做两次随机选择,选出两个节点providerA和providerB。
-2. 比较providerA和providerB两个节点,选择其“当前正在处理的连接数”较小的那个节点。
-
-以下是 [Dubbo P2C 算法实现提案](../../reference/proposals/heuristic-flow-control/#p2c算法)
-
-### Adaptive Load Balance
-Adaptive 即自适应负载均衡,是一种能根据后端实例负载自动调整流量分布的算法实现,它总是尝试将请求转发到负载最小的节点。
-
-以下是 [Dubbo Adaptive 算法实现提案](../../reference/proposals/heuristic-flow-control/#adaptive算法)
-
-## 配置方式
-Dubbo 支持在服务提供者一侧配置默认的负载均衡策略,这样所有的消费者都将默认使用提供者指定的负载均衡策略,消费者可以自己配置要使用的负载均衡策略,如果都没有任何配置,
-则默认使用随机负载均衡策略。
-
-同一个应用内支持配置不同的服务使用不同的负载均衡策略,支持为同一服务的不同方法配置不同的负载均衡策略。
-
-具体配置方式参加以下多语言实现
-
-* [Java](../../mannual/java-sdk/advanced-features-and-usage/performance/loadbalance/#使用方式)
-* [Golang](../../mannual/golang-sdk/)
-
-## 自定义扩展
-负载均衡策略支持自定义扩展实现,具体请参见 [Dubbo 可扩展性](../extensibility)
diff --git a/content/zh-cn/overview/core-features/more.md b/content/zh-cn/overview/core-features/more.md
deleted file mode 100644
index b1bb6cfc01f..00000000000
--- a/content/zh-cn/overview/core-features/more.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/more/
-description: 高级功能指南
-linkTitle: 更多高级功能
-title: 更多高级功能
-type: docs
-weight: 11
----
-
-
-作为一款与应用开发紧密相关的微服务框架,同时旨在为微服务集群提供企业级服务治理能力,Dubbo 还提供了很多高级功能,涵盖服务调用行为控制、服务诊断与调优、服务治理等。
-
-多种语言 sdk 在功能实现、配置方式上会略有差异,具体功能列表和使用方式可参考如下文档:
-* [Java](../../mannual/java-sdk/advanced-features-and-usage/)
-* [Golang](../../mannual/golang-sdk/tutorial/)
-
-## 控制服务调用行为
-* 服务版本
-* 服务分组
-* 分组聚合
-* 异步调用
-* 异步执行
-* 流式通信
-* 响应式编程
-* 泛化调用
-* 泛化实现
-* 调用链路传递隐式参数
-* RPC调用上下文
-* 调用触发事件通知
-* 服务端对客户端进行回调
-* 只订阅
-* 只注册
-* 运行时动态指定 IP 调用
-* 直连提供者
-* 启动时检查
-* 本地调用
-* 参数校验
-* 本地伪装
-* 本地存根
-* 回声测试
-* 调用信息记录
-* 延迟暴露
-* 集群容错
-* 服务降级
-
-## 诊断与调优
-* 端口协议复用
-* 线程池隔离
-* 多协议
-* 多注册中心
-* 请求耗时采样
-* 线程模型
-* 服务引用配置对象缓存
-* 路由状态采集
-* 负载均衡
-* 注册信息简化
-* 调用结果缓存
-* 并发控制
-* 连接控制
-* 延迟连接
-* 粘滞连接
-* 支持 Graal VM
-* 导出线程堆栈
-* Kryo 和 FST 序列化
-* 自定义服务容器
-* 优雅停机
-* 主机地址自定义暴露
-* 一致性哈希选址
-* 日志框架适配及运行时管理
-* Kubernetes 生命周期探针
diff --git a/content/zh-cn/overview/core-features/observability.md b/content/zh-cn/overview/core-features/observability.md
deleted file mode 100644
index c61cfe430ca..00000000000
--- a/content/zh-cn/overview/core-features/observability.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/observability/
-description: 观测服务
-feature:
-    description: |
-        多维度的可观测指标(Metrics、Tracing、Accesslog)帮助了解服务运行状态,Admin 控制台、Grafana 等帮助实现数据指标可视化展示。
-    title: 可观测性
-linkTitle: 观测服务
-title: 观测服务
-type: docs
-weight: 7
----
-
-
-
-Dubbo 内部维护了多个纬度的可观测指标,并且支持多种方式的可视化监测。可观测性指标从总体上来说分为三个度量纬度:
-
-* **Admin** Admin 控制台可视化展示了集群中的应用、服务、实例及依赖关系,支持流量治理规则下发,同时还提供如服务测试、mock、文档管理等提升研发测试效率的工具。
-
-* **Metrics** Dubbo 统计了一系列的流量指标如 QPS、RT、成功请求数、失败请求数等,还包括一系列的内部组件状态如线程池数、服务健康状态等。
-
-* **Tracing** Dubbo 与业界主流的链路追踪工作做了适配,包括 Skywalking、Zipkin、Jaeger 都支持 Dubbo 服务的链路追踪。
-
-* **Logging** Dubbo 支持多种日志框架适配。以 Java 体系为例,支持包括 Slf4j、Log4j2、Log4j、Logback、Jcl 等,用户可以基于业务需要选择合适的框架;同时 Dubbo 还支持 Access Log 记录请求踪迹。
-
-## Admin
-Admin 控制台可视化展示了集群中的应用、服务、实例及依赖关系,支持流量治理规则下发,同时还提供如服务测试、mock、文档管理等提升研发测试效率的工具
-
-![Admin 效果图](/imgs/v3/feature/observability/admin.jpg)
-
-* [Admin 部署与效果演示](../../tasks/observability/admin/)
-
-## Metrics
-Dubbo 运行时统计了包括 qps、rt、调用总数、成功数、失败数,失败原因统计等在内的核心服务指标,同时,为了更好的监测服务运行状态,Dubbo 还提供了对核心组件状态的监控,如线程池数量、服务健康状态等。
-
-可以通过 Grafana 可视化的查看 Metrics 指标
-
-![Grafana 效果图](/imgs/v3/feature/observability/provider-stat.png)
-
-* [使用 Grafana 可视化展示 Metrics 指标](../../tasks/observability/grafana/)
-* [如何从 Prometheus 查询特定 Metrics 指标](../../tasks/observability/prometheus/)
-
-## Tracing
-全链路追踪对于监测分布式系统运行状态具有非常重要的价值,Dubbo 通过 Filter 拦截器实现了请求运行时的埋点跟踪,通过将跟踪数据导出到一些主流实现如 Zipkin、Skywalking、Jaeger 等,可以实现全链路跟踪数据的分析与可视化展示。
-
-![Tracing 效果图](/imgs/v3/feature/observability/tracing.png)
-
-> 未来我们计划支持通过 Dubbo Admin 等治理平台动态调整 Dubbo 的链路追踪采样率。
-
-* [基于 Skywalking 实现全链路追踪](../../tasks/observability/tracing/skywalking/)
-* [基于 Zipkin 实现全链路追踪](../../tasks/observability/tracing/zipkin/)
-* [通过链路追踪关联日志系统](../../mannual/java-sdk/advanced-features-and-usage/observability/tracing#关联日志)
-
-## Logging
-访问日志可以帮助分析系统的流量情况,在有些场景下,开启访问日志对于排查问题也非常有帮助。
-
-* [开启 Access Log](../../mannual/java-sdk/advanced-features-and-usage/service/accesslog/)
-* [你还在运行态开启 Access Log](../../tasks/traffic-management/accesslog/)
diff --git a/content/zh-cn/overview/core-features/protocols.md b/content/zh-cn/overview/core-features/protocols.md
deleted file mode 100644
index 2e8384612c1..00000000000
--- a/content/zh-cn/overview/core-features/protocols.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/protocols/
-description: 通信协议
-feature:
-    description: |
-        支持 HTTP/2、gRPC、TCP、REST 等任意通信协议,切换协议只需要修改一行配置,支持单个端口上的多协议发布。
-    title: 通信协议
-linkTitle: 通信协议
-title: 通信协议
-type: docs
-weight: 5
----
-
-Dubbo 框架提供了自定义的高性能 RPC 通信协议:基于 HTTP/2 的 Triple 协议 和 基于 TCP 的 Dubbo2 协议。除此之外,Dubbo 框架支持任意第三方通信协议,如官方支持的 gRPC、Thrift、REST、JsonRPC、Hessian2 等,更多协议可以通过自定义扩展实现。这对于微服务实践中经常要处理的多协议通信场景非常有用。
-
-**Dubbo 框架不绑定任何通信协议,在实现上 Dubbo 对多协议的支持也非常灵活,它可以让你在一个应用内发布多个使用不同协议的服务,并且支持用同一个 port 端口对外发布所有协议。**
-
-![protocols](/imgs/v3/feature/protocols/protocol1.png)
-
-通过 Dubbo 框架的多协议支持,你可以做到:
-* 将任意通信协议无缝地接入 Dubbo 服务治理体系。Dubbo 体系下的所有通信协议,都可以享受到 Dubbo 的编程模型、服务发现、流量管控等优势。比如 gRPC over Dubbo 的模式,服务治理、编程 API 都能够零成本接入 Dubbo 体系。
-* 兼容不同技术栈,业务系统混合使用不同的服务框架、RPC 框架。比如有些服务使用 gRPC 或者 Spring Cloud 开发,有些服务使用 Dubbo 框架开发,通过 Dubbo 的多协议支持可以很好的实现互通。
-* 让协议迁移变的更简单。通过多协议、注册中心的协调,可以快速满足公司内协议迁移的需求。比如如从自研协议升级到 Dubbo 协议,Dubbo 协议自身升级,从 Dubbo 协议迁移到 gRPC,从 HTTP 迁移到 Dubbo 协议等。
-
-## HTTP/2 (Triple)
-Triple 协议是 Dubbo3 发布的面向云原生时代的通信协议,它基于 HTTP/2 并且完全兼容 gRPC 协议,原生支持 Streaming 通信语义,Triple 可同时运行在 HTTP/1 和 HTTP/2 传输协议之上,让你可以直接使用 curl、浏览器访问后端 Dubbo 服务。
-
-自 Triple 协议开始,Dubbo 还支持基于 Protocol Buffers 的服务定义与数据传输,但 Triple 实现并不绑定 IDL,比如你可以直接使用 Java Interface 定义和发布 Triple 服务。Triple 具备更好的网关、代理穿透性,因此非常适合于跨网关、代理通信的部署架构,如服务网格等。
-
-Triple 协议的核心特性如下:
-* 支持 TLS 加密、Plaintext 明文数据传输
-* 支持反压与限流
-* 支持 Streaming 流式通信
-* 同时支持 HTTP/1 和 HTTP/2 传输协议
-
-在编程与通信模型上,Triple 协议支持如下模式:
-* 消费端异步请求(Client Side Asynchronous Request-Response)
-* 提供端异步执行(Server Side Asynchronous Request-Response)
-* 消费端请求流(Request Streaming)
-* 提供端响应流(Response Streaming)
-* 双向流式通信(Bidirectional Streaming)
-
-开发实践
-* Triple 协议使用请参见 [Triple 协议开发任务](../../tasks/protocols/triple/) 或 [java sdk 示例文档](../../mannual/java-sdk/reference-manual/protocol/triple/)
-* [Triple 设计思路与协议规范](../../reference/protocols/triple/)
-
-## Dubbo2
-Dubbo2 协议是基于 TCP 传输层协议之上构建的一套 RPC 通信协议,由于其紧凑、灵活、高性能的特点,在 Dubbo2 时代取得了非常广泛的应用,是企业构建高性能、大规模微服务集群的关键通信方案。在云原生时代,我们更推荐使用通用性、穿透性更好的 Triple 协议。
-
-Dubbo2 协议也内置 HTTP 支持,因此你可以使用 curl 在开发阶段快速验证或调试服务。
-
-* [Dubbo2 协议开发任务](../../tasks/protocols/dubbo/)
-* [Dubbo2 设计思路与协议规范](../../reference/protocols/tcp/)
-
-## gRPC
-你可以用 Dubbo 开发和治理微服务,然后设置使用 gRPC 协议进行底层通信。但为什么要这么做呢,与直接使用 gRPC 框架对比有什么优势?简单的答案是,这是使用 gRPC 进行微服务开发的常用模式,具体请往下看。
-
-gRPC 是谷歌开源的基于 HTTP/2 的通信协议,如同我们在 [产品对比](../../what/xyz-difference) 文档中提到的,gRPC 的定位是通信协议与实现,是一款纯粹的 RPC 框架,而 Dubbo 定位是一款微服务框架,为微服务实践提供解决方案。因此,相比于 Dubbo,gRPC 相对欠缺了微服务编程模型、服务治理等能力的抽象。
-
-在 Dubbo 体系下使用 gRPC 协议 (gRPC over Dubbo Framework) 是一个非常高效和轻量的选择,它让你既能使用原生的 gRPC 协议通信,又避免了基于 gRPC 进行二次定制与开发的复杂度 (二次开发与定制 gRPC,是很多企业规模化实践后证实不可避免的环节,Dubbo 框架替开发者完成了这一步,让开发者可以直接以最简单的方式使用 gRPC)。
-
-[gRPC over Dubbo 示例](../../tasks/protocols/grpc/)
-
-## REST
-微服务领域常用的一种通信模式是 HTTP + JSON,包括 Spring Cloud、Microprofile 等一些主流的微服务框架都默认使用的这种通信模式,Dubbo 同样提供了对基于 HTTP 的编程、通信模式的支持。
-
-* [HTTP over Dubbo 示例](../../tasks/protocols/web/)
-* [Dubbo 与 Spring Cloud 体系互通](../../tasks/protocols/springcloud/)
-
-## 其他通信协议
-除了以上介绍的几种协议之外,你还可以将以下协议运行在 Dubbo 之上。对 Dubbo 而言,只需要修改一行简单的配置,就可以切换底层服务的通信协议,其他外围 API 和治理能力不受影响。
-* Hessian2
-* Thrift
-* JsonRPC
-
-## 异构微服务体系互通
-关于协议迁移、多协议技术栈共存的实践方案,请参考本篇[博客文章](/zh-cn/blog/2023/01/05/dubbo-连接异构微服务体系-多协议多注册中心/)。
-
-## 配置方式
-以上协议的配置和使用方式,包括如何配置 `单端口多协议` 支持等,请参照以下 sdk 示例文档:
-
-* [Java](../../mannual/java-sdk/reference-manual/protocol/)
-* [Golang](../../mannual/golang-sdk/tutorial/develop/protocol/)
-* [Rust](../../mannual/rust-sdk/)
-
-## 自定义扩展
-除了以上官方版本支持的通信协议,Dubbo 支持扩展新协议支持,具体请参见 [【任务】-【可扩展性】-【protocol】](../../tasks/extensibility/protocol/)
diff --git a/content/zh-cn/overview/core-features/security.md b/content/zh-cn/overview/core-features/security.md
deleted file mode 100644
index dbc8052372e..00000000000
--- a/content/zh-cn/overview/core-features/security.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/security/
-description: 认证鉴权
-feature:
-    description: |
-        支持基于 TLS 的传输链路认证与加密通信以及基于请求身份的权限校验,帮助构建零信任分布式微服务体系。
-    title: 认证鉴权
-linkTitle: 认证鉴权
-title: 认证鉴权
-type: docs
-weight: 8
----
-
-Dubbo 提供了构建安全微服务通信体系 (零信任体系) 的完善机制,这包括:
-* 避免通信过程中的中间人攻击,Dubbo 提供了身份认证 (Authentication) 和基于 TLS 的通信链路加密能力
-* 控制服务间的访问鉴权 (Authorization),Dubbo 提供了 mTLS 和权限检查机制
-
-通过这篇文档,你将了解如果使用 Dubbo 的安全机制构建微服务零信任体系,实现身份认证、透明链路加密、鉴权、审计等能力。由于构建零信任是一套系统的工作,而 Dubbo 只是其中数据通信层的一环,因此你可能需要一系列基础设施的配合,包括证书生成、分发、安全策略管控等。
-
-> **证书的生成和分发不在本文讨论范围,我们假设您已经有完善的基础设施解决了证书管理问题,因此,我们将更专注在讲解 Dubbo 体系的认证和鉴权机制与流程。** 如果您并没有这些证书管理设施,我们推荐您使用服务网格架构 (具体请参见 [Dubbo Mesh 服务网格](../service-mesh/) 文档说明),借助 [Istio](https://istio.io/latest/docs/concepts/security/) 等服务网格控制面的证书管理机制和安全策略,您可以很容易将 Dubbo 集群的认证和鉴权能力实施起来。
-
-> 另外,以下默认讲的都是 Dubbo Proxyless Mesh 模式下的 Dubbo 数据面行为,对于部署 Envoy 的场景,由于 Dubbo 只是作为通信和编程 sdk,因此 Envoy 场景下认证鉴权能力请完全参考标准 Istio 文档即可。
-
-## 架构
-
-一套完整的零信任体系包含多个组成部分:
-
-* 一个根证书机构 (CA) 来负责管理 key 和 certificate
-* 一个安全策略的管理和分发中心,来负责将安全策略实时下发给数据面组件:
-    * 认证策略
-    * 鉴权策略
-    * 安全命名信息 (Secure Naming Information)
-* 数据面组件 (Dubbo) 负责识别和执行身份认证、加密、策略解析等动作
-* 一系列的工具和生态,配合完成安全审计、数据链路监控等工作
-
-在服务网格 (Istio) 部署模式下,控制面通常负责安全策略、证书等的管理,控制面负责与基础设施如 Kubernetes API Server 等交互,将配置数据下发给 Dubbo 或者 Envoy 等数据面组件。但如我们前面提到的,我们假设控制面产品已经就绪,因此不会涉及控制面如何签发证书、定义认证鉴权策略的讨论,我们将专注在 Dubbo 作为数据面的职责及与控制面的交互流程上。
-
-以下是完整的 Dubbo 零信任架构图
-
-![Authentication](/imgs/v3/feature/security/arch.png)
-
-## Authentication 认证
-
-Dubbo 提供了两种认证模式:
-
-* **传输通道认证 (Channel Authentication)**:Dubbo 支持基于 TLS 的 HTTP/2 和 TCP 通信,通过 Channel Authentication API 或者控制面认证策略可以开启 TLS,实现 Server 身份端认证以及数据链路加密。另外,还可以开启 mTLS 实现 Client、Server 双向认证。Channel Authentication 是 service-to-service 模式的认证,代表的是服务或实例的身份认证。
-* **请求认证 (Request Authentication)**:Dubbo 提供了 API 用来在用户请求上下文中放入代表用户身份的 credential (如 JSON Web Token),Dubbo 框架将自动识别请求中的身份信息并进行权限校验。另外,你也可以定制请求上下文中的身份,如放入 Access Token 的如 OAuth2 tokens。Request Authentication 是 end-user 模式的认证,代表登录系统的用户身份的认证。
-
-### 架构图
-
-你可以使用 Istio 控制面管理证书、认证策略等,不同的认证策略会影响 Dubbo 数据面的认证行为,如是否开启 mTLS、是否允许迁移阶段的 Plaintext 请求等。
-
-在 Istio 模式下,Dubbo 认证机制通过 xDS 实现了和 Istio 控制面的自动对接,即 Istio 控制面生成的证书、认证策略配置会自动的下发到 Dubbo 数据面,Dubbo 数据面通过 Authentication API 接收配置并将它们应用到后续的所有数据通信环节,如启用新的证书、执行新的认证策略等。
-
-如果认证策略开启了 Request Authentication,则 Dubbo 数据面要负责 JWT token 的读取与填充,即 token 要在请求发起前附加到请求上下文中。Request Authentication 使用的前提一定是开启了 Channel Authentication,否则 Request Authentication 无法生效。
-
-![Authentication](/imgs/v3/feature/security/auth-1.png)
-
-#### Dubbo mTLS 流程
-
-在 Istio 部署架构下,可以通过控制面认证策略开启或关闭 Channel Authentication 的双向认证,双向认证的工作流程如下:
-
-1. 通过 Istio 下发认证策略,开启双向认证
-2. Dubbo 客户端同服务端开启双向 TLS 握手,在此期间,Dubbo 客户端会做 secure naming check 以检查服务端的身份(它被证实是有运行这个服务的合法身份)。
-3. 客户端和服务端之间建立一条双向的 mTLS 链接,随后发起正常的加密通信。
-4. Dubbo 服务端收到请求后,识别客户端身份并检查其是否有权限访问响应的资源。
-
-### 认证策略
-具体请查看 Istio 官方支持的认证规则,Dubbo 完全支持 Istio 定义的认证策略。
-
-https://istio.io/latest/docs/concepts/security/#authentication-policies
-
-## Authorization 鉴权
-
-Dubbo 抽象了一套鉴权的扩展机制,但当前在具体实现上只支持 Istio 体系,因此其鉴权能力与 Istio 官方描述对等。具体可参见
-[Istio 鉴权文档](https://istio.io/latest/docs/concepts/security/#authorization)
-
-### 架构图
-
-Dubbo 通过 xDS 与 Istio 控制面的数据通道,接收用户配置的鉴权策略,当一个请求到达 Dubbo 实例时,Dubbo SDK 使用内置的鉴权策略引擎将请求参数和用户身份与鉴权策略进行匹配,如果匹配成功则允许访问,否则拒绝访问。
-
-![Authorization](/imgs/v3/feature/security/authz-1.png)
-
-Dubbo 完整的鉴权工作流程如下:
-
-![Authorization](/imgs/v3/feature/security/authz-2.png)
-
-### 鉴权策略
-具体请查看 Istio 官方支持的鉴权规则,Dubbo 完全支持 Istio 定义的鉴权策略。
-
-https://istio.io/latest/docs/concepts/security/#authorization-policies
-
-
-## Dubbo 认证 API
-Dubbo 定义了一套认证 API,对于常规使用的场景,开发者可以通过这套 API 启用 TLS/mTLS 通信;但对于 Istio 控制面部署的场景,Dubbo 会自动识别 Istio 控制面下发的证书和认证策略,因此只需要与 Istio 控制面交互即可,不需要 Dubbo 侧的特别配置。
-
-不论是否使用 Istio 控制面,对于 Request Authentication,JWT token 仍需要在 Dubbo 侧编程指定。
-
-每种语言实现的认证 API 定义略有差异,具体定义请参考各 SDK 文档:
-* [Java](/)
-* [Go](/)
-* [Rust](/)
-* [Node.js](/)
-
-## 示例任务
-
-访问如下 [Dubbo 任务示例](/) 进行安全策略动手实践。
diff --git a/content/zh-cn/overview/core-features/service-definition.md b/content/zh-cn/overview/core-features/service-definition.md
deleted file mode 100644
index 9de24816ae9..00000000000
--- a/content/zh-cn/overview/core-features/service-definition.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/service-definition/
-description: 微服务开发
-linkTitle: 微服务开发
-title: 微服务开发
-type: docs
-weight: 1
----
-
-
-Dubbo 解决企业微服务从开发、部署到治理运维的一系列挑战,Dubbo 为开发者提供从项目创建、开发测试,到部署、可视化监测、流量治理,再到生态集成的全套服务。
-* **开发层面**,Dubbo 提供了 Java、Go、Rust、Node.js 等语言实现并定义了一套微服务开发范式,配套脚手架可用于快速创建微服务项目骨架
-* **部署层面**,Dubbo 应用支持虚拟机、Docker 容器、Kubernetes、服务网格架构部署
-* **服务治理层面**,Dubbo 提供了地址发现、负载均衡、流量管控等治理能力,官方还提供 Admin 可视化控制台、丰富的微服务生态集成
-
-## 开发
-
-接下来以 Java 体系 Spring Boot 项目为例讲解 Dubbo 应用开发的基本步骤,整个过程非常直观简单,其他语言开发过程类似。
-
-### 创建项目
-<a href="https://start.dubbo.apache.org/bootstrap.html" target="_blank">Dubbo 微服务项目脚手架</a>(支持浏览器页面、命令行和 IDE)可用于快速创建微服务项目,只需要告诉脚手架期望包含的功能或组件,脚手架最终可以帮助开发者生成具有必要依赖的微服务工程。更多脚手架使用方式的讲解,请参见任务模块的 [通过模板生成项目脚手架](../../tasks/develop/template/)
-
-![脚手架示例图](/imgs/v3/advantages/initializer.png)
-
-### 开发服务
-
-**1. 定义服务**
-
-```java
-public interface DemoService {
-    String hello(String arg);
-}
-```
-
-**2. 提供业务逻辑实现**
-
-```java
-@DubboService
-public class DemoServiceImpl implements DemoService {
-    public String hello(String arg) {
-        // put your microservice logic here
-    }
-}
-```
-
-### 发布服务
-**1. 发布服务定义**
-
-为使消费方顺利调用服务,服务提供者首先要将服务定义以 Jar 包形式发布到 Maven 中央仓库。
-
-**2. 对外暴露服务**
-
-补充 Dubbo 配置并启动 Dubbo Server
-
-```yaml
-dubbo:
-  application:
-    name: dubbo-demo
-  protocol:
-    name: dubbo
-    port: -1
-  registry:
-    address: zookeeper://127.0.0.1:2181
-```
-
-### 调用服务
-
-首先,消费方通过 Maven/Gradle 引入 `DemoService` 服务定义依赖。
-
-```xml
-<dependency>
-    <groupId>org.apache.dubbo</groupId>
-    <artifactId>dubbo-demo-interface</artifactId>
-    <version>3.2.0</version>
-</dependency>
-```
-
-编程注入远程 Dubbo 服务实例
-
-```java
-@Bean
-public class Consumer {
-    @DubboReference
-    private DemoService demoService;
-}
-```
-
-以上是 Dubbo 微服务开发的流程性说明,实际开发的详细指导步骤请参见:
-* [Java 微服务开发入门](../../quickstart/java)
-* [Go 微服务开发入门](../../quickstart/go)
-* [Rust 微服务开发入门](../../quickstart/rust)
-* [Node.js 微服务开发入门](https://github.com/apache/dubbo-js)
-
-## 部署
-Dubbo 原生服务可打包部署到 Docker 容器、Kubernetes、服务网格 等云原生基础设施和微服务架构。
-
-关于不同环境的部署示例,可参考:
-* [部署 Dubbo 服务到 Docker 容器](../../tasks/deploy/deploy-on-docker)
-* [部署 Dubbo 服务到 Kubernetes](../../tasks/deploy/deploy-on-k8s-docker)
-
-## 治理
-对于服务治理,绝大多数应用只需要增加以下配置即可,Dubbo 应用将具备地址发现和负载均衡能力。
-
-```yaml
-dubbo:
-  registry:
-    address: zookeeper://127.0.0.1:2181
-```
-
-部署并打开 [Dubbo Admin 控制台](../../tasks/deploy),可以看到集群的服务部署和调用数据
-
-![Admin](/imgs/v3/what/admin.png)
-
-除此之外,Dubbo Amin 还可以通过以下能力提升研发测试效率
-* 文档管理,提供普通服务、IDL 文档管理
-* 服务测试 & 服务 Mock
-* 服务状态查询
-
-对于更复杂的微服务实践场景,Dubbo 还提供了更多高级服务治理特性,具体请参见文档了解更多。包括:
-* 流量治理
-* 动态配置
-* 限流降级
-* 数据一致性
-* 可观测性
-* 多协议
-* 多注册中心
-* 服务网格
diff --git a/content/zh-cn/overview/core-features/service-discovery.md b/content/zh-cn/overview/core-features/service-discovery.md
deleted file mode 100644
index 98795cc74ea..00000000000
--- a/content/zh-cn/overview/core-features/service-discovery.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/service-discovery/
-    - /zh-cn/overview/mannual/java-sdk/concepts-and-architecture/service-discovery/
-description: 服务发现
-feature:
-    description: |
-        Dubbo 提供了高性能、可伸缩的服务发现机制,面向百万集群实例规模设计,默认提供 Nacos、Zookeeper 等注册中心适配并支持自定义扩展。
-    title: 服务发现
-linkTitle: 服务发现
-title: 服务发现
-type: docs
-weight: 2
----
-
-
-Dubbo 提供的是一种 Client-Based 的服务发现机制,依赖第三方注册中心组件来协调服务发现过程,支持常用的注册中心如 Nacos、Consul、Zookeeper 等。
-
-以下是 Dubbo 服务发现机制的基本工作原理图:
-
-![service-discovery](/imgs/v3/feature/service-discovery/arc.png)
-
-服务发现包含提供者、消费者和注册中心三个参与角色,其中,Dubbo 提供者实例注册 URL 地址到注册中心,注册中心负责对数据进行聚合,Dubbo 消费者从注册中心读取地址列表并订阅变更,每当地址列表发生变化,注册中心将最新的列表通知到所有订阅的消费者实例。
-
-## 面向百万实例集群的服务发现机制
-区别于其他很多微服务框架的是,**Dubbo3 的服务发现机制诞生于阿里巴巴超大规模微服务电商集群实践场景,因此,其在性能、可伸缩性、易用性等方面的表现大幅领先于业界大多数主流开源产品**。是企业面向未来构建可伸缩的微服务集群的最佳选择。
-
-![service-discovery](/imgs/v3/feature/service-discovery/arc2.png)
-
-* 首先,Dubbo 注册中心以应用粒度聚合实例数据,消费者按消费需求精准订阅,避免了大多数开源框架如 Istio、Spring Cloud 等全量订阅带来的性能瓶颈。
-* 其次,Dubbo SDK 在实现上对消费端地址列表处理过程做了大量优化,地址通知增加了异步、缓存、bitmap 等多种解析优化,避免了地址更新常出现的消费端进程资源波动。
-* 最后,在功能丰富度和易用性上,服务发现除了同步 ip、port 等端点基本信息到消费者外,Dubbo 还将服务端的 RPC/HTTP 服务及其配置的元数据信息同步到消费端,这让消费者、提供者两端的更细粒度的协作成为可能,Dubbo 基于此机制提供了很多差异化的治理能力。
-
-### 高效地址推送实现
-
-从注册中心视角来看,它负责以应用名 (dubbo.application.name) 对整个集群的实例地址进行聚合,每个对外提供服务的实例将自身的应用名、实例ip:port 地址信息 (通常还包含少量的实例元数据,如机器所在区域、环境等) 注册到注册中心。
-
-> Dubbo2 版本注册中心以服务粒度聚合实例地址,比应用粒度更细,也就意味着传输的数据量更大,因此在大规模集群下也遇到一些性能问题。
-> 针对 Dubbo2 与 Dubbo3 跨版本数据模型不统一的问题,Dubbo3 给出了[平滑迁移方案](/zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/migration-service-discovery/),可做到模型变更对用户无感。
-
-![service-discovery](/imgs/v3/feature/service-discovery/registry-data.png)
-
-<br/>
-每个消费服务的实例从注册中心订阅实例地址列表,相比于一些产品直接将注册中心的全量数据 (应用 + 实例地址) 加载到本地进程,Dubbo 实现了按需精准订阅地址信息。比如一个消费者应用依赖 app1、app2,则只会订阅 app1、app2 的地址列表更新,大幅减轻了冗余数据推送和解析的负担。
-
-<p> </p>
-<br/>
-
-![service-discovery](/imgs/v3/feature/service-discovery/subscription2.png)
-
-### 丰富元数据配置
-除了与注册中心的交互,Dubbo3 的完整地址发现过程还有一条额外的元数据通路,我们称之为元数据服务 (MetadataService),实例地址与元数据共同组成了消费者端有效的地址列表。
-
-![service-discovery](/imgs/v3/feature/service-discovery/metadata.png)
-
-完整工作流程如上图所示,首先,消费者从注册中心接收到地址 (ip:port) 信息,然后与提供者建立连接并通过元数据服务读取到对端的元数据配置信息,两部分信息共同组装成 Dubbo 消费端有效的面向服务的地址列表。以上两个步骤都是在实际的 RPC 服务调用发生之前。
-
-> 关于 MetadataService 的定义及完整服务发现流程分析,请查看 [应用级服务发现详解]({{< relref "../../../blog/proposals/service-discovery/" >}})。
-
-> 对于微服务间服务发现模型的数据同步,REST 定义了一套非常有意思的成熟度模型,感兴趣的朋友可以参考这里的链接 https://www.martinfowler.com/articles/richardsonMaturityModel.html, 按照文章中的 4 级成熟度定义,Dubbo 当前基于接口粒度的模型可以对应到最高的 L4 级别。
-
-## 配置方式
-Dubbo 服务发现扩展了多种注册中心组件支持,如 Nacos、Zookeeper、Consul、Redis、kubernetes 等,可以通过配置切换不同实现,同时还支持鉴权、命名空间隔离等配置。具体配置方式请查看 SDK 文档
-
-* [Java](../../mannual/java-sdk/reference-manual/registry)
-* [Golang](../../mannual/golang-sdk/tutorial/develop/registry)
-* [Rust](../../mannual/rust-sdk/)
-
-Dubbo 还支持一个应用内配置多注册中心的情形如双注册、双订阅等,这对于实现不同集群地址数据互通、集群迁移等场景非常有用处,我们将在未来文档中添加 `最佳实践` 对这部分内容进行示例说明。
-
-## 自定义扩展
-注册中心适配支持自定义扩展实现,具体请参见 [Dubbo 可扩展性](../extensibility)
diff --git a/content/zh-cn/overview/core-features/service-mesh.md b/content/zh-cn/overview/core-features/service-mesh.md
deleted file mode 100644
index d92e94b4a1e..00000000000
--- a/content/zh-cn/overview/core-features/service-mesh.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/service-mesh/
-    - /zh-cn/overview/mannual/java-sdk/concepts-and-architecture/mesh/
-description: 服务网格
-feature:
-    description: |
-        灵活的数据面 (Proxy & Proxyless) 部署形态支持,无缝接入 Istio 控制面治理体系。
-    title: 服务网格(Service Mesh)
-linkTitle: 服务网格
-title: 服务网格
-type: docs
-weight: 9
-working-in-progress: true
----
-
-
-
-Dubbo Mesh 是 Dubbo 在云原生背景的微服务整体解决方案,它帮助开发者实现 Dubbo 服务与标准的 Kubernetes Native Service 体系的打通,让 Dubbo 应用能够无缝接入 Istio 等业界主流服务网格产品。
-
-以下是 Dubbo Mesh 的部署架构图
-
-![Dubbo-Mesh](/imgs/v3/mesh/mix-mesh.png)
-
-* 控制面。Istio 作为统一控制面,为集群提供 Kubernetes 适配、服务发现、证书管理、可观测性、流量治理等能力。
-* 数据面。Dubbo 应用实例作为数据面组件,支持两种部署模式
-    * Proxy 模式。Dubbo 进程与 Envoy 部署在同一 pod,进出 Dubbo 的流量都经 Envoy 代理拦截,由 Envoy 执行流量管控。
-    * Proxyless 模式。Dubbo 进程独立部署,进程间直接通信,通过 xDS 协议与控制面直接交互。
-
-关于服务网格架构以及为何要接入 Istio 控制面,请参考 [Istio 官网](https://istio.io/),本文不包含这部分通用内容的讲解,而是会侧重在 Dubbo Mesh 解决方案本身。
-
-## Dubbo Mesh
-
-### Proxy Mesh
-在 proxy 模式下,Dubbo 与 Envoy 等边车 (Proxy or Sidecar) 部署在一起
-
-![dubbo-sidecar](/imgs/v3/mesh/dubbo-proxy.png)
-
-以上是 Dubbo Proxy Mesh 部署架构图
-* Dubbo 与 Envoy 部署在同一个 Pod 中,Istio 实现对流量和治理的统一管控。
-* Dubbo 只提供面向业务应用的编程 API、RPC 通信能力,其余流量管控能力如地址发现、负载均衡、路由寻址等都下沉到 Envoy,Envoy 拦截所有进出流量并完成路由寻址等服务治理工作。
-* 控制面与 Envoy 之间通过图中虚线所示的 xDS 协议进行配置分发。
-
-在 Proxy 模式下,Dubbo3 通信层选用 Triple、gRPC、REST 等基于 HTTP 的通信协议可以获得更好的网关穿透性与性能体验。
-
-### Proxyless Mesh
-在 Proxyless 模式下,没有 Envoy 等代理组件,Dubbo 进程保持独立部署并直接通信,Istio 控制面通过 xDS 与 Dubbo 进程进行治理能力交互。
-
-![dubbo-proxyless](/imgs/v3/mesh/dubbo-proxyless.png)
-
-Proxyless 模式下 Dubbo 部署与服务网格之前基本一致,通过不同语言版本的 Dubbo3 SDK 直接实现 xDS 协议解析
-
-#### 为什么需要 Proxyless Mesh
-
-Proxy 模式很好的实现了治理能力与有很多优势,如平滑升级、多语言、业务侵入小等,但也带来了一些额外的问题,比如:
-* Sidecar 通信带来了额外的性能损耗,这在复杂拓扑的网络调用中将变得尤其明显。
-* Sidecar 的存在让应用的声明周期管理变得更加复杂。
-* 部署环境受限,并不是所有的环境都能满足 Sidecar 部署与请求拦截要求。
-
-在 Proxyless 模式下,Dubbo 进程之间继续保持直连通信模式:
-* 没有额外的 Proxy 中转损耗,因此更适用于性能敏感应用
-* 更有利于遗留系统的平滑迁移
-* 架构简单,容易运维部署
-* 适用于几乎所有的部署环境
-
-## 示例任务
-了解了足够多的原理知识,我们推荐你访问如下 [示例](../../tasks/mesh) 进行动手实践。
-
-## 可视化
-推荐使用 [Dubbo Admin](../../tasks/deploy) 作为您 Dubbo 集群的可视化控制台,它兼容所有 Kubernetes、Mesh 和非 Mesh 架构的部署。
-
-除此之外,你也可以使用 [Istio 官方推荐的可视化工具](https://istio.io/latest/docs/tasks/observability/kiali/) 来管理您的 Dubbo Mesh 集群。
-
-## 接入非 Istio 控制面
-Dubbo Mesh 本身并不绑定任何控制面产品实现,你可以使用 Istio、Linkerd、Kuma 或者任一支持 xDS 协议的控制面产品,对于 Sidecar 亦是如此。
-
-如果你已经完整的体验了 [基于 Istio 的 Dubbo Mesh](/) 示例任务,并且发现 Istio 很好的满足了你的 Dubbo Mesh 治理诉求,那么采用 Istio 作为你的控制面是首选的解决方案。
-
-如果你发现 Istio 模式下 Dubbo 部分能力受限,而这部分能力正好是你需要的,那么你需要考虑接入 Dubbo 控制面,用 Dubbo 控制面来替代 Istio,以获得更多 Dubbo 体系原生能力支持、更好的性能体验。具体请参见 [基于 Dubbo 定制控制面的 Dubbo Mesh 示例任务](/)。
-
-> 简单来讲,这是 Dubbo 社区发布的一款基于 Istio 的定制版本控制面,Dubbo 控制面安装与能力差异请参见上面的示例任务链接。
-
-## 老系统迁移方案
-### 如何解决注册中心数据同步的问题?
-Address Synchronization
-
-### 如何解决 Dubbo2 协议通信的问题?
-
-Aeraki Mesh
diff --git a/content/zh-cn/overview/core-features/traffic/_index.md b/content/zh-cn/overview/core-features/traffic/_index.md
deleted file mode 100755
index a8a760fd244..00000000000
--- a/content/zh-cn/overview/core-features/traffic/_index.md
+++ /dev/null
@@ -1,274 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/traffic/
-description: 流量管控
-feature:
-    description: |
-        Dubbo 提供的基于路由规则的流量管控策略,可以帮助实现全链路灰度、金丝雀发布、按比例流量转发、动态调整调试时间、设置重试次数等服务治理能力。
-    title: 流量管控
-linkTitle: 流量管控
-no_list: true
-title: 流量管控
-type: docs
-weight: 4
----
-
-
-
-Dubbo 提供了丰富的流量管控策略
-* **地址发现与负载均衡**,地址发现支持服务实例动态上下线,负载均衡确保流量均匀的分布到每个实例上。
-* **基于路由规则的流量管控**,路由规则对每次请求进行条件匹配,并将符合条件的请求路由到特定的地址子集。
-
-服务发现保证调用方看到最新的提供方实例地址,服务发现机制依赖注册中心 (Zookeeper、Nacos、Istio 等) 实现。在消费端,Dubbo 提供了多种负载均衡策略,如随机负载均衡策略、一致性哈希负载、基于权重的轮询、最小活跃度优先、P2C 等。
-
-Dubbo 的流量管控规则可以基于应用、服务、方法、参数等粒度精准的控制流量走向,根据请求的目标服务、方法以及请求体中的其他附加参数进行匹配,符合匹配条件的流量会进一步的按照特定规则转发到一个地址子集。流量管控规则有以下几种:
-* 条件路由规则
-* 标签路由规则
-* 脚本路由规则
-* 动态配置规则
-
-如果底层用的是基于 HTTP 的 RPC 协议 (如 REST、gRPC、Triple 等),则服务和方法等就统一映射为 HTTP 路径 (path),此时 Dubbo 路由规则相当于是基于 HTTP path 和 headers 的流量分发机制。
-
-> Dubbo 中有应用、服务和方法的概念,一个应用可以发布多个服务,一个服务包含多个可被调用的方法,从抽象的视角来看,一次 Dubbo 调用就是某个消费方应用发起了对某个提供方应用内的某个服务特定方法的调用,Dubbo 的流量管控规则可以基于应用、服务、方法、参数等粒度精准的控制流量走向。
-
-## 工作原理
-
-以下是 Dubbo 单个路由器的工作过程,路由器接收一个服务的实例地址集合作为输入,基于请求上下文 (Request Context) 和 (Router Rule) 实际的路由规则定义对输入地址进行匹配,所有匹配成功的实例组成一个地址子集,最终地址子集作为输出结果继续交给下一个路由器或者负载均衡组件处理。
-
-![Router](/imgs/v3/feature/traffic/router1.png)
-
-通常,在 Dubbo 中,多个路由器组成一条路由链共同协作,前一个路由器的输出作为另一个路由器的输入,经过层层路由规则筛选后,最终生成有效的地址集合。
-* Dubbo 中的每个服务都有一条完全独立的路由链,每个服务的路由链组成可能不同,处理的规则各异,各个服务间互不影响。
-* 对单条路由链而言,即使每次输入的地址集合相同,根据每次请求上下文的不同,生成的地址子集结果也可能不同。
-
-![Router](/imgs/v3/feature/traffic/router2.png)
-
-## 路由规则分类
-### 标签路由规则
-
-标签路由通过将某一个服务的实例划分到不同的分组,约束具有特定标签的流量只能在指定分组中流转,不同分组为不同的流量场景服务,从而实现流量隔离的目的。标签路由可以作为蓝绿发布、灰度发布等场景能力的基础。
-
-标签路由规则是一个非此即彼的流量隔离方案,也就是匹配`标签`的请求会 100% 转发到有相同`标签`的实例,没有匹配`标签`的请求会 100% 转发到其余未匹配的实例。如果您需要按比例的流量调度方案,请参考示例 [基于权重的按比例流量路由](../../tasks/traffic-management/weight/)。
-
-`标签`主要是指对 Provider 端应用实例的分组,目前有两种方式可以完成实例分组,分别是`动态规则打标`和`静态规则打标`。`动态规则打标` 可以在运行时动态的圈住一组机器实例,而 `静态规则打标` 则需要实例重启后才能生效,其中,动态规则相较于静态规则优先级更高,而当两种规则同时存在且出现冲突时,将以动态规则为准。
-
-#### 标签规则示例 - 静态打标
-
-静态打标需要在服务提供者实例启动前确定,并且必须通过特定的参数 `tag` 指定。
-
-##### Provider
-
-在 Dubbo 实例启动前,指定当前实例的标签,如部署在杭州区域的实例,指定 `tag=gray`。
-
-```xml
-<dubbo:provider tag="gray"/>
-```
-
-or
-
-```xml
-<dubbo:service tag="gray"/>
-```
-
-or
-
-```properties
-java -jar xxx-provider.jar -Ddubbo.provider.tag=gray
-```
-
-##### Consumer
-
-发起调用的一方,在每次请求前通过 `tag` 设置流量标签,确保流量被调度到带有同样标签的服务提供方。
-
-```java
-RpcContext.getContext().setAttachment(Constants.TAG_KEY, "gray");
-```
-
-#### 标签规则示例 - 动态打标
-
-相比于静态打标只能通过 `tag` 属性设置,且在启动阶段就已经固定下来,动态标签可以匹配任意多个属性,根据指定的匹配条件将 Provider 实例动态的划分到不同的流量分组中。
-
-##### Provider
-
-以下规则对 `shop-detail` 应用进行了动态归组,匹配 `env: gray` 的实例被划分到 `gray` 分组,其余不匹配 `env: gray` 继续留在默认分组 (无 tag)。
-
-```yaml
-configVersion: v3.0
-force: true
-enabled: true
-key: shop-detail
-tags:
-  - name: gray
-    match:
-      - key: env
-        value:
-          exact: gray
-```
-
-> 这里牵涉到如何给您的实例打各种原始 label 的问题,即上面示例中的 `env`,一种方式是直接写在配置文件中,如上面静态规则实例 provider 部分的配置所示,另一种方式是通过预设环境变量指定,关于这点请参考下文的 [如何给实例打标](#如何给实例打标) 一节。
-
-##### Consumer
-
-服务发起方的设置方式和之前静态打标规则保持一致,只需要在每次请求前通过 `tag` 设置流量标签,确保流量被调度到带有同样标签的服务提供方。
-
-```java
-RpcContext.getContext().setAttachment(Constants.TAG_KEY, "Hangzhou");
-```
-
-设置了以上标签的流量,将全部导流到 `hangzhou-region` 划分的实例上。
-
-> 请求标签的作用域仅为一次点对点的 RPC 请求。比如,在一个 A -> B -> C 调用链路上,如果 A -> B 调用通过 `setAttachment` 设置了 `tag` 参数,则该参数不会在 B -> C 的调用中生效,同样的,在完成了 A -> B -> C 的整个调用同时 A 收到调用结果后,如果想要相同的 `tag` 参数,则在发起其他调用前仍需要单独设置 `setAttachment`。可以参考 [示例任务 - 环境隔离](../../tasks/traffic-management/isolation/) 了解更多 `tag` 全链路传递解决方案。
-
-### 条件路由规则
-
-条件路由与标签路由的工作模式非常相似,也是首先对请求中的参数进行匹配,符合匹配条件的请求将被转发到包含特定实例地址列表的子集。相比于标签路由,条件路由的匹配方式更灵活:
-
-* 在标签路由中,一旦给某一台或几台机器实例打了标签,则这部分实例就会被立马从通用流量集合中移除,不同标签之间不会再有交集。有点类似下图,地址集合在输入阶段就已经划分明确。
-
-![tag-condition-compare](/imgs/v3/feature/traffic/tag-condition-compare1.png)
-
-* 而从条件路由的视角,所有的实例都是一致的,路由过程中不存在分组隔离的问题,每次路由过滤都是基于全量地址中执行
-
-![tag-condition-compare](/imgs/v3/feature/traffic/tag-condition-compare2.png)
-
-条件路由规则的主体 `conditions` 主要包含两部分内容:
-
-* => 之前的为请求参数匹配条件,指定的 `匹配条件指定的参数` 将与 `消费者的请求上下文 (URL)、甚至方法参数` 进行对比,当消费者满足匹配条件时,对该消费者执行后面的地址子集过滤规则。
-* => 之后的为地址子集过滤条件,指定的 `过滤条件指定的参数` 将与 `提供者实例地址 (URL)` 进行对比,消费者最终只能拿到符合过滤条件的实例列表,从而确保流量只会发送到符合条件的地址子集。
-    * 如果匹配条件为空,表示对所有请求生效,如:`=> status != staging`
-    * 如果过滤条件为空,表示禁止来自相应请求的访问,如:`application = product =>`
-
-
-#### 条件路由规则示例
-
-基于以下示例规则,所有 `org.apache.dubbo.demo.CommentService` 服务调用都将被转发到与当前消费端机器具有相同 `region` 标记的地址子集。`$region` 是特殊引用符号,执行过程中将读取消费端机器的实际的 `region` 值替代。
-
-```yaml
-configVersion: v3.0
-enabled: true
-force: false
-key: org.apache.dubbo.samples.CommentService
-conditions:
-  - '=> region = $region'
-```
-
-> 针对条件路由,我们通常推荐配置 `scope: service` 的规则,因为它可以跨消费端应用对所有消费特定服务 (service) 的应用生效。关于 Dubbo 规则中的 `scope` 以及 `service`、`application` 的说明请阅读 [条件路由规则手册](./condition-rule)。
-
-条件路由规则还支持设置具体的机器地址如 ip 或 port,这种情况下使用条件路由可以处理一些开发或线上机器的临时状况,实现**黑名单、白名单、实例临时摘除**等运维效果,如以下规则可以将机器 `172.22.3.91` 从服务的可用列表中排除。
-
-```yaml
-=> host != 172.22.3.91
-```
-
-条件路由还支持基于请求参数的匹配,示例如下:
-
-```yaml
-conditions:
-  - method=getDetail&arguments[0]=dubbo => port=20880
-```
-
-### 动态配置规则
-通过 Dubbo 提供的动态配置规则,您可以动态的修改 Dubbo 服务进程的运行时行为,整个过程不需要重启,配置参数实时生效。基于这个强大的功能,基本上所有运行期参数都可以动态调整,比如超时时间、临时开启 Access Log、修改 Tracing 采样率、调整限流降级参数、负载均衡、线程池配置、日志等级、给机器实例动态打标签等。与上文讲到的流量管控规则类似,动态配置规则支持应用、服务两个粒度,也就是说您一次可以选择只调整应用中的某一个或几个服务的参数配置。
-
-当然,出于系统稳定性、安全性的考量,有些特定的参数是不允许动态修改的,但除此之外,基本上所有参数都允许动态修改,很多强大的运行态能力都可以通过这个规则实现,您可以找个示例应用去尝试一下。通常 URL 地址中的参数均可以修改,这在每个语言实现的参考手册里也记录了一些更详细的说明。
-
-#### 动态配置规则示例 - 修改超时时间
-
-以下示例将 `org.apache.dubbo.samples.UserService` 服务的超时参数调整为 2000ms
-
-```yaml
-configVersion: v3.0
-scope: service
-key: org.apache.dubbo.samples.UserService
-enabled: true
-configs:
-  - side: provider
-    parameters:
-      timeout: 2000
-```
-
-以下部分指定这个配置是服务粒度,具体变更的服务名为 `org.apache.dubbo.samples.UserService`。`scope` 支持 `service`、`application` 两个可选值,如果 `scope: service`,则 `key` 应该配置为 `version/service:group` 格式。
-
-```yaml
-scope: service
-key: org.apache.dubbo.samples.UserService
-```
-
-> 关于 Dubbo 规则中的 `scope` 以及 `service`、`application` 的说明请参考 [动态配置参考手册](./configuration-rule/) 或 [动态配置示例](../../tasks/traffic-management/timeout/)。
-
-`parameters` 参数指定了新的修改值,这里将通过 `timeout: 2000` 将超时时间设置为 2000ms。
-
-```yaml
-parameters:
- timeout: 2000
-```
-
-### 脚本路由规则
-脚本路由是最直观的路由方式,同时它也是当前最灵活的路由规则,因为你可以在脚本中定义任意的地址筛选规则。如果我们为某个服务定义一条脚本规则,则后续所有请求都会先执行一遍这个脚本,脚本过滤出来的地址即为请求允许发送到的、有效的地址集合。
-
-```yaml
-configVersion: v3.0
-key: demo-provider
-type: javascript
-enabled: true
-script: |
-  (function route(invokers,invocation,context) {
-      var result = new java.util.ArrayList(invokers.size());
-      for (i = 0; i < invokers.size(); i ++) {
-          if ("10.20.3.3".equals(invokers.get(i).getUrl().getHost())) {
-              result.add(invokers.get(i));
-          }
-      }
-      return result;
-  } (invokers, invocation, context)); // 表示立即执行方法
-```
-
-## 如何给实例打标
-
-当前,有两种方式可以在启动阶段为 Dubbo 实例指定标签,一种是之前提到的应用内配置的方式,如在 xml 文件中设置 `<dubbo:provider tag="gray"/>`,应用打包部署后即自动被打标。
-
-还有一种更灵活的方式,那就是通过读取所部署机器上的环境信息给应用打标,这样应用的标签就可以跟随实例动态的自动填充,避免每次更换部署环境就重新打包应用镜像的问题。当前 Dubbo 能自动读取以下环境变量配置:
-
-```yaml
-spec:
-  containers:
-  - name: detail
-    image: apache/demo-detail:latest
-    env:
-    - name: DUBBO_LABELS
-      value: "region=hangzhou; env=gray"
-```
-
-```yaml
-spec:
-  containers:
-  - name: detail
-    image: apache/demo-detail:latest
-    env:
-    - name: DUBBO_ENV_KEYS
-      value: "REGION, ENV"
-    - name: REGION
-      value: "hangzhou"
-    - name: ENV
-      value: "gray"
-```
-
-如果您有不同的实例环境保存机制,可以通过扩展 `InfraAdapter 扩展点` 来自定义自己的标签加载方式。如果您的应用是部署在 Kubernetes 环境下,并且已经接入了服务网格体系,则也可以使用标准 deployment 标签的方式打标,具体请跟随 [服务网格任务示例](../../tasks/mesh/) 学习。
-
-## 如何配置流量规则
-Dubbo 提供了控制台 Dubbo Admin,帮助您可视化的下发流量管控规则,并实时监控规则生效情况。
-
-![Admin](/imgs/v3/what/admin.png)
-
-Dubbo 还提供了 `dubboctl` 命令行工具,需要有 Dubbo Admin 提前部署就绪,因为 dubboctl 是通过与 Admin 进行 http 通信完成规则下发的。
-
-如果您使用的是如 Istio 的服务网格架构,还可以使用 Istioctl、kubectl 等下发 Istio 标准规则。
-
-## 接入服务网格
-
-以上介绍的都是 Dubbo 体系内的流量治理规则,如果您对服务网格架构感兴趣,则可以将 Dubbo 服务接入服务网格体系,这样,您就可以使用服务网格提供的流量治理能力,如 Istio 体系的 VirtualService 等。
-
-具体请参见 [Dubbo 中的服务网格架构](../service-mesh)。
-
-## 跟随示例学习
-我们搭建了一个 [线上商城系统](../../tasks/traffic-management/) 供您学习流量规则的具体使用。
diff --git a/content/zh-cn/overview/core-features/traffic/circuit-breaking.md b/content/zh-cn/overview/core-features/traffic/circuit-breaking.md
deleted file mode 100644
index 4b1444cd995..00000000000
--- a/content/zh-cn/overview/core-features/traffic/circuit-breaking.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-description: ""
-linkTitle: 限流 & 熔断
-title: 限流 & 熔断
-type: docs
-weight: 5
----
-
-由于微服务分布式的特点,如何构建稳定的微服务集群是一个很大的挑战,其中有两项非常关键的点值得关注
-* 流量控制 (Rate Limiting)
-* 熔断降级 (Circuit Breaking)
-
-## 流量控制
-**流量控制更多的是站在 Dubbo 服务提供者视角来保证服务稳定性**,通过明确的为 Dubbo 服务设置请求上限阈值,确保服务所处理的请求数始终在一个合理范围之内,从而确保系统整体的稳定性。
-
-![provider-rate-limit](/imgs/v3/feature/circuit-breaking/provider-rate-limit.png)
-
-根据服务的具体部署情况,服务所能处理的流量上限是一定的,当对服务的请求数量保持在合理的范围时,系统运行正常;而当请求数量严重超过服务处理能力时,如大促期间的流量洪峰等场景,就可能造成服务提供者端的资源过度消耗、负载过高,进而出现响应延迟、请求无应答、系统假死等情况。
-
-流量控制解决的问题和工作方式比较容易理解,而其使用的难点就是如何确定服务所能处理的流量最大值?
-* 一种模式是由用户预先设定一个固定的限流值,如 Dubbo 通过集成 Sentinel 等产品实现的限流能力即是这种模式
-    * [Dubbo Sentinel 流量控制](../../../tasks/rate-limit/sentinel/)
-* 另一种方式是 Dubbo 框架自动根据系统或集群负载情况执行限流,相比用户预先设置限流值更加灵活方便,Dubbo 目前内置了自适应限流模式,具体可参见:
-    * [Java 自适应限流使用方式](../../../mannual/java-sdk/advanced-features-and-usage/performance/adaptive-concurrency-control/)
-    * [Go 自适应限流使用方式](../../../reference/proposals/heuristic-flow-control/)
-    * [自适应限流设计原理](../../../reference/proposals/heuristic-flow-control/)
-
-## 熔断降级
-**熔断降级则是更多的从 Dubbo 服务消费者视角来保障系统稳定性的重要手段**。一个服务往往需要调用更多的下游 Dubbo 服务来完成业务逻辑,这时下游服务的稳定性就会影响当前服务甚至整个系统的稳定性,熔断(Circuit Breaking)即是面向不稳定服务场景设计的,它能最大限度避免下游服务不稳定对上游服务带来的影响。
-
-而相比于熔断后直接返回调用失败信息,配合服务降级能力,我们可以继续调用预先设置好的服务降级逻辑,以降级逻辑的结果作为最终调用结果,以更优雅的返回给服务调用方。
-
-![consumer-circuit-breaking](/imgs/v3/feature/circuit-breaking/consumer-circuit-breaking.png)
-
-如上图所示,Dubbo Consumer 依赖的下游的三个 Dubbo 服务,当 Service 3 出现不稳定的情况时(如响应时间变长、错误率增加等),从而 Consumer 调用 Service 3 的线程等资源就会产生堆积,如果此时我们不在 Consumer 侧做任何限制,则 Service 1 与 Service 2 的调用都会受到稳定性影响。通过熔断 Service 3 我们就能保证整个 Dubbo Consumer 服务的稳定性,不拖垮整个 Consumer 服务,熔断 Service 3 的方式可以有很多种实现,包括线程数、信号量、错误率等。
-
-Dubbo 通过集成业界主流的框架实现了服务熔断降级能力
-
-* [Sentinel](../../../tasks/rate-limit/sentinel/)
-* [Hystrix](../../../tasks/rate-limit/hystrix/)
-* [Resilience4J](../../../tasks/rate-limit/resilience4j/)
diff --git a/content/zh-cn/overview/core-features/traffic/condition-rule.md b/content/zh-cn/overview/core-features/traffic/condition-rule.md
deleted file mode 100644
index 8fb8e7865d4..00000000000
--- a/content/zh-cn/overview/core-features/traffic/condition-rule.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/traffic/condition-rule/
-description: ""
-linkTitle: 条件路由
-title: 条件路由规则
-type: docs
-weight: 1
-
----
-
-
-
-条件路由规则将符合特定条件的请求转发到特定的地址实例子集上。规则首先对发起流量的请求参数进行匹配,符合匹配条件的请求将被转发到包含特定实例地址列表的子集。
-
-以下是一个条件路由规则示例。
-
-基于以下示例规则,所有 `org.apache.dubbo.samples.CommentService` 服务 `getComment` 方法的调用都将被转发到有 `region=Hangzhou` 标记的地址子集。
-
-  ```yaml
-  configVersion: v3.0
-  scope: service
-  force: true
-  runtime: true
-  enabled: true
-  key: org.apache.dubbo.samples.CommentService
-  conditions:
-    - method=getComment => region=Hangzhou
-  ```
-
-可以看具体的例子代码: [条件路由](https://github.com/apache/dubbo-samples/tree/master/4-governance/dubbo-samples-configconditionrouter/src/main/java/org/apache/dubbo/samples/governance)
-
-## ConditionRule
-
-条件路由规则主体。定义路由规则生效的目标服务或应用、流量过滤条件以及一些特定场景下的行为。
-
-| 字段名        | 类型     | **描述**                                                     | 必填 |
-| --- | --- |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ---- |
-| configVersion | string   | 条件路由的版本,当前版本为 `v3.0`                            | 是   |
-| scope         | string   | 支持 `service` 和 `application` 两种规则                     | 是   |
-| key           | string   | 应用到的目标服务或应用程序的标识符<br/><br/>- 当 `scope:service` 时,  `key`应该是该规则生效的服务名比如 org.apache.dubbo.samples.CommentService<br/> - 当 `scope:application` 时, then `key`应该是该规则应该生效的应用名称,比如说my-dubbo-service. | 是   |
-| enabled       | bool     | 规则是否生效 当 `enabled:false` 时,规则不生效               | 是   |
-| conditions    | string[] | 配置中定义的条件规则,详情可以看[条件规则](https://cn.dubbo.apache.org/zh-cn/overview/core-features/traffic/condition-rule/#condition) | 是   |
-| force         | bool     | T路由后实例子集为空时的行为。 `true` 则抛出一个No Provider Exception。  `false` 则忽略规则,直接去请求其他的实例。默认值是false | 否   |
-| runtime       | bool     | 是否为每个 rpc 调用运行路由规则或使用路由缓存(如果可用)。默认值是false(false则走缓存,true不走缓存) | 否   |
-
-## Condition
-
-`Condition` 为条件路由规则的主体,类型为一个复合结构的 string 字符串,如 `method=getComment => region=Hangzhou`。其中,
-
-* => 之前的为请求参数匹配条件,指定的 `匹配条件指定的参数` 将与 `消费者的请求上下文 (URL)、甚至方法参数` 进行对比,当消费者满足匹配条件时,对该消费者执行后面的地址子集过滤规则。
-* => 之后的为地址子集过滤条件,指定的 `过滤条件指定的参数` 将与 `提供者实例地址 (URL)` 进行对比,消费者最终只能拿到符合过滤条件的实例列表,从而确保流量只会发送到符合条件的地址子集。
-  * 如果匹配条件为空,表示对所有请求生效,如:`=> status != staging`
-  * 如果过滤条件为空,表示禁止来自相应请求的访问,如:`application = product =>`
-
-### 匹配/过滤条件
-
-**参数支持**
-
-* 服务调用上下文,如:interface, method, group, version 等
-* 请求上下文,如 attachments[key] = value
-* 方法参数,如 arguments[0] = tom
-* URL 本身的字段,如:protocol, host, port 等
-* URL 上任务扩展参数,如:application, organization 等
-* 支持开发者自定义扩展
-
-**条件支持**
-
-* 等号 = 表示 "匹配",如:method = getComment
-* 不等号 != 表示 "不匹配",如:method != getComment
-
-**值支持**
-
-* 以逗号 , 分隔多个值,如:host != 10.20.153.10,10.20.153.11
-* 以星号 * 结尾,表示通配,如:host != 10.20.*
-* 以美元符 $ 开头,表示引用消费者参数,如:region = $region
-* 整数值范围,如:userId = 1~100、userId = 101~
-* 支持开发者自定义扩展
diff --git a/content/zh-cn/overview/core-features/traffic/configuration-rule.md b/content/zh-cn/overview/core-features/traffic/configuration-rule.md
deleted file mode 100644
index dd58e2911b5..00000000000
--- a/content/zh-cn/overview/core-features/traffic/configuration-rule.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/traffic/configuration-rule/
-description: ""
-linkTitle: 动态配置
-title: 动态配置规则
-type: docs
-weight: 4
----
-
-
-动态配置规则 (ConfigurationRule) 是 Dubbo 设计的在无需重启应用的情况下,动态调整 RPC 调用行为的一种能力,也称为动态覆盖规则,因为它是通过在运行态覆盖 Dubbo 实例或者 Dubbo 实例中 URL 地址的各种参数值,实现改变 RPC 调用行为的能力。
-
-使用动态配置规则,有以下几条关键信息值得注意:
-* **设置规则生效过滤条件。** 配置规则支持一系列的过滤条件,用来限定规则只对符合特定条件的服务、应用或实例才生效。
-* **设置规则生效范围。** 一个 rpc 服务有服务发起方(消费者)和服务处理方(提供者)两个角色,对某一个服务定义的规则,可以具体到限制是对消费者还是提供者生效。
-* **选择规则管理粒度。** Dubbo 支持从服务和应用两个粒度来管理和下发规则。
-
-以下一个应用级别的配置示例,配置生效后,`shop-detail` 应用下提供的所有服务都将启用 accesslog,对 `shop-detail` 部署的所有实例生效。
-
-```yaml
-configVersion: v3.0
-scope: application
-key: shop-detail
-configs:
-  - side: provider
-    parameters:
-      accesslog: 'true'
-```
-
-以下是一个服务级别的配置示例,`key: org.apache.dubbo.samples.UserService` 和 `side: consumer` 说明这条配置对所有正在消费 UserService 的 Dubbo 实例生效,在调用失败后都执行 4 次重试。`match` 条件进一步限制了消费端的范围,限定为只对应用名为 `shop-frontend` 的这个消费端应用生效。
-
-```yaml
-configVersion: v3.0
-scope: service
-key: org.apache.dubbo.samples.UserService
-configs:
-  - match:
-      application:
-        oneof:
-          - exact: shop-frontend
-    side: consumer
-    parameters:
-      retries: '4'
-```
-## ConfigurationRule
-配置规则主体,定义要设置的目标服务或应用、具体的规则配置。具体配置规则 (configs) 可以设置多条。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| configVersion | string | The version of the configuration rule definition, currently available version is `v3.0` | Yes |
-| scope | string | Supports `service` and `application` scope configurations.  | Yes |
-| key | string | The identifier of the target service or application that this rule is about to apply to. <br/><br/>- If `scope:service`is set, then `key`should be specified as the Dubbo service key that this rule targets to control.<br/> - If `scope:application` is set, then `key`should be specified as the name of the application that this rule targets to control.| Yes |
-| enabled | bool | Whether enable this rule or not, set `enabled:false` to disable this rule. | Yes |
-| configs | Config[] | The `match condition` and `configuration` of this rule. | Yes |
-
-## Config
-具体的规则配置定义,包含生效端 (consumer 或 provider) 和过滤条件。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| side | string | Especially useful when `scope:service`is set.<br/><br/>- `side: provider`means this Config will only take effect on the provider instances of the service key.<br/>- `side:consumer`means this Config will only take effect on the consumer instances of the service key| Yes |
-| parameters | map<string, string> | The keys and values this rule aims to change. | Yes |
-| match | MatchCondition | A set of criterion to be met in order for the rule/config to be applied to the Dubbo instance.  | No |
-| enabled | bool | Whether enable this Config or not, will use the value in ConfigurationRule if not set | No |
-| ~~addresses~~ | ~~string[]~~ | ~~replaced with address in MatchCondition~~ | ~~No~~ |
-| ~~providerAddresses~~ | ~~string[]~~ | ~~not supported anymore~~ | ~~No~~ |
-| ~~services~~ | ~~string[]~~ | ~~replaced with service in MatchCondition~~ | ~~No~~ |
-| ~~applications~~ | ~~string[]~~ | ~~replaced with application in MatchCondition~~ | ~~No~~ |
-
-## MatchCondition
-过滤条件,用来设置规则对哪个服务 (service)、应用 (application)、实例 (address),或者包含哪些参数 (param) 的实例生效。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| address | StringMatch | The instance address matching condition for this config rule to take effect.<br/><br/>- xact: "value" for exact string match<br/>- prefix: "value" for prefix-based match<br/>- regex: "value" for RE2 style regex-based match ([https://github.com/google/re2/wiki/Syntax)](https://github.com/google/re2/wiki/Syntax)).| No |
-| service | StringMatch (oneof) | The service matching condition for this config rule to take effect. Effective when `scope: application` is set.<br/><br/>- exact: "value" for exact string match<br/>- prefix: "value" for prefix-based match<br/>- regex: "value" for RE2 style regex-based match ([https://github.com/google/re2/wiki/Syntax)](https://github.com/google/re2/wiki/Syntax)).| No |
-| application | StringMatch (oneof) | The application matching condition for this config rule to take effect. Effective when `scope: service` is set.<br/><br/>- exact: "value" for exact string match<br/>- prefix: "value" for prefix-based match<br/>- regex: "value" for RE2 style regex-based match ([https://github.com/google/re2/wiki/Syntax)](https://github.com/google/re2/wiki/Syntax)).| No |
-| param | ParamCondition[] | The Dubbo url keys and values matching condition for this config rule to take effect. | No |
-
-## ParamCondition
-定义实例参数 (param) 过滤条件,对应到 Dubbo URL 地址参数。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| key | string | The name of the key in the Dubbo url address. | Yes |
-| value | StringMatch (oneof) | The matching condition for the value in the Dubbo url address. | Yes |
-
-## StringMatch
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| exact | string (oneof) | exact string match | No |
-| prefix | string (oneof) | prefix-based match | No |
-| regex | string (oneof) | RE2 style regex-based match ([https://github.com/google/re2/wiki/Syntax)](https://github.com/google/re2/wiki/Syntax)). | No |
diff --git a/content/zh-cn/overview/core-features/traffic/mesh-rule.md.bak b/content/zh-cn/overview/core-features/traffic/mesh-rule.md.bak
deleted file mode 100644
index 7c4fad9c586..00000000000
--- a/content/zh-cn/overview/core-features/traffic/mesh-rule.md.bak
+++ /dev/null
@@ -1,372 +0,0 @@
----
-type: docs
-title: "Mesh 路由规则"
-linkTitle: "Mesh 路由"
-weight: 50
-description: ""
----
-
-Dubbo Mesh 路由规则是基于 Istio 的 VirtualService、DestinationRule 改造而来,总体思路和格式可以参考 Istio 流量管控规则参考手册:[Istio VirtualService](https://istio.io/latest/docs/reference/config/networking/virtual-service/) 和 [Istio DestinationRule](https://istio.io/latest/docs/reference/config/networking/destination-rule/)
-
-本文描述了 Dubbo Mesh 路由规则的设计原理,和 Istio 规则的差异等。
-
-### 基本思想
-基于路由链,采用Pipeline的处理方式,如下图所示:
-
-![route-rule1.png](/imgs/user/route-rule1.png)
-
-
-可以把路由链的逻辑简单的理解为 target = rn(...r3(r2(r1(src))))。对于每一个 router 内部的逻辑,可以抽象为输入地址 addrs-in 与 router 中按全量地址 addrs-all 实现切分好的 n 个互不相交的地址池 addrs-pool-1 ... addrs-pool-n 按实现定义好的规则取交集作为输出 addrs-out。以此类推,完成整个路由链的计算。
-
-![route-rule2.png](/imgs/user/route-rule2.png)
-
-另外一方面,如果 router(n) 需要执行 fallback 逻辑的时候,那么需要经过 router(n) 就应该决定好 fallback 逻辑
-
-
-### fallback 处理原则
-
-由于多个 router 之间多个条件组件之后,很容易出现地址被筛选为空的情况,那么我们需要针对这情况进行 fallback 处理,保证业务在正确性的前提下,能够顺利找到有效地址。
-
-首先我们看一下以下规则
-
-```yaml
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: VirtualService
-metadata:
-  name: demo-route
-spec:
-  hosts:
-  - demo  // 统一定义为应用名
-  dubbo:
-  - service:
-    - exact: com.taobao.hsf.demoService:1.0.0
-    - exact: com.taobao.hsf.demoService:2.0.0
-    routedetail:
-    - name: sayHello-String-method-route
-      match:
-      - method:
-          name_match:
-            exact: "sayHello"
-            .....
-          argp:
-          - string
-      route:
-      - destination:
-          host: demo
-          subset: v1
-        fallback:
-          destination:
-            host: demo
-            subset: v2
-          fallback:
-            destination:
-              host: demo
-              subset: v3
-
-      - name: sayHello-method-route
-        match:
-        - method:
-            name_match:
-              exact: "s-method"
-        route:
-        - destination:
-            host: demo
-            subset: v2
-          fallback:
-            destination:
-              host: demo
-              subset: v3
-
-      - name: interface-route
-        route:
-        - destination:
-          host: demo
-          subset: v3
-
-  - service:
-
-      ....
----
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: DestinationRule
-metadata:
-  name: demo-route
-spec:
-  host: demo
-  subsets:
-  - name: v1
-    labels:
-      sigma.ali/mg: v1-host
-
-  - name: v2
-    labels:
-      sigma.ali/mg: v2-host
-
-  - name: v3
-    labels:
-      sigma.ali/mg: v3-host
-
-```
-
-我们以脚本路由为例,这个脚本路由的匹配条件是遵循一个原则的,就是匹配的范围是从精确到广泛的一个过程,在这个示例来说,就是 sayHello(string)参数 -> sayHello 方法 -> 接口级路由 的一个匹配查找过程。
-
-那么如果我们已经满足某个条件,但是选到的 subset 地址为空,我们将如何进行 fallback 处理呢?
-
-以匹配 sayHello(string)参数 条件为例,我们选择到的是 v1 subset,如果是空,我们可以向上一级是寻找地址,也就是方法级去寻找地址,具体的配置为下
-
-```yaml
-       - name: sayHello-String-method-route
-         match:
-          - method:
-             name_match:
-               exact: "sayHello"
-               .....
-             argp:
-              - string
-         route:
-          - destination:
-              host: demo
-              subset: v1
-            fallback:
-              destination:
-                host: demo
-                subset: v2
-              fallback:
-                destination:
-                  host: demo
-                  subset: v3
-```
-
-此时我们选到的地址是 v2 方法级地址,如果 v2 还是没有地址,根据规则的定义,我们是可以 fallback 到 v3 接口级。
-
-假设我们有一个方法匹配时,如果没有地址,需要不进行 fallback,直接报错,我们可以这样配置
-
-
-```yaml
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: VirtualService
-metadata:
-  name: demo-route
-spec:
-  hosts:
-  - demo  // 统一定义为应用名
-  dubbo:
-  - service:
-    - exact: com.taobao.hsf.demoService:1.0.0
-    - exact: com.taobao.hsf.demoService:2.0.0
-    routedetail:
-      - name: sayHello-String-method-route
-        match:
-        - method:
-            name_match:
-              exact: "sayHello"
-              .....
-            argp:
-            - string
-        route:
-        - destination:
-            host: demo
-            subset: v1
-          fallback:
-            destination:
-              host: demo
-              subset: v2
-            fallback:
-              destination:
-                host: demo
-                subset: v3
-
-      - name: sayHello-method-route
-        match:
-        - method:
-            name_match:
-              exact: "s-method"
-        route:
-        - destination:
-            host: demo
-            subset: v2
-          fallback:
-            destination:
-              host: demo
-              subset: v3
-      - name: some-method-route
-        match:
-        - method:
-            name_match:
-              exact: "some-method"
-        route:
-        - destination:
-            host: demo
-            subset: v4
-
-      - name: interface-route
-        route:
-        - destination:
-          host: demo
-          subset: v3
-
-  - service:
-
-      ....
----
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: DestinationRule
-metadata:
-  name: demo-route
-spec:
-  host: demo
-  subsets:
-  - name: v1
-    labels:
-      sigma.ali/mg: v1-host
-
-  - name: v2
-    labels:
-      sigma.ali/mg: v2-host
-
-  - name: v3
-    labels:
-      sigma.ali/mg: v3-host
-```
-
-从这个规则我们看出来匹配到 some-method  条件时对应的是 v4 subset,那么 v4 为空时,因为没有配置 fallback ,此时会直接报错
-
-#### fallback 处理原则总结
-
-- 我们应该在 VirtualService route 中配置好 Destination 的 fallback 处理逻辑
-- 在 fallback subset 时,如果对应的 subset 也配置有 fallback subset 时,也应递归处理;fallback subset 之间的关系也应该是从具体到广泛
-- 我们在编写匹配条件时,应该遵循从 具体条件到广泛条件 的原则
-
-### RouteChain 的组装模式 (目前未实现)
-
-![route-rule3.png](/imgs/user/route-rule3.png)
-
-
-我们看到上面的图,在路由的过程当中,我们是 Pipeline 的处理方式,Pipeline 的 Router 节点存在顺序,并且每个 Router 都有一个唯一对应的 VirtualService 和 **多个** 相应的 DestinationRule 进行描述。
-
-以 Nacos 上存着的路由规则配置为例,配置的格式如下:
-
-```yaml
-DataId: Demo.rule.yaml
-GROUP: HSF
-
-content:
-
-VirtualService A
----
-DestinationRule A1
----
-DestinationRule A2
----
-VirtualService B
----
-DestinationRule B
----
-VirtualService C
----
-DestinationRule C
----
-...
-```
-
-`VirtualService A` 与 `DestinationRule A1` 、`DestinationRule A2` 组成一个 Router A,`VirtualService B` 与 `DestinationRule B` 组成 Router B,以此类推,完成整个 router 链的组装。
-
-### 示例:按比例流量路由规则
-
-> 注意,虽然接下来的规则和 Istio 的 VirtualService、DestinationRule 很像,但工作过程和具体规则和 Istio 还是有一些差异,Dubbo 只是参考了 Istio 的设计。如果您想接入原生的 Istio 服务网格治理体系,请参考下文 [接入服务网格流量治理](#接入服务网格流量治理)。
-
-在一些场景下,我们需要将相同属性的流量按比例的分发到不同的实例分组。一个典型的示例场景是 A/B 测试,比如我们需要将 20% 流量转发到服务新版本 v2 的实例,以验证新版本的稳定性,或者是将公司内部的一部分用户导流到新版本 v2 的实例进行测试验证。另一个应用场景是实现服务的金丝雀发布,通过逐步调整流量分配比例值,使得新版本的流量逐步提升并最终将全部流量完全迁移到新版本之上。
-
-#### 按比例流量规则示例
-
-以下示例会将访问服务 `org.apache.dubbo.demo.DetailService` 特定方法 `getDetail` 的所有请求按比例进行转发。
-
-```yaml
-...
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: VirtualService
-metadata:
-  name: details
-spec:
-  dubbo:
-   - name: detail-service-traffic-split
-     match:
-      - name:
-        services:
-         - exact: "org.apache.dubbo.demo.DetailService"
-        method:
-         name_match:
-          exact: "getDetail"
-     route:
-      - destination:
-         subset: details-v1
-        weight: 60
-      - destination:
-         subset: details-v2
-        weight: 40
----
-...
-apiVersion: service.dubbo.apache.org/v1alpha1
-kind: DestinationRule
-metadata:
-  name: reviews-route
-spec:
-  subsets:
-    - name: details-v1
-      labels:
-        detail_version: v1 # 'version' is a reserved key in Dubbo, so must not be used.
-    - name: details-v2
-      labels:
-        detail_version: v2 # 'version' is a reserved key in Dubbo, so must not be used.
----
-```
-
-##### Dubbo VirtualService
-
-> 此部分完全可参考 Istio VirtualService 语义,两者几乎完全相同,Dubbo 增加了 `dubbo` 协议标签(对应 http 协议位置)并对 `match` 条件进行了丰富。
-
-`match` 条件设置了流量规则只对访问服务 "org.apache.dubbo.demo.DetailService" 的 `getDetail` 方法的请求有效。
-
-```yaml
-match:
-  - name:
-    services:
-     - exact: "org.apache.dubbo.demo.DetailService"
-    method:
-     name_match:
-      exact: "getDetail"
-```
-
-以下 `route` 指定匹配后流量的目标实例子集,实例子集 `details-v1` `details-v2` 是通过下面的 DestinationRule 定义的。对于没有匹配的流量,则默认可以访问任何实例,不会做任何过滤。
-
-```yaml
-route:
-  - destination:
-     subset: details-v1
-    weight: 60
-  - destination:
-     subset: details-v2
-    weight: 40
-```
-
-##### Dubbo DestinationRule
-
-> 此部分完全可参考 Istio DestinationRule 语义,两者完全相同。
-
-以下规则通过匹配 `detail_version` 值将应用 details 划分为两个部署版本 `v1` 和 `v2`,分别命名为 `deatils-v1` 和 `details-v2`,同时 `deatils-v1` 和 `details-v2` 将成为 Dubbo VirtualService 的流量转发目标对象。
-
-```yaml
-subsets:
- - name: details-v1
-   labels:
-     detail_version: v1 # 'version' is a reserved key in Dubbo, so must not be used.
- - name: details-v2
-   labels:
-     detail_version: v2 # 'version' is a reserved key in Dubbo, so must not be used.
-```
-
-> 和标签路由类似,这里牵涉到如何给您的实例打标(这里是 `detail_version`)的问题,请参考下文的 [如何给实例打标](#如何给实例打标) 一节。
-
-除了以上介绍的与 Istio 流量规则很相似的功能之外,Dubbo 的 VirtualService、DestinationRule 还可以实现方法参数路由等 Istio 规则不能做到的事情,具体查看 [参考手册]()。
-
-
diff --git a/content/zh-cn/overview/core-features/traffic/script-rule.md b/content/zh-cn/overview/core-features/traffic/script-rule.md
deleted file mode 100644
index 63c43b48ccf..00000000000
--- a/content/zh-cn/overview/core-features/traffic/script-rule.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/traffic/script-rule/
-description: ""
-linkTitle: 脚本路由
-title: 脚本路由规则
-type: docs
-weight: 3
----
-
-
-
-脚本路由为流量管理提供了最大的灵活性,所有流量在执行负载均衡选址之前,都会动态的执行一遍规则脚本,根据脚本执行的结果确定可用的地址子集。
-
-脚本路由只对消费者生效且只支持应用粒度管理,因此, `key` 必须设置为消费者应用名;脚本语法支持多种,以 Dubbo Java SDK 为例,脚本语法支持 Javascript、Groovy、Kotlin 等,具体可参见每个语言实现的限制。
-
-> 脚本路由由于可以动态加载远端代码执行,因此存在潜在的安全隐患,在启用脚本路由前,一定要确保脚本规则在安全沙箱内运行。
-
-```yaml
-configVersion: v3.0
-key: demo-provider
-type: javascript
-enabled: true
-script: |
-  (function route(invokers,invocation,context) {
-      var result = new java.util.ArrayList(invokers.size());
-      for (i = 0; i < invokers.size(); i ++) {
-          if ("10.20.3.3".equals(invokers.get(i).getUrl().getHost())) {
-              result.add(invokers.get(i));
-          }
-      }
-      return result;
-  } (invokers, invocation, context)); // 表示立即执行方法
-```
-
-## ScriptRule
-脚本路由规则主体。定义脚本规则生效的目标消费者应用、流量过滤脚本以及一些特定场景下的行为。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| configVersion | string | The version of the script rule definition, currently available version is `v3.0` | Yes |
-| key | string | The identifier of the target application that this rule is about to apply to.| Yes |
-| type | string | The script language used to define `script`. | Yes |
-| enabled | bool | Whether enable this rule or not, set `enabled:false` to disable this rule. | Yes |
-| script | string | The script definition used to filter dubbo provider instances. | Yes |
-| force | bool | The behaviour when the instance subset is empty after after routing. `true` means return no provider exception while `false` means ignore this rule. | No |
-
-## Script
-`script` 为脚本路由规则的主体,类型为一个具有符合结构的 string 字符串,具体取决于 `type` 指定的脚本语言。
-
-以下是 `type: javascript` 的一个脚本规则示例:
-
-```javascript
-(function route(invokers,invocation,context) {
-      var result = new java.util.ArrayList(invokers.size());
-      for (i = 0; i < invokers.size(); i ++) {
-          if ("10.20.3.3".equals(invokers.get(i).getUrl().getHost())) {
-              result.add(invokers.get(i));
-          }
-      }
-      return result;
-  } (invokers, invocation, context)); // 表示立即执行方法
-```
diff --git a/content/zh-cn/overview/core-features/traffic/tag-rule.md b/content/zh-cn/overview/core-features/traffic/tag-rule.md
deleted file mode 100644
index 8d36a5fbaf5..00000000000
--- a/content/zh-cn/overview/core-features/traffic/tag-rule.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-aliases:
-    - /zh/overview/core-features/traffic/tag-rule/
-description: ""
-linkTitle: 标签路由
-title: 标签路由规则
-type: docs
-weight: 2
----
-
-
-
-标签路由通过将某一个服务的实例划分到不同的分组,约束具有特定标签的流量只能在指定分组中流转,不同分组为不同的流量场景服务,从而达到实现流量隔离的目的,可以作为蓝绿发布、灰度发布等场景能力的基础。目前有两种方式可以对实例打标,分别是`动态规则打标`和`静态规则打标`。`动态规则打标` 可以在运行时动态的圈住一组机器实例,而 `静态规则打标` 则需要实例重启后才能生效,其中,动态规则相较于静态规则优先级更高,而当两种规则同时存在且出现冲突时,将以动态规则为准。
-
-本文要讲的就是标签路由规则就是 `动态规则打标`。
-
-标签路由是一套严格隔离的流量体系,对于同一个应用而言,一旦打了标签则这部分地址子集就被隔离出来,只有带有对应标签的请求流量可以访问这个地址子集,这部分地址不再接收没有标签或者具有不同标签的流量。
-
-举个例子,如果我们将一个应用进行打标,打标后划分为 tag-a、tag-b、无 tag 三个地址子集,则访问这个应用的流量,要么路由到 tag-a (当请求上下文 dubbo.tag=tag-a),要么路由到 tag-b (dubbo.tag=tag-b),或者路由到无 tag 的地址子集 (dubbo.tag 未设置),不会出现混调的情况。
-
-标签路由的作用域是提供者应用,消费者应用无需配置标签路由规则。一个提供者应用内的所有服务只能有一条分组规则,不会有服务 A 使用一条路由规则、服务 B 使用另一条路由规则的情况出现。以下条件路由示例,在 `shop-detail` 应用中圈出了一个隔离环境 `gray`,`gray` 环境包含所有带有 `env=gray` 标识的机器实例。
-
-```yaml
-configVersion: v3.0
-force: true
-enabled: true
-key: shop-detail
-tags:
-  - name: gray
-    match:
-      - key: env
-        value:
-          exact: gray
-```
-## TagRule
-标签路由规则主体。定义路由规则生效的目标应用、标签分类规则以及一些特定场景下的行为。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| configVersion | string | The version of the tag rule definition, currently available version is `v3.0` | Yes |
-| key | string | The identifier of the target application that this rule is about to control| Yes |
-| enabled | bool | Whether enable this rule or not, set `enabled:false` to disable this rule. | Yes |
-| tags | Tag[] | The tag definition of this rule. | Yes |
-| force | bool | The behaviour when the instance subset is empty after routing. `true` means return no provider exception while `false` means fallback to subset without any tags. | No |
-| runtime | bool | Whether run routing rule for every rpc invocation or use routing cache if available. | No |
-
-## Tag
-标签定义,根据 `match` 条件筛选出一部分地址子集。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| name | string | The name of the tag used to match the `dubbo.tag` value in the request context. | Yes |
-| match | MatchCondition | A set of criterion to be met for instances to be classified as member of this tag.  | No |
-
-## MatchCondition
-定义实例过滤条件,根据 Dubbo URL 地址中的特定参数进行过滤。
-
-| Field | Type | Description | Required |
-| --- | --- | --- | --- |
-| key | string | The name of the key in the Dubbo url address. | Yes |
-| value | StringMatch (oneof) | The matching condition for the value in the Dubbo url address. | Yes |
diff --git a/content/zh-cn/overview/demo/_index.md b/content/zh-cn/overview/demo/_index.md
new file mode 100644
index 00000000000..52a64b0f67b
--- /dev/null
+++ b/content/zh-cn/overview/demo/_index.md
@@ -0,0 +1,6 @@
+---
+title: "Demo"
+layout: "shortcodes/blocks/demo-zh"
+toc_hide: true
+---
+  {{< blocks/demo-zh >}}
diff --git a/content/zh-cn/overview/home/_index.md b/content/zh-cn/overview/home/_index.md
index b247ff3189e..faa0410eae5 100644
--- a/content/zh-cn/overview/home/_index.md
+++ b/content/zh-cn/overview/home/_index.md
@@ -53,6 +53,7 @@ hide_feedback: true
 hide_summary: true
 linkTitle: 主页
 main_menu: true
+toc_hide: true
 menu:
     main:
         name: 文档
diff --git a/content/zh-cn/overview/mannual/_index.md b/content/zh-cn/overview/mannual/_index.md
index 3b6de506518..b2af438234a 100755
--- a/content/zh-cn/overview/mannual/_index.md
+++ b/content/zh-cn/overview/mannual/_index.md
@@ -9,7 +9,7 @@ feature:
     description: |
         提供 Java、Golang、Rust、Node.js、Python 等多语言 SDK 实现,支持基于 IDL 的跨语言服务定义和基于 Protobuf、Json 的数据编码
     title: 多语言 SDK
-linkTitle: SDK 用户手册
+linkTitle: 用户手册
 no_list: true
 title: Dubbo SDK 用户手册
 type: docs
@@ -40,7 +40,7 @@ weight: 6
         <div class="h-100 card shadow">
             <div class="card-body">
                 <h4 class="card-title">
-                    <a href='{{< relref "./golang-sdk" >}}'>Golang SDK</a>
+                    <a href='{{< relref "./golang-sdk" >}}'>Go SDK</a>
                 </h4>
                 <p>Dubbo Golang SDK 手册</p>
             </div>
@@ -50,9 +50,9 @@ weight: 6
         <div class="h-100 card shadow">
             <div class="card-body">
                 <h4 class="card-title">
-                    <a href='{{< relref "./erlang-sdk" >}}'>Erlang SDK</a>
+                    <a href='{{< relref "./nodejs-sdk" >}}'>Node.js</a>
                 </h4>
-                <p>Dubbo Erlang SDK 手册</p>
+                <p>Dubbo Node.js SDK 手册</p>
             </div>
         </div>
     </div>
@@ -60,9 +60,9 @@ weight: 6
         <div class="h-100 card shadow">
             <div class="card-body">
                 <h4 class="card-title">
-                    <a href='{{< relref "./dubbo-go-pixiu" >}}'>Dubbo Go Pixiu</a>
+                    <a href='{{< relref "./web-sdk" >}}'>Web SDK</a>
                 </h4>
-                <p>Dubbo Go Pixiu 手册</p>
+                <p>Dubbo Web SDK 手册</p>
             </div>
         </div>
     </div>
@@ -72,11 +72,10 @@ weight: 6
                 <h4 class="card-title">
                     <a href='{{< relref "./rust-sdk" >}}'>Rust SDK</a>
                 </h4>
-                <p>Rust SDK 手册</p>
+                <p>Dubbo Rust SDK 手册</p>
             </div>
         </div>
     </div>
-
 </div>
 <hr>
 </div>
diff --git a/content/zh-cn/overview/mannual/control-plane/_index.md b/content/zh-cn/overview/mannual/control-plane/_index.md
new file mode 100644
index 00000000000..8421fd1f3f8
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/_index.md
@@ -0,0 +1,10 @@
+---
+aliases:
+  - /zh/overview/reference/admin/
+  - /zh-cn/overview/reference/admin/
+description: ""
+linkTitle: 控制面
+title: Admin 控制台操作手册
+type: docs
+weight: 20
+---
diff --git a/content/zh-cn/overview/mannual/control-plane/architecture.md b/content/zh-cn/overview/mannual/control-plane/architecture.md
new file mode 100644
index 00000000000..d6b1eb5565b
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/architecture.md
@@ -0,0 +1,296 @@
+---
+aliases:
+  - /zh/overview/reference/admin/architecture/
+  - /zh-cn/overview/reference/admin/architecture/
+description: ""
+linkTitle: 架构与安装
+no_list: true
+title: Admin 整体架构与安装步骤
+type: docs
+weight: 1
+working_in_progress: true
+---
+
+回顾 [Dubbo 服务治理体系的总体架构](../../../what/overview/),Admin 是服务治理控制面中的一个核心组件,负责微服务集群的服务治理、可视化展示等。
+
+## Admin 部署架构
+
+![admin-core-components.png](/imgs/v3/reference/admin/admin-core-components.png)
+
+总体上来说,Admin 部署架构分为以下几个部分:
+* Admin 主进程,包括服务发现元数据管理、可视化控制台、安全认证策略管控、其他定制化服务治理能力等组件。
+* 强依赖组件,包括 Mysql 数据库、注册/配置/元数据中心(可以是 Kubernetes、Nacos、Zookeeper 等)
+* 可选依赖组件,包括 Prometheus、Grafana、Zipkin 等
+
+## 安装 Admin
+
+### Dubboctl 安装
+#### Download
+当前Dubboctl未正式发行,可按以下方式进行尝试。
+拉取Dubbo Admin并编译Dubboctl
+```shell
+git clone https://github.com/apache/dubbo-admin.git
+cd dubbo-admin/cmd/dubboctl
+go build -o dubboctl .
+```
+
+将 dubboctl 放入可执行路径
+```shell
+ln -s dubbo-admin/cmd/dubboctl/dubboctl /usr/local/bin/dubboctl
+```
+#### Install
+安装过程会依次:
+
+1. 将用户自定义的配置profile以及set参数覆盖于默认profile,得到最终的profile
+```yaml
+# default profile
+apiVersion: dubbo.apache.org/v1alpha1
+kind: DubboOperator
+metadata:
+  namespace: dubbo-system
+spec:
+  profile: default
+  namespace: dubbo-system
+  componentsMeta:
+    admin:
+      enabled: true
+    grafana:
+      enabled: true
+      repoURL: https://grafana.github.io/helm-charts
+      version: 6.52.4
+    nacos:
+      enabled: true
+    zookeeper:
+      enabled: true
+      repoURL: https://charts.bitnami.com/bitnami
+      version: 11.1.6
+    prometheus:
+      enabled: true
+      repoURL: https://prometheus-community.github.io/helm-charts
+      version: 20.0.2
+    skywalking:
+      enabled: true
+      repoURL: https://apache.jfrog.io/artifactory/skywalking-helm
+      version: 4.3.0
+    zipkin:
+      enabled: true
+      repoURL: https://openzipkin.github.io/zipkin
+      version: 0.3.0
+```
+建议使用自定义profile进行配置,在componentsMeta中开启或关闭组件,在components下配置各组件。其中components下各组件的配置值都是helm chart的values,各组件的具体配置请参考:
+Grafana: https://github.com/grafana/helm-charts/blob/main/charts/grafana/README.md
+Zookeeper: https://github.com/bitnami/charts/tree/main/bitnami/zookeeper/#installing-the-chart
+Prometheus: https://github.com/prometheus-community/helm-charts/tree/main/charts
+Skywalking: https://github.com/apache/skywalking-kubernetes/blob/master/chart/skywalking/README.md
+Zipkin: https://github.com/openzipkin/zipkin-helm
+```yaml
+# customization profile
+apiVersion: dubbo.apache.org/v1alpha1
+kind: DubboOperator
+metadata:
+  namespace: dubbo-system
+spec:
+  profile: default
+  namespace: dubbo-system
+  componentsMeta:
+    admin:
+      enabled: true
+    grafana:
+      enabled: true
+      version: 6.31.0
+    prometheus:
+      enabled: false
+  components:
+    admin:
+      replicas: 3
+    grafana:
+      testFramework:
+        enabled: false
+```
+2. 根据profile拉取所需组件并生成manifest,目前Admin,Nacos已在本地,无需拉取;Grafana,Zookeeper,Prometheus,Skywalking,Zipkin将从官方chart库拉取,具体地址和版本可见上方default profile
+3. 将manifest应用于k8s集群
+```shell
+dubboctl manifest install # 使用默认 manifests 安装
+
+# or
+
+dubboctl manifest generate | kubectl apply -f -
+```
+
+```shell
+dubboctl install --set spec.components.admin.replicas=2 # 设置组件的配置
+```
+
+```shell
+dubboctl install --set spec.componentsMeta.admin.enabled=true, spec.componentsMeta.grafana.enabled=false
+# 开启或关闭组件
+```
+
+```shell
+dubboctl install --set spec.componentsMeta.grafana.repoURL=https://grafana.github.io/helm-charts, spec.componentsMeta.grafana.version=6.31.0
+# 设置需远程拉取组件的仓库地址与版本
+```
+
+检查安装效果
+```shell
+kubectl get pod -n dubbo-system
+```
+
+#### 打开 Admin 控制台
+```shell
+kubectl port-forward svc/dubbo-admin -n dubbo-system 38080:38080
+```
+
+打开浏览器,访问: `http://127.0.0.1:38080/`
+
+### Helm 安装
+
+获取图表
+```
+helm repo add https://charts.bitnami.com/bitnami
+helm repo add https://prometheus-community.github.io/helm-charts
+helm repo add https://grafana.github.io/helm-charts
+helm repo add https://apache.jfrog.io/artifactory/skywalking-helm
+helm repo add https://openzipkin.github.io/zipkin
+```
+安装 zookeeper
+```bash
+helm install zookeeper bitnami/zookeeper -n dubbo-system
+```
+
+安装 prometheus
+```bash
+helm install prometheus prometheus-community/prometheus -n dubbo-system
+```
+
+安装 grafana
+```bash
+helm install grafana grafana/grafana -n dubbo-system
+```
+
+安装 skywalking
+```bash
+helm install skywalking skywalking/skywalking -n dubbo-system
+```
+
+安装 zipkin
+```
+helm install zipkin openzipkin/zipkin -n dubbo-system
+```
+
+检查安装状态
+```shell
+helm ls -n dubbo-system ;kubectl get pods -n dubbo-system --output wide
+```
+
+### VM 安装
+#### Download
+下载 Dubbo Admin 发行版本
+```shell
+curl -L https://dubbo.apache.org/installer.sh | VERSION=0.1.0 sh -
+# Admin 要组织好发行版本
+```
+
+将 dubboctl 放入可执行路径
+```shell
+ln -s dubbo-admin-0.1.0/bin/dubbo-admin /usr/local/bin/dubbo-admin
+```
+#### Run
+```shell
+dubbo-admin run -f override-configuration.yml
+```
+## 配置手册 (Configuration)
+配置用于控制 dubbo-admin 的行为
+
+
+```yaml
+# Environment type. Available values are: "kubernetes" or "universal"
+environment: universal # ENV: DUBBO_ENVIRONMENT
+# Mode in which Dubbo CP is running. Available values are: "standalone", "global", "zone"
+mode: standalone # ENV: DUBBO_MODE
+
+# Resource Store configuration
+store:
+  # Type of Store used in the Control Plane. Available values are: "kubernetes", "postgres" or "memory"
+  type: memory # ENV: DUBBO_STORE_TYPE
+
+  # Kubernetes Store configuration (used when store.type=kubernetes)
+  kubernetes:
+    # Namespace where Control Plane is installed to.
+    systemNamespace: dubbo-system # ENV: DUBBO_STORE_KUBERNETES_SYSTEM_NAMESPACE
+
+  # Postgres Store configuration (used when store.type=postgres)
+  mysql:
+    # Host of the Postgres DB
+    host: 127.0.0.1 # ENV: DUBBO_STORE_POSTGRES_HOST
+    # Port of the Postgres DB
+    port: 15432 # ENV: DUBBO_STORE_POSTGRES_PORT
+    # User of the Postgres DB
+    user: dubbo # ENV: DUBBO_STORE_POSTGRES_USER
+    # Password of the Postgres DB
+    password: dubbo # ENV: DUBBO_STORE_POSTGRES_PASSWORD
+    # Database name of the Postgres DB
+    dbName: dubbo # ENV: DUBBO_STORE_POSTGRES_DB_NAME
+    # Connection Timeout to the DB in seconds
+    connectionTimeout: 5 # ENV: DUBBO_STORE_POSTGRES_CONNECTION_TIMEOUT
+    # Maximum number of open connections to the database
+    # `0` value means number of open connections is unlimited
+    maxOpenConnections: 50 # ENV: DUBBO_STORE_POSTGRES_MAX_OPEN_CONNECTIONS
+    # Maximum number of connections in the idle connection pool
+    # <0 value means no idle connections and 0 means default max idle connections
+    maxIdleConnections: 50  # ENV: DUBBO_STORE_POSTGRES_MAX_IDLE_CONNECTIONS
+    # TLS settings
+    tls:
+      # Mode of TLS connection. Available values are: "disable", "verifyNone", "verifyCa", "verifyFull"
+      mode: disable # ENV: DUBBO_STORE_POSTGRES_TLS_MODE
+      # Path to TLS Certificate of the client. Used in verifyCa and verifyFull modes
+      certPath: # ENV: DUBBO_STORE_POSTGRES_TLS_CERT_PATH
+      # Path to TLS Key of the client. Used in verifyCa and verifyFull modes
+      keyPath: # ENV: DUBBO_STORE_POSTGRES_TLS_KEY_PATH
+      # Path to the root certificate. Used in verifyCa and verifyFull modes.
+      caPath: # ENV: DUBBO_STORE_POSTGRES_TLS_ROOT_CERT_PATH
+    # MinReconnectInterval controls the duration to wait before trying to
+    # re-establish the database connection after connection loss. After each
+    # consecutive failure this interval is doubled, until MaxReconnectInterval
+    # is reached. Successfully completing the connection establishment procedure
+    # resets the interval back to MinReconnectInterval.
+    minReconnectInterval: "10s" # ENV: DUBBO_STORE_POSTGRES_MIN_RECONNECT_INTERVAL
+    # MaxReconnectInterval controls the maximum possible duration to wait before trying
+    # to re-establish the database connection after connection loss.
+    maxReconnectInterval: "60s" # ENV: DUBBO_STORE_POSTGRES_MAX_RECONNECT_INTERVAL
+server:
+	port: 38080
+registry:
+  address: xxx
+metadata-center:
+  address: xxx
+config-center:
+	address: xxx
+external-services:
+  prometheus:
+      # Prometheus service name is "metrics" and is in the "telemetry" namespace
+		  # http://prometheus.<dubbo_namespace_name>:9090
+      url: "http://metrics.telemetry:9090/"
+  tracing:
+    # Enabled by default. Kiali will anyway fallback to disabled if
+    # Jaeger is unreachable.
+    enabled: true
+    # Jaeger service name is "tracing" and is in the "telemetry" namespace.
+    # Make sure the URL you provide corresponds to the non-GRPC enabled endpoint
+    # if you set "use_grpc" to false.
+    in_cluster_url: 'http://tracing.telemetry:16685/jaeger'
+    use_grpc: true
+    # Public facing URL of Jaeger
+    url: 'http://my-jaeger-host/jaeger'
+	grafana:
+      enabled: true
+      # Grafana service name is "grafana" and is in the "telemetry" namespace.
+      in_cluster_url: 'http://grafana.telemetry:3000/'
+      # Public facing URL of Grafana
+      url: 'http://my-ingress-host/grafana'
+
+# 更多配置
+```
+#### 打开 Admin 控制台
+
+打开浏览器,访问: `http://127.0.0.1:38080/`
diff --git a/content/zh-cn/overview/mannual/control-plane/documentation.md b/content/zh-cn/overview/mannual/control-plane/documentation.md
new file mode 100644
index 00000000000..e05ebf8b72f
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/documentation.md
@@ -0,0 +1,17 @@
+---
+aliases:
+  - /zh/overview/reference/admin/documentation/
+  - /zh-cn/overview/reference/admin/documentation/
+description: ""
+linkTitle: 文档管理
+no_list: true
+toc_hide: true
+title: Admin 文档管理功能介绍
+type: docs
+weight: 6
+working_in_progress: true
+---
+
+// TBD
+
+
diff --git a/content/zh-cn/overview/mannual/control-plane/mock.md b/content/zh-cn/overview/mannual/control-plane/mock.md
new file mode 100644
index 00000000000..582960435e7
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/mock.md
@@ -0,0 +1,176 @@
+---
+aliases:
+  - /zh/overview/reference/admin/mock/
+  - /zh-cn/overview/reference/admin/mock/
+description: ""
+linkTitle: 服务Mock
+no_list: true
+title: Admin 服务 Mock 功能简介
+type: docs
+weight: 4
+working_in_progress: true
+---
+
+Mock 功能是设计用来提升微服务研发与测试效率的,它可以短路 Consumer 侧发起的远程调用,提前返回预先设定好的 Mock 值,这样即使在没有 Provider 可用的情况下,消费端也能正常的推进开发、测试进程。除此之外,mock 也可用于快速模拟负责返回值的测试数据、模拟服务端异常等场景
+
+需要注意的是,Mock 能力仅限用于测试环境,应避免将其用于生产环境。
+
+# 设计背景
+在跨团队或是多应用开发时,在前期开发中往往会出现依赖的服务还未开发完成的情况,这样就会导致流程的阻塞,影响研发效率。基于这种情况,Dubbo Admin 提供了 mock 能力来解耦 Consumer 与 Provider 之间的依赖,以确保在 Provider 未就绪的情况下 Consumer 仍能正常开展测试,提高研发效率。
+
+Dubbo 框架本身设计有服务降级(有时也称为 mock)能力,通过配置 `org.apache.dubbo.config.ReferenceConfig` 的 mock 字段(可设置为true或是对应接口的Mock实现)或动态配置规则,此时就可以启动服务降级能力。这种服务降级能力是为生产环境的限流降级准备的,虽然也可以用于本地开发测试场景,但灵活度并不高,基于提升开发效率的根本诉求,我们设计了基于 Admin 的服务降级能力。
+
+Dubbo Admin 服务 mock 是一种更为轻量和便捷实现方式,主要用于开发测试阶段的,目标是提升微服务场景下的整体研发效率。需求详见:[Dubbo Admin Mock需求](https://github.com/apache/dubbo-admin/issues/757)。
+
+## 架构设计
+
+![admin-mock-architecture.png](/imgs/v3/reference/admin/console/mock-architecture.png)
+
+**实现 Mock 能力,Dubbo 框架与 Admin 侧要支持的能力**
+
+* Dubbo Admin
+    * 规则管理
+        * 规则新增
+        * 规则查询
+        * 规则修改
+        * 规则删除
+    * 请求历史记录
+    * Mock 请求数据查询
+    * MockService Provider
+        * 根据规则生成 Mock 数据
+        * 响应 Consumer Mock 请求
+        * 保存请求和返回数据
+* Dubbo
+    * 根据 mock 开关配置,转发请求到 Admin 注册的 MockService
+    * 处理 mock 返回值并转换为匹配方法签名的强类型数据
+
+**Mock 请求原理时序图**
+
+![admin-mock-workflow.png](/imgs/v3/reference/admin/console/mock-workflow.png)
+
+## 使用方式
+
+1. 在 Consumer 应用中添加依赖
+
+    开启 Mock 前,请确保在消费端应用中引入以下依赖:
+
+    ```xml
+    <dependency>
+      <groupId>org.apache.dubbo.extensions</groupId>
+      <artifactId>dubbo-mock-admin</artifactId>
+      <version>${version}</version>
+    </dependency>
+    ```
+
+    > 查看 [dubbo-mock-admin 的可用版本](/zh-cn/download/spi-extensions/)
+
+2. 配置 `-Denable.dubbo.admin.mock=true` 参数开启 Mock 并重启进程
+3. 打开 Admin 配置 Mock 规则
+
+    用户可以通过在控制台上指定需要被 mock 的消费端IP、服务名和方法和具体的 mock 行为,实现对调用结果的 mock。
+
+    ![admin-mock](/imgs/v3/reference/admin/console/mock-rule-screenshot.png)
+
+    一些支持的规则类型与示例
+
+    ```
+    数字类型:123
+
+    字符串:"hello, world!"
+
+    数组、列表:[1, 2, 3]
+
+    枚举:"ENUM_TYPE"
+
+    Map、对象:
+      {
+        "prop1": "value1",
+        "prop2": ["a", "b", "c"]
+      }
+
+    null: null
+    ```
+
+4. 此时,消费端再次发起远程调用,就会得到预期 Mock 返回值。
+
+    > 注意事项
+    > 1. Mock 仅限用于测试开发环境,因此为了确保核心依赖的稳定性,社区没有将 mock 组件打包在核心框架包中,用户可以自行决策是否将其作为应用的默认依赖在公司内推广
+    > 2. 即使添加了 mock 二进制依赖,mock 功能也不会默认开启,需要设置 `-Denable.dubbo.admin.mock=true` 后才能开启。
+
+## 实现原理
+
+Consumer 调用发起的调用会被本地的 MockServiceFilter 拦截,如果 mock 开关开启,则 MockServiceFilter 将请求转发到 MockService (由 Dubbo Admin 发布的服务),MockService 根据请求的服务、方法等查询用户预先配置的 mock 规则,如果查询到则返回规则中的 mock 值,Consumer 收到 mock 值后调用成功返回。
+
+### Mock 返回值如何定义?
+
+当前 Admin 支持录入 JSON 或者基本类型数据,如:
+
+* 返回数字值 (当方法签名返回值是数字类型)
+
+```
+123
+```
+
+* 返回字符串 (当方法签名返回值是字符串类型)
+```
+"hello, world!"
+```
+
+* 返回 JSON (当方法签名返回值是 Map 或对象类型)
+```
+{
+    "prop1": "value1",
+    "prop2": ["a", "b", "c"]
+}
+```
+
+* 返回数组 (当方法签名返回值是数组或列表)
+```
+[1, 2, 3]
+```
+
+### 消费端如何发起 MockService 调用?
+
+`dubbo-mock-admin` 将为消费端引入 MockServiceFilter 请求拦截器,如果用户打开 mock 开关,那么 Filter 会将请求转发到 Admin MockService 服务。
+
+### Mock 值如何转换为原始类型值?
+
+MockService 支持返回标准 JSON 格式或者基本类型数据,消费端会基于 Dubbo 内置类型转换器将 JSON 等值转为原始对象类型。
+
+### 未来优化点
+* 保存 Mock 开关到配置中心,用户可以通过 Admin 动态控制开关。
+* 开启 Mysql 数据库链接池
+
+### 表结构设计
+Admin 依赖 Mysql 数据库存储用户配置的 mock 规则,具体的表结构设计如下。
+
+#### Mock Rule
+
+```sql
+CREATE TABLE `mock_rule` (
+  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT '主键',
+  `service_name` varchar(255) DEFAULT NULL COMMENT '服务名',
+  `method_name` varchar(255) DEFAULT NULL COMMENT '方法名',
+  `rule` text NULL DEFAULT COMMENT '规则',
+  `created_at` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间',
+  `updated_at` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '更新时间',
+  PRIMARY KEY (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='服务mock方法表';
+```
+#### Mock Log
+
+```sql
+CREATE TABLE `mock_log` (
+  `id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT '主键id',
+  `method_id` int(11) DEFAULT NULL COMMENT '规则id',
+  `request` text COMMENT '请求数据',
+  `response` text COMMENT '返回值',
+  `created_at` datetime DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间',
+  `updated_at` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '更新时间',
+  PRIMARY KEY (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='mock请求记录表';
+```
+
+
+
+
diff --git a/content/zh-cn/overview/mannual/control-plane/search.md b/content/zh-cn/overview/mannual/control-plane/search.md
new file mode 100644
index 00000000000..031f5289c8b
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/search.md
@@ -0,0 +1,55 @@
+---
+aliases:
+  - /zh/overview/reference/admin/search/
+  - /zh-cn/overview/reference/admin/search/
+description: ""
+linkTitle: 文档查询
+title: Admin 服务查询
+type: docs
+weight: 2
+working_in_progress: true
+---
+
+Admin 支持可视化的展示 Dubbo 微服务集群的状态,方便用户从全局掌握集群的应用、服务和实例分布,Admin 还可以通过查询的方式了解某一个服务更详细的信息:
+* 首页集群大盘,展示集群应用、服务、示例的总体分布,集群总体流量情况等
+* 支持根据应用名、服务名(可包含版本&分组)、实例 IP 查询详细信息
+* 支持服务名/应用名的自动补全
+* 支持查看单条服务实例的详情
+
+## 首页大盘
+
+![admin-dashboard](/imgs/v3/reference/admin/console/dashboard.png)
+
+## 根据 Dubbo 服务名查询
+
+精确输入`接口名:版本` 查询服务
+
+![admin-search-service](/imgs/v3/reference/admin/console/admin-search-service.png)
+
+通过 `*` 通配符模糊查询服务
+
+![admin-search-service2](/imgs/v3/reference/admin/console/admin-search-service.png)
+
+## 根据应用名查询
+
+输入应用名查询某应用关联的所有服务(包含提供和消费的服务)
+
+![admin-search-application](/imgs/v3/reference/admin/console/admin-search-application.png)
+
+## 根据实例 IP 名查询
+
+输入实例 IP 查询某实例关联的所有服务(包含提供和消费的服务)
+
+![admin-search-ip](/imgs/v3/reference/admin/console/admin-search-ip.png)
+
+> 支持基于端口过滤服务
+
+## 查看服务实例详情
+
+在服务列表点击 `详情` 查看服务详细情况
+
+![admin-search-service-detail](/imgs/v3/reference/admin/console/admin-search-service-detail.png)
+
+
+
+
diff --git a/content/zh-cn/overview/mannual/control-plane/test.md b/content/zh-cn/overview/mannual/control-plane/test.md
new file mode 100644
index 00000000000..ce4a83b3356
--- /dev/null
+++ b/content/zh-cn/overview/mannual/control-plane/test.md
@@ -0,0 +1,193 @@
+---
+aliases:
+   - /zh/overview/reference/admin/test/
+   - /zh-cn/overview/reference/admin/test/
+description: ""
+linkTitle: 服务测试
+no_list: true
+title: Admin 服务测试功能简介
+type: docs
+weight: 3
+working_in_progress: true
+---
+
+服务测试功能通常提供给 Dubbo 服务的开发者使用,用来对自己发布的服务进行自测。通过在 Admin 控制台上模拟真实的消费端进程,对服务提供者发起调用,并验证调用结果是否符合预期。
+
+## 使用方式
+
+### 准备用例
+1. 启动用例
+
+    可以参考 [快速开始](../../../quickstart/java/) 启动一个简单的 Dubbo 服务,对于服务测试来说,只需要启动 provider 即可。
+
+2. 查询服务
+
+    完成服务端部署后,可以到 Admin 的 `服务测试` 页面查询对应的服务:
+
+    ![testSearch](/imgs/blog/admin/testSearch.jpg)
+
+    这里的信息和元数据类似,包含方法名,参数类型和返回值信息,点击右边的标签就可以进入服务测试页面
+
+### 执行服务测试
+
+服务测试页面包含了两个 json 编辑器,参数类型的信息都是以 json 格式保存。
+
+如以下示例所示,在左侧编辑器中填入对应的参数值(本例中数类型是 `String` ),填写完成后点击 `执行` 即可对服务端发起调用,调用结果展示在右边的编辑器中。
+
+![testSuccess](/imgs/blog/admin/testSuccess.jpg)
+
+如果调用失败,会显示详细的失败原因,下面来看一下调用失败的例子:
+
+![testFail](/imgs/blog/admin/testFail.jpg)
+
+本例中,先关掉 Dubbo 服务提供者的进程,再执行服务测试,可以看到返回的结果是`找不到服务提供者`的异常。和普通调用一样,业务和框架的异常都会返回在结果中,方便业务排查。
+
+### 复合类型参数的填写
+
+考虑 `UserService` 中的以下方法和类型:
+
+```java
+//org.apache.dubbo.demo.api.UserService
+Result getUser(String name, UserInfoDO userInfoDO);
+```
+```java
+public class UserInfoDO {
+    private int id;
+    private LocationDO locationDO;
+    private DepartmentDO departmentDO;
+
+    @Override
+    public String toString() {
+        return "UserInfoDO{" +
+                "id=" + id +
+                ", locationDO=" + locationDO.toString() +
+                ", departmentDO=" + departmentDO.toString() +
+                '}';
+    }
+}
+```
+
+```java
+public class DepartmentDO {
+
+    private String departName;
+    private LocationDO departLocation;
+
+    @Override
+    public String toString() {
+        return "DepartmentDO{" +
+                "departName='" + departName + '\'' +
+                ", departLocation=" + departLocation.toString() +
+                '}';
+    }
+}
+```
+
+```java
+public class LocationDO {
+    private String address;
+    private int postNum;
+
+    @Override
+    public String toString() {
+        return "LocationDO{" +
+                "address='" + address + '\'' +
+                ", postNum=" + postNum +
+                '}';
+    }
+}
+```
+参数是比较复杂的符合类型参数,服务测试的时候,会逐层展开填写每一个field的值,如下图所示:
+![complex](/imgs/blog/admin/complex.jpg)
+同样可以调用成功并且返回结果
+
+## 原理
+
+### 数据来源
+
+服务测试中,最重要的就是完整的方法签名信息,和参数的类型信息,有了这些信息才能够一步步填入每个参数的值,拼装出完整的服务消费者。因此,使用服务测试的前提是在 Dubbo 中开启元数据中心(默认开启,Zookeeper、Nacos、Redis 等默认以注册中心做为元数据中心),Dubbo Admin 的方法签名和参数类型信息就是元数据中心来的:
+
+![medatada](/imgs/blog/admin/metadata.png)
+
+如图所示,服务端在运行的时候会将服务的元数据信息注册到元数据中心,格式如下:
+
+```json
+{
+    ...
+    "methods": [
+        {
+            "name": "sayHello",
+            "parameterTypes": [
+                "org.apache.dubbo.demo.model.User"
+            ],
+            "returnType": "org.apache.dubbo.demo.model.Result"
+        },
+      ...
+    ],
+    "types": [
+        {
+            "type": "char"
+        },
+        {
+            "type": "long"
+        },
+        {
+            "type": "org.apache.dubbo.demo.model.Result",
+            "properties": {
+                "msg": {
+                    "type": "java.lang.String",
+                    "properties": {
+                        "value": {
+                            "type": "char[]"
+                        },
+                        "hash": {
+                            "type": "int"
+                        }
+                    }
+                },
+                "userName": {
+                    "type": "java.lang.String",
+                    "properties": {
+                        "value": {
+                            "type": "char[]"
+                        },
+                        "hash": {
+                            "type": "int"
+                        }
+                    }
+                }
+            }
+        },
+        {
+            "type": "org.apache.dubbo.demo.model.User",
+            "properties": {
+                "id": {
+                    "type": "java.lang.Long",
+                    "properties": {
+                        "value": {
+                            "type": "long"
+                        }
+                    }
+                },
+                "username": {
+                    "type": "java.lang.Sring",
+                    "properties": {
+                        "value": {
+                            "type": "char[]"
+                        },
+                        "hash": {
+                            "type": "int"
+                        }
+                    }
+                }
+            }
+        },
+       ...
+    ]
+}
+```
+与服务测试相关的就是`methods`和`types`所包含的方法和类型信息,Dubbo Admin根据这些信息,将参数渲染到服务测试页面的Json Editor中,由用户来输入每个参数,每个成员变量的值。
+
+### 泛化调用
+
+有了参数类型,下一个问题就是怎么能够调用到服务端,在传统的Dubbo RPC调用中,客户端需要依赖服务端的API jar包 (参考 [Quick Start](https://github.com/apache/dubbo-samples/tree/master/1-basic/dubbo-samples-spring-boot/dubbo-samples-spring-boot-consumer) 中的消费端示例,这对于 Dubbo Admin 来说不太可能,因为服务的上下线是动态的,Dubbo Admin 无法动态增加 jar 包依赖,因此需要用到 Dubbo 中的[**泛化调用**](../../../mannual/java-sdk/advanced-features-and-usage/service/generic-reference/),指的是在没有服务端API接口的情况下,客户端直接通过 `GenericService` 接口来发起服务调用,返回值中的数据对象都用Map来表示。泛化调用在服务端不需要做特殊处理,只需要客户端发起即可。
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/_index.md
deleted file mode 100755
index ffc0955c447..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/
-description: Dubbo Go Pixiu
-linkTitle: Dubbo Go Pixiu
-title: Dubbo Go Pixiu
-type: docs
-weight: 3
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/_index.md
deleted file mode 100755
index 498afec54a5..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/dev/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/dev/
-description: 开发者指南
-linkTitle: 开发者指南
-title: 开发者指南
-type: docs
-weight: 30
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/dubbo-pilot.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/dubbo-pilot.md
deleted file mode 100644
index d58402f5ea4..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/dubbo-pilot.md
+++ /dev/null
@@ -1,201 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/dev/dubbo-pilot/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/dev/dubbo-pilot/
-description: dubbo-pilot Control Plane 部署
-linkTitle: dubbo-pilot Control Plane 部署
-title: dubbo-pilot Control Plane 部署
-type: docs
-weight: 2
----
-
-
-
-
-
-
-* [1.总体目标](#target)
-* [2.基本流程](#basic)
-* [3.详细步骤](#detail)
-    + [3.1 环境要求](#env)
-    + [3.2 istio 本地部署](#native_deploy)
-        - [3.2.1 编译](#nbuild)
-        - [3.2.2 部署 & debug](#ndeploy)
-    + [3.3 istio 容器部署](#docker_deploy)
-        - [3.3.1 编译](#dbuild)
-        - [3.3.2 部署 & debug](#ddeploy)
-<h2 id="target">1 总体目标</h2>
-
-* 控制面编译和镜像构建
-* 使用 istioctl 在 kubernetes 环境部署
-* 如何对控制面程序 debug
-
-
-
-<h2 id="basic">2 基本流程</h2>
-这个例子将演示如何在编译 dubbo-pilot 控制平面并在 kubernetes 环境下如何使用 istioctl 进行部署
-
-1. 本地启动控制平面,对 dubbo-pilot 进行启动和 debug
-2. 使用 istioctl 在 k8s 环境启动和 debug 
-
-
-<h2 id="detail">3 详细步骤</h2>
-<h3 id="env">3.1 环境要求</h3>
-
-* Golang
-* Docker
-* Minikube/Kind
-* Kubectl
-* Dlv
-
-
-<h3 id="native_deploy">3.2 本地部署</h3>
-<h4 id="nbuild">3.2.1 编译</h4>
-
-1. 编译 docker-builder
-```
-cd dubbo-go-pixiu/tools/docker-builder && go install
-
-docker-builder -h:
-
-Builds Istio docker images
-
-Usage:
-   [flags]
-
-Flags:
-      --architecures strings   architectures to build (default [linux/amd64])
-      --base-version string    base version to use (default "latest")
-      --builder string         type of builder to use. options are crane or docker (default "docker")
-  -h, --help                   help for this command
-      --hub strings            docker hub(s) (default [localhost:5000])
-      --istio-version string   istio version to use (default "1.14-dev")
-      --kind-load              kind cluster to load into
-      --no-cache               disable caching
-      --no-clobber             do not allow pushing images that already exist
-      --proxy-version string   proxy version to use (default "7ae8e27f274b33dc2f4d83100aea5971ed6698d3")
-      --push                   push targets to registry
-      --save                   save targets to tar.gz
-      --tag strings            docker tag(s) (default [latest])
-      --targets strings        targets to build (default [app,app_sidecar_centos_7,app_sidecar_debian_11,app_sidecar_ubuntu_jammy,app_sidecar_ubuntu_xenial,ext-authz,install-cni,istioctl,operator,pilot,proxyv2])
-      --variants strings       variants to build (default [default])
-      --version                show build version
-```
-
-2. 使用 docker-builder 自动编译 && 构建镜像
-
-编译 istioctl
-```
-docker-builder --targets istioctl
-
-编译完成:
-
-ls  out/linux_amd64/
-istioctl  logs  pilot-agent  pilot-discovery
-```
-
-编译 dubbo-pilot 并推送到私有镜像仓库
-```
-tools/docker-builder/docker-builder --targets pilot --hub docker.io/bobtthp --push
-```
-
-
-<h4 id="ndeploy">3.2.2 本地部署</h4>
-
-本地启动方式:
-```
-./out/linux_amd64/pilot-discovery
-
-启动日志:
-2022-09-24T15:31:56.751245Z	info	FLAG: --caCertFile=""
-2022-09-24T15:31:56.751277Z	info	FLAG: --clusterAliases="[]"
-2022-09-24T15:31:56.751280Z	info	FLAG: --clusterID="Kubernetes"
-2022-09-24T15:31:56.751282Z	info	FLAG: --clusterRegistriesNamespace="istio-system"
-2022-09-24T15:31:56.751284Z	info	FLAG: --configDir=""
-2022-09-24T15:31:56.751286Z	info	FLAG: --ctrlz_address="localhost"
-2022-09-24T15:31:56.751289Z	info	FLAG: --ctrlz_port="9876"
-2022-09-24T15:31:56.751291Z	info	FLAG: --domain="cluster.local"
-...
-2022-09-24T15:31:56.753814Z	info	initializing mesh configuration ./etc/istio/config/mesh
-```
-
-<h3 id="docker_deploy">3.3 容器部署</h3>
-
-<h4 id="dbuild">3.3.1 镜像构建</h4>
-
-构建远程 debug 镜像
-
-1. 下载 dlv
-```
-git clone https://github.com/go-delve/delve.git
-make install
-
-which dlv
-/root/go/bin/dlv
-```
-
-2. Dockerfile 增加dlv dubbo-go-pixiu/pilot/docker/Dockerfile.pilot:
-```
-COPY ${TARGETARCH:-amd64}/dlv /usr/local/bin/dlv
-```
-
-3. 拷贝 dlv 至镜像挂载目录中:
-```
-cp /root/go/bin/dlv out/linux_amd64/dockerx_build/build.docker.pilot/amd64/
-```
-
-4. debug 镜像构建并推送:
-```
-docker-builder --targets pilot --hub docker.io/bobtthp --push --tag debug
-```
-
-5. 本地也可以查看镜像构建情况:
-
-```
-[root~master-1] /tmp/dubbo-go-pixiu/tools/docker-builder> docker images
-REPOSITORY                                                        TAG                                               IMAGE ID       CREATED             SIZE
-bobtthp/pilot                                                     latest                                            7b1aadd55120   13 minutes ago      262MB
-```
-
-
-
-<h4 id="ddeploy">3.3.2 部署</h4>
-
-1. 使用刚构建的镜像部署:
-```
-out/linux_amd64/istioctl --set .values.pilot.image=bobtthp/pilot:debug install
-```
-
-2. 查看部署情况:
-```
-[root~master] /tmp/dubbo-go-pixiu/tools/docker-builder> kubectl  get po -n istio-system
-NAME                    READY   STATUS    RESTARTS   AGE
-istiod-fd5d9f77-2ncjq   1/1     Running   0          18m
-```
-
-
-3. 进入容器远程 debug:
-```
-[root~master-1] /tmp/dubbo-go-pixiu> kubectl  exec -it -n istio-system istiod-fd5d9f77-2ncjq bash
-kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
-```
-
-4. 启动 dlv:
-```
-istio-proxy@istiod-fd5d9f77-2ncjq:/$ dlv --listen=:8015 --headless=true --api-version=2 --log attach `ps -ef |grep pilot-discovery| awk '{print $2}'`
-2022-11-04T15:43:14Z error layer=debugger could not create config directory: mkdir /home/istio-proxy/.config: read-only file system
-API server listening at: [::]:8015
-2022-11-04T15:43:14Z warning layer=rpc Listening for remote connections (connections are not authenticated nor encrypted)
-2022-11-04T15:43:14Z info layer=debugger attaching to pid 1
-```
-
-
-5. 对外暴露端口:
-
-```
-[root~master-1] /tmp> kubectl  port-forward -n istio-system istiod-fd5d9f77-2ncjq 8015:8015
-Forwarding from 127.0.0.1:8015 -> 8015
-Forwarding from [::1]:8015 -> 8015
-```
-
-6. 可以进行远程调试
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/filter-extension.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/filter-extension.md
deleted file mode 100644
index f6f857d5f16..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/filter-extension.md
+++ /dev/null
@@ -1,141 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/dev/filter-extension/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/dev/filter-extension/
-description: Pixiu Filter体系介绍
-linkTitle: Pixiu Filter体系介绍
-title: Pixiu Filter体系介绍
-type: docs
-weight: 1
----
-
-
-
-
-
-
-## **怎样编写一个Filter**
-`更详细的信息,请移步Blog《谈谈Pixiu的Filter》`
-
-我们来尝试写一个简单的Filter,这个Filter将会有简单的配置,在Decode阶段把请求的Body Log出来,并翻转后作为Mock的返回值。最后在Encode阶段根据配置把返回值Log出来。
-
-1.首先创建一个Filter
-
-```go
-type DemoFilter struct {
-   logPrefix string
-}
-
-// Decode阶段,发生在调用Upstream之前
-func (f *DemoFilter) Decode(ctx *contexthttp.HttpContext) filter.FilterStatus {
-   body, _ := ioutil.ReadAll(ctx.Request.Body)
-   logger.Infof("request body: %s", body)
-
-   //reverse res str
-   runes := []rune(string(body))
-   for i := 0; i < len(runes)/2; i += 1 {
-      runes[i], runes[len(runes)-1-i] = runes[len(runes)-1-i], runes[i]
-   }
-   reverse := string(runes)
-
-   //mock response
-   ctx.SendLocalReply(200, []byte(reverse))
-   return filter.Stop
-}
-
-// Encode阶段,此时可以获取到Upstream的Response
-func (f *DemoFilter) Encode(ctx *contexthttp.HttpContext) filter.FilterStatus {
-   res := ctx.SourceResp.(string)
-   logger.Infof("%s: %s", f.logPrefix, res)
-   return filter.Continue
-}
-```
-
-2.创建Filter Factory
-
-```go
-type (
-	DemoFilterFactory struct {
-		conf *Config
-	}
-	// Config describe the config of Filter
-	Config struct {
-		LogPrefix string `yaml:"logPrefix,omitempty"`
-	}
-)
-
-func (f *DemoFilterFactory) PrepareFilterChain(ctx *contexthttp.HttpContext, chain filter.FilterChain) error {
-   demo := &DemoFilter{logPrefix: f.conf.LogPrefix}
-
-   chain.AppendDecodeFilters(demo)
-   chain.AppendEncodeFilters(demo)
-   return nil
-}
-
-func (f *DemoFilterFactory) Config() interface{} {
-   return f.conf
-}
-
-func (f *DemoFilterFactory) Apply() error {
-   return nil
-}
-```
-
-3.创建Filter Plugin,并注册自己
-
-```go
-//important
-func init() {
-   filter.RegisterHttpFilter(&Plugin{})
-}
-
-type Plugin struct {
-}
-
-func (p *Plugin) Kind() string {
-   return "dgp.filters.demo"
-}
-
-func (p *Plugin) CreateFilterFactory() (filter.HttpFilterFactory, error) {
-	return &DemoFilterFactory{conf: &Config{}}, nil
-}
-```
-
-4.配置文件中配置此Filter,并启动Pixiu
-
-```yaml
-static_resources:
-  listeners:
-    - name: "net/http"
-      protocol_type: "HTTP"
-      address:
-        socket_address:
-          address: "0.0.0.0"
-          port: 8888
-      filter_chains:
-          filters:
-            - name: dgp.filter.httpconnectionmanager
-              config:
-                route_config:
-                  routes:
-                    - match:
-                        prefix: "/"
-                http_filters:
-                  - name: dgp.filters.demo
-                    config:
-```
-
-5.访问并查看日志与结果
-
-```shell
-curl localhost:8888/demo -d "eiv al tse’c"
-
-c’est la vie% 
-```
-
-日志
-
-```
-2022-02-19T20:20:11.900+0800    INFO    demo/demo.go:62 request body: eiv al tse’c
-2022-02-19T20:20:11.900+0800    INFO    demo/demo.go:71 : eiv al tse’c
-```
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/trie.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/trie.md
deleted file mode 100644
index fa76be362cc..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/dev/trie.md
+++ /dev/null
@@ -1,145 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/dev/trie/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/dev/trie/
-description: Trie 前缀树介绍
-linkTitle: Trie 前缀树介绍
-title: Trie 前缀树介绍
-type: docs
-weight: 2
----
-
-
-
-
-
-# 简介
-
-![image.png](/imgs/pixiu/trie-1.png)<br />网关的核心之一是路由逻辑,决定一个请求需要经过怎样的加工,被转发到哪个下行服务。<br />其中 80% 的路由需求表达都以 URL 为基础。需要描述清楚具有某个特征的 URL 或者 URL 集合对应怎样的一系列下游处理策略。
-
-例如,'/test/**' 开头的 URL 路由到测试环境集群,'/release/user/**' 开头的 URL 会被路由到正式环境的 user 服务集群。
-
-
-同时网关作为所有请求的入口,每一毫秒的延时都会做用在全量的业务下,在 mesh 场景下,延时还会随着调用链路的加深,被倍数放大。按照生产环境业务相应 <=7 毫秒的标准来看,规则匹配的性能要求也是十分苛刻的。一定不能随着规则数目的增加而性能退化。
-
-# 使用介绍
-
-仅从使用方的角度阐述 pixiu 的配置文件如何描述 URL 相关的路由规则。(下面,我们介绍一下如何配置 URL 路由规则)<br />如下是一份 pixiu 的 api 配置文件,这份配置文件会被解析后生成一份对应的内存模型,作为 pixiu 路由相关配置的初始状态。之后由 RDS 协议修改解析后得到的内存模型,实现路由逻辑动态生效的效果。RDS 协议(RDS:xDS 协议下描述路由规则的部分)相关内容是后话不详细阐述。我们把注意力聚焦到resource部分。<br />resource 下 path 部分就是上文阐述的,URL 相关的路由描述。意思是满足 path 描述特征的 URL 会被成功匹配。
-
-```json
-name: server
-description: server sample
-resources:
-  - path: '/api/v1/test-dubbo/user/name/:name'
-    type: restful
-    description: user
-    methods:
-      - httpVerb: GET
-        enable: true
-        timeout: 1000ms
-        inboundRequest:
-          requestType: http
-          uri:
-            - name: name
-              required: true
-        integrationRequest:
-          requestType: dubbo
-          mappingParams:
-            - name: uri.name
-              mapTo: 0
-              mapType: "string"
-          applicationName: "UserProvider"
-          interface: "com.dubbogo.server.UserService"
-          method: "GetUserByName"
-          group: "test"
-          version: 1.0.0
-          clusterName: "test_dubbo"
-
-
-```
-
-被匹配后的请求会被转化成 dubbo 协议转发到 test_dubbo 集群调用 com.dubbogo.server.UserService 下的 GetUserByName 服务。<br />我们继续聚焦到如下范围:
-```json
-path: '/api/v1/test-dubbo/user/name/:name'
-```
-为了描述清楚一个 URL 或者一组 URL,路由引擎需要拥有以下能力:
-
-1. URL 可以包含变量,'/api/v1/test-dubbo/user/name/:name' 代表 URL 用“/”分割后,第六个部分的值作为变量 name 的值,向下游 filter 传递供filter使用。
-1. 需要有通配符
-   1. * 代表一个层级任意字符的通配 '/api/*/test-dubbo/user/name/:name' 这样的一个 path 描述代表了可能并不关心具体的版本,不论什么版本下的 URL 只要匹配都使用相同的逻辑加工数据并转发。
-   1. ** 代表多个层级的通配,从这个层级以后,子层级也可以是任意字符,**只可能存在于 URL 的末尾,不然会有二义性。'/api/v1/**' 这样的 path 表达了所有 V1 版本下的 URL 都采用相同的逻辑。
-
-为了正确的使用 pixiu 您可能还需要了解如下内容。
-
-## 优先级
-
-并非是独创的,类似 java 下的 spring 以及其他框架统一具有的优先级逻辑:
-
-1. 通配的优先级低于特指 。 '/api/v1/**' 低于 '/api/v1/test-dubbo/user/name/:name' 的优先级,假设有两个 resource 分别采用了如上两个path 配置,request 为 '/api/v1/test-dubbo/user/name/yqxu' 的请求到达pixiu 后应该生效哪个 resource?按照通配低于特指的原则,'/api/v1/test-dubbo/user/name/:name' 这条规则会生效。
-1. 深度更深的,优先级更高 。 '/api/v1/**' 对比 /api/v1/test-dubbo/**' ,如果请求同时满足如上两个描述, '/api/v1/test-dubbo/**' 深度更深,会生效。
-1. 通配符之间 '/*' 优先级高于 '/**'
-1. 变量等同于通配。
-
-## 冲突处理
-
-优先级规则只是冲突解决策略的一种,才同时匹配多个url描述时,优先级更高的那一种将会生效,然而优先级策略并不能涵盖所有的情况。<br />如果强行配置两条 resource path 完全相同,但是转发到不同的下游服务,这时候就会冲突。pixiu 下应对冲突的方案是 failfast,在 pixiu 初始化阶段,发现配置文件中有冲突的两项规则,则启动失败,让开发者今早发现问题并处理。
-
-# 原理介绍
-
-技术选型之初,以及确定使用pixiu后为了处理一些突发情况,以及应付一些pixiu自身可能存在的bug,开发者需要对pixiu 的路由原理有更深刻的了解。<br />下面,我们将详细介绍路由引擎的相关原理和实现,供感兴趣的同学了解。<br />相信阅读这部分内容的同学一定会有人下意识联想到字典树这个结构。使用字典树这个结构能实现存量规则数无关的匹配性能优化。
-
-一个存放字符串作为node的字典树,具有表达url 的能力。<br />![img](/imgs/pixiu/trie-2.png)<br />如上图描述等价于URL集合 '/api/v1' ,'/api/v2' ,'/web'
-
-维护一个标准字典树有几个关键的操作
-
-1. 字典树指定节点的查找(find): 从root 开始遍历字典书,'/api/v2' 称之为路径,在当前层级寻找指定路径,如果存在就继续在子树下完成剩下的路径匹配。'/api/v2' 先从 logic root 找到 '/api' ,并在 '/api' 的子树下继续查找剩下的路径 '/v2' 。
-1. 字典树节点的添加(add): 尝试查找指定节点,如果指定节点不存在则新建一个节点。假设一个空树状态下添加 '/api/v1' ,因为是空树那么logic root 下查找 '/api' 一定不存在,则在 root 下创建 '/api' ,继续在创建的 '/api' 节点下查找 '/v1' 因为 '/api' 是新建的 v1 一定也不存在,则继续创建v1
-1. 字典树url匹配(match):在这个最简单的版本下,匹配逻辑与指定节点的查找逻辑没有区别。
-
-还有一些不涉及递归或者复用上面逻辑递归操作的简单操作
-
-4. 修改字典树节点(modify):通过 find 逻辑找到指定节点,调用 set 方法或者直接赋值的方式修改节点内容。
-4. 删除字典树节点(delete): 通过 modify 逻辑修改 isdeleted 标为 true,并把节点内容 modify 为空。节点本身的内存不释放。
-4. 重建字典树(rebuild):遍历所有节点,添加到新树,如果 isdeleted为 true 则不添加到新树,通过rebuild 操作创建副本。
-
-由上可知,标准字典树结构距离通用的路由引擎底层数据结构能力还有一定差距,缺乏统配描述能力,缺乏变量表达的能力,下面我们来看一下如何进行改进。
-
-添加 描述统配逻辑的子树,作为子树中默认存在的一部分<br />![img](/imgs/pixiu/trie-3.png)<br />现在我们的变种字典树多了变量表达能力<br />'/web/:appname/test/*' 这样的url 在图中应该怎么表达?<br />没错就是这个路径<br />
-
-![img](/imgs/pixiu/trie-4.png)
-
-
-继续分析字典树几个关键的操作是否需要做变化?
-
-1. 字典树指定节点的查找  :
-   1. 如果不改动使用前一版本逻辑在 '/*' 节点处理之前都不会有问题: 从root 开始遍历字典书,'/api/v2/*' 称之为路径,在当前层级寻找指定路径,如果存在就继续在子树下完成剩下的路径匹配。 /api/v2 先从  logic root 找到 '/api' ,并在 '/api' 的子树下继续查找剩下的路径 '/v2' 。
-   1. 这版本我们加上对 '/*' 节点的处理:'/v2' 后是 '/*' ,'/*' 对应单级通配节点,继续递归查找 '/v2' 节点下一级通配节点是否为空。如果 path 是 '/api/v2/*/test2' 这样的路径则继续在统配子树下完成递归过程。
-2. 字典树节点的添加   :
-   1. 在添加 '/*' 节点之前,所有逻辑上一版本就足够处理:尝试查找指定节点,如果指定节点不存在则新建一个节点。假设一个空树状态下添加 '/api/v1/*' ,因为是空树那么 logic root 下查找 '/api' 一定不存在,则在 root 下创建 '/api' ,继续在创建的 '/api' 节点下查找 '/v1' 因为 '/api' 是新建的 v1 一定也不存在,则继续创建 v1。
-   1. 这版本加上 '/*' 的特殊处理 :'/v1' 新建后,查看通配子树,通配子树不存在,则为V1 节点添加内容为空的单级通配子树并在子树中继续递归。
-3. 字典树url匹配:在这个版本下,对比查找逻辑需要增加回朔逻辑。
-   1. 在遇到通配节点前逻辑与find 依旧相同 : 从root 开始遍历字典书,'/api/v2/*' 称之为路径,在当前层级寻找指定路径,如果存在就继续在子树下完成剩下的路径匹配。 '/api/v2' 先从 logic root 找到 '/api' ,并在 '/api' 的子树下继续查找剩下的路径 '/v2' 。
-   1. 在处理统配节点的时候会与 find 逻辑有所不同:'/v2' 下普通子树无匹配节点,回朔到通配子树,查看是否能匹配,这个例子中 '/v2' 下无通配子树,查询不到节点 。值得注意的是回朔逻辑的先后顺序,是先找普通子树再回朔到通配子树还是先查找通配子树再回朔到普通子树是取决于优先级规则的,按照需求必须是先查找普通子树。
-
-但是我们目前还是缺乏 '/**' 这种通配的表达能力代表了多级通配,可以分析需求得到结论,这种通配符,一定不存在子树,是一种特殊的叶子结点,仅用于 match 逻辑回朔时做特殊判断。继续加点特殊 node 后演化为:<br />![img](/imgs/pixiu/trie-5.png)<br />好了至此,需求都能满足了。<br />'/api/**' 等价路径为:<br />![img](/imgs/docs3-v2/dubbo-go-pixiu/dev/trie/1642993180981-51a0df19-bb03-49c8-9128-a6e95dbabfcd.png)<br />其他逻辑大同小异,match 逻辑回朔再多一级判断,如果一级通配子树也匹配不到结果,则再看一下多级通配子树是否为空(其实留一个标位就可以,为了统一模型好理解,还是用一个子树去描述)
-
-到目前这个版本所有上文提到的能力已经都能有效支撑,回头分析一下时间复杂读。<br />url 被 '/' 分割出一个一个的段,容易理解在匹配一个url 过程中复杂度是 O(n) n= url 段数。与树中存有的规则数量无关。再分析 n 的范围,n 其实不是一个可以无限大的数字,一部分浏览器甚至约束 url 长度必须小于 2000,按照一个单词长度为 5 来计算,可以大概估计段数最多会在 400 左右,n 如果可以被视为一个常数,那么复杂读可以看作是 O(1)。
-
-稍微解释一下find 和 match 有什么不同,为什么需要两种查找节点的方法。看下这个例子 :假设树中已经add 了 '/api/v1/:name/add' 这个 path,那么<br />find("/api/v1/:name/add"),find("/api/v1/*/add")两个调用应该能够拿到结果,在add 的过程中用于冲突判断。<br />假设有请求进来url 为 '/api/v1/:name/add' 那么match("/api/v1/:name/list")也应该能 match 到结果且变量name 为 :name。<br />再假设有请求进来 url 为 '/api/v1/yq/add' 那么match("/api/v1/yq/list")也应该能 match 到结果且变量name 为 yq 。find("/api/v1/yq/add" ) 则不会匹配到结果。
-# 后续改进
-
-目前实现在读树和写树之前,竞争一把全局锁,竞争失败后自旋直到竞争成功,然后完成读写。<br />解释一下为什么读都需要上锁,因为代码中大量运用了go 的 map 结构。这个结构只要并发读写直接会报如下错误:concurrent map read and map write<br />目前实现如下<br />![img](/imgs/pixiu/trie-6.png)<br />引入 command 队列,所有对 trie 的用户写操作先入列,同时做读写分离,分为读树和写树,维护一个线程负责追 log 把 command 写入到写树,读树因为只读,没有写入线程操作读树所以可以不加锁。写树因为只有一条线程向树内写入,没有竞争问题,也可以不加锁。(写入操作并不会很频繁单线程完全能负荷)<br />定义一个配置延迟生效的时间,比如3s<br />每3秒,读树和写树角色切换,每个 trie 分别维护一个 command 队列的游标,游标代表当前这个 trie,追 log 追到了哪�
 �记录,写入线程每3s 切换写游标引用。<br />
-
-![img](/imgs/pixiu/trie-7.png)
-
-如上图,最上面部分是一个先进先出的 command 队列,追 log 线程从这个队列中读取用户写操作,这个队列维护了两个游标 index1,index2,index1 代表了trie1 追 log 追到了 index1 的位置,index2 代表了 trie2 追 log 追到了 index2 的位置。追 log 线程同一时间内只会使用一个引用进行写操作,每次写完树对应的 index 游标下移一格,另一个 trie 引用将被用于读操作,一切读请求将从读引用对应的树中读取。因为追的是同一份 log ,最终一致性是能保证的。
-
-切换逻辑:
-
-1. 先使追 log 线程空转(不挂起,避免上下文切换,因为马上要恢复)
-1. 保证两个树都没有写入线程操作
-1. 切换读引用到另一个树
-1. 切换写引用到另一个树
-1. 恢复追 log 线程
-
-pr:<br />[https://github.com/apache/dubbo-go-pixiu/pull/262](https://github.com/apache/dubbo-go-pixiu/pull/262)<br />pkg/common/router/trie/trie.go:26
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/_index.md
deleted file mode 100755
index 201ba51b761..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/overview/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/overview/
-description: 入门概述
-linkTitle: 入门概述
-title: 入门概述
-type: docs
-weight: 10
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/faq.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/faq.md
deleted file mode 100755
index fccd3c0142a..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/faq.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/overview/faq/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/overview/faq/
-description: Pixiu 常见问题
-linkTitle: Pixiu 常见问题
-title: Pixiu 常见问题
-type: docs
-weight: 3
----
-
-
-
-
-
-
-
-### 常见问题 Q1
-**Pixiu 目前可以用于生产环境吗?**
-
-**A:** 
- 0.4.0版本之后就可以上生产环境,欢迎已经在使用的企业参与此 issue: [who's using Pixiu](https://github.com/apache/dubbo-go-pixiu/issues/64)
-
-### 常见问题 Q2
-**Pixiu 目前支持高可用吗?**
-
-**A:** 
- 目前 Pixiu 仅支持单实例部署,可以和 Nginx 组成无状态多实例集群。
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/terminology.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/terminology.md
deleted file mode 100755
index 20b040a906c..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/terminology.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/overview/terminology/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/overview/terminology/
-description: Pixiu 术语
-linkTitle: Pixiu 术语
-title: Pixiu 术语
-type: docs
-weight: 2
----
-
-
-
-
-
-
-
-![img](/imgs/pixiu/overview/terminology.png)
-
-### Listener 监听器
-
-Lisnter 代表网络端口监听的能力,可以配置监听的协议类型,地址,端口。目前支持 TCP、HTTP、HTTP2 和 TRIPLE 协议。
-
-### Network Filter 网络过滤器
-
-NetworkFilter 直接和 Listener 进行对接,代表对基础网络请求的处理,包括原始协议解析,路由解析等功能。
-
-### Http Filter & Dubbo Filter HTTP & Dubbo 过滤器
-
-Http Filter 和 Dubbo Filter 可以看做二级 Filter,提供诸如协议转换,限流,身份认证等通用功能。
-
-### Route 路由
-
-Route 代表请求的路由规则
-
-### Cluster 集群
-
-Cluter 代表相同服务的集群,Endpoint 则代表服务集群中的单一服务实例。
-
-### Adapter 适配器
-
-Adapter 则代表 Pixiu 和外界进行元数据获取的能力。能够根据服务中的服务元数据,进行路由和集群信息的动态获取。目前 Pixiu 支持两宽 Adapter,分别是从 Dubbo 集群和 Springcloud 集群获取信息。
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/what-is-pixiu.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/what-is-pixiu.md
deleted file mode 100755
index 3c9de721b0d..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/overview/what-is-pixiu.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/overview/what-is-pixiu/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/overview/what-is-pixiu/
-description: Pixiu 是一款开源的 Dubbo 生态的 API 网关和 接入 dubbo 集群的语言解决方案。作为 API 网关形态。
-linkTitle: Pixiu 是什么
-title: Pixiu 是什么
-type: docs
-weight: 1
----
-
-
-
-
-
-
-### Pixiu 说明
-
-
-Pixiu 是一款开源的 Dubbo 生态的 API 网关和 接入 dubbo 集群的语言解决方案。作为 API 网关形态, Pixiu 能接收外界的网络请求,将其转换为 dubbo 等协议请求,转发给背后集群;作为 Sidecar,Pixiu 期望可以代替代理服务注册到 Dubbo 集群,让多语言服务接入 Dubbo 集群提供更快捷的解决方案。
-
-
-![image](/imgs/pixiu/overview/pixiu-overview.png)
-
-
-
-
-### API 网关
-
-作为一款网关产品,Pixiu 帮助用户轻松创建、发布、维护、监控和保护任意规模的 API ,接受和处理成千上万个并发 API 调用,包括流量管理、 CORS 支持、授权和访问控制、限制、监控,以及 API 版本管理。除此以外,作为 Dubbo 的衍生产品,Pixiu 可以帮助 Dubbo 用户进行协议转换,实现跨系统、跨协议的服务能力互通。
-Pixiu 的整体设计遵守以下原则:
-- High performance: 高吞吐量以及毫秒级的延时。
-- 可扩展: 通过 go-plugin,用户可以根据自己的需求延展 Pixiu 的功能。
-- 简单可用: 用户通过少量配置,即可上线。
-
-
-### Sidecar 模式
-
-目前最为主流的接入 dubbo 集群的方式当然是集成语言对应的 sdk,但是如图的左侧部分。但是对于dubbo来讲,它的多语言支持能力不足,目前较为成熟的只有 java 版本和 go 版本,当然 js 版本 和 python 版本也在努力追赶中.其次,就是使用sdk的通用问题,比如代码耦合度高,版本升级困难,服务发现,服务路由和负载均衡策略不易整体调控等。
-
-所以 mesh 话或者 sidecar 的方案,也就是 service mesh 在16年时被提出。将服务发现,服务路由和负载均衡等逻辑放在 sidecar,服务使用轻量级 sdk 与之进行交互。 
-
-![img](/imgs/pixiu/overview/pixiu-sidecar.png)
-
-对于接入 dubbo 的多语言解决方案。首推的当然是 pixiu 作为 sidecar 和 服务进行同时部署。pixiu提供 服务发现,流量治理,路由能力,协议转换能力和通讯能力。如图的左侧部分,使用sidecar的服务可以和原生使用 dubbo 框架的服务组成集群,无感的进行相互调用。
-另外一种方案是 pixiu 只单单作为代理,将服务注册到dubbo集群中,如图右侧部分,这种方案部署和运维较为简单,比如适合中小规模的集群。
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/_index.md
deleted file mode 100755
index be140f46f13..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/
-description: 用户文档
-linkTitle: 用户文档
-title: 用户文档
-type: docs
-weight: 20
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/_index.md
deleted file mode 100755
index 4ec10d599cd..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/adapter/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/adapter/
-description: Adapter 介绍
-linkTitle: Adapter 介绍
-title: Adapter 介绍
-type: docs
-weight: 60
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/dubbo.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/dubbo.md
deleted file mode 100644
index 9f20c49fea7..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/dubbo.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/adapter/dubbo/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/adapter/dubbo/
-description: Dubbo 集群中心 Adapter
-linkTitle: Dubbo 集群中心 Adapter
-title: Dubbo 集群中心 Adapter
-type: docs
-weight: 10
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/springcloud.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/springcloud.md
deleted file mode 100644
index 03e9bd52d10..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/adapter/springcloud.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/adapter/springcloud/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/adapter/springcloud/
-description: Spring Cloud 集群中心 Adapter
-linkTitle: Spring Cloud 集群中心 Adapter
-title: Spring Cloud 集群中心 Adapter
-type: docs
-weight: 20
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/_index.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/_index.md
deleted file mode 100755
index fd47ce60c8a..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/appendix/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/appendix/
-description: 附录
-linkTitle: 附录
-title: 附录
-type: docs
-weight: 90
----
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/http-to-dubbo-default-stragety.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/http-to-dubbo-default-stragety.md
deleted file mode 100644
index 1c4e499619b..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/appendix/http-to-dubbo-default-stragety.md
+++ /dev/null
@@ -1,325 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/appendix/http-to-dubbo-default-stragety/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/appendix/http-to-dubbo-default-stragety/
-description: HTTP to Dubbo 默认转换协议
-linkTitle: HTTP to Dubbo 默认转换协议
-title: HTTP to Dubbo 默认转换协议
-type: docs
-weight: 10
----
-
-
-
-
-
-
-# 背景
-
-
-​	通过 Http 提供一个统一的服务提供者视图,用户不用在乎后端Dubbo服务的版本差异,协议差异,通过简单地在Http请求中传递rpc调用的参数,完成一次Rpc调用,通过实现http调用后端dubbo服务,进一步简化后端服务设计的复杂性。
-
-# 目的
-
-​	统一Http调用后端dubbo服务的形式,方便网关产品实现 Http 调用转 dubbo 调用的实现,Dubbo能和网关更好的融合。
-
-# Conception
-
-## Dubbo RPC 调用的基本形式
-
-
-
-![img](/imgs/pixiu/user/appendix/img1.png)
-
-
-
-希望通过提供Http调用Dubbo的方式简化 Consumer 的Rpc调用流程
-
-
-
-![img](/imgs/pixiu/user/appendix/img2.png)
-
-
-
-网关会在整个服务调用的过程中承担更多的原本客户端的功能,比如负载均衡,服务治理,安全等能力,外部用户调用服务的时候将更多的关注与调用本身。
-
-
-
-## Http request 和 Http response 的格式
-
-request的URL和Header中包含RPC调用的元信息,包含服务名,方法名,服务分组,服务版本,request 的 body 中包含请求的参数,参数是 **json list** 的格式, 如果没有参数则为 ***null***
-
-http response 中包含请求的处理状态,返回结果或者调用的错误类型以及错误具体信息,返回的body中只包含一个 ***json object***,这个object中包含 ***code***,***result***,***error***
-
-通过 code 表示返回的具体状态,result 和 error 在返回中只会返回其中一个,分别是调用的返回结果,调用返回的错误信息。
-
-
-
-### Http request
-
-#### Http 请求的方法
-
-只能为 **POST** 方法
-
-
-
-#### Http 请求的 URL
-
-格式:`[http://host/ {service} / {method](http://host/service/method)}` or `[https://host/ {service} / {method](https://host/service/method)}`
-
-
-
--  service 是调用的服务名,对应于Dubbo message body中的 service Name 
--  method 是调用的方法名,对应于Dubbo message body中的 method Name 
-
-服务名和方法名都应该和后端服务的声明一致
-
-
-
-如果URL中无法获取到service和method,应该直接返回 
-
-| http code | code | detail                         |
-| --------- | ---- | ------------------------------ |
-| 400       | 3    | service or method not provided |
-
-
-
-#### Http 请求的Header
-
-
-
-Header中必须包含以下条目:
-
-- x-dubbo-service-protocol
-
-表明这个Http 请求是一个Http转dubbo的请求,目前支持Dubbo 协议和 triple 协议,可配置的选项为:
-
-- - x-dubbo-service-protocol: triple
-  - x-dubbo-service-protocol: dubbo
-
-​      前者表示这是转化为triple协议,后者表示转化为dubbo协议
-
-
-
-可选参数:
-
--  x-dubbo-service-version 如果提供了应该填充到Dubbo message 的Serviceversion字段中.
--  x-dubbo-service-group  如果提供了应该在attachment 添加 group 字段并把对应的值进行填充。 
-
-
-
-#### Http 请求的Body
-
-
-
-body中包含请求的参数,body中只包含一个 ***Json object*** 对象
-
-这个对象目前包含两个字段:
-
-- param
-
-param 的值类型为 list,标识调用方法的参数,顺序和方法签名中的参数顺序一致
-
-这里使用object组装请求参数是为了协议能够向后兼容,body中的对象可能会增加新的字段。
-
-
-
-##### 基本类型在 Json Java Go 中的映射关系
-
-| Json Type | Java Type         | Golang Type |
-| --------- | ----------------- | ----------- |
-| Integer   | java.lang.Long    | int64       |
-| Double    | java.lang.Double  | float64     |
-| String    | java.lang.String  | string      |
-| Null      | null              | nil         |
-| Bool      | java.lang.Boolean | bool        |
-| List      | java.lang.List    | silice      |
-| Object    | java.lang.Map     | map         |
-
-通过对基本类型映射关系的定义简化网关配置,对于只使用基本配置的转化,网关应该可以在不使用额外配置的情况下完成转化的
-
-
-
-##### Body 处理异常时的处理策略
-
-1.  调用方提供的请求参数 Json 解析错误,返回状态码 400 
-2.  调用的时候,无法确定参数的具体类型,例如,用户使用的自定义类型,但是没有在网关配置具体的类型名,应该返回状态码 400  
-
-| http code | code | detail                       |
-| --------- | ---- | ---------------------------- |
-| 400       | 3    | argument parse error         |
-| 400       | 3    | argument type info not found |
-
-在以上条件都符合时,一个Http 调用可以被转化成为 Dubbo 协议的调用,只要网关能够成功进行请求的转化,则网关回复调用方的时候,Http 状态码都应该是 200 OK,至于调用方调用后端服务出现错误的信息,应该放在 body 中的 code 以及 error 字段中。
-
-
-
-### http response
-
-在请求经过后端返回之后,需要将一下信息传递给调用方:
-
-| name     | description                                              |
-| -------- | -------------------------------------------------------- |
-| status   | 返回的状态,在dubbo response 的header的status 中         |
-| 返回值   | 调用成功返回的结果,如果没有返回值,则result 的值为 null |
-| 返回异常 | 调用失败,产生异常,返回异常的具体message                |
-
-返回值和返回异常只能出现一项
-
-code 和 grpc 中的 status code 一致 详细的 code 及其含义见 https://grpc.github.io/grpc/core/md_doc_statuscodes.html
-
-
-
-#### 返回异常的处理:
-
-dubbo 中的异常以hessian2 的 class 类型返回,返沪的error中只需要对应的message 字段即可
-
-
-
-
-
-## Dubbo 协议的具体转化
-
-### Dubbo 协议的具体介绍 可以见文章
-
-https://dubbo.apache.org/en/blog/2018/10/05/introduction-to-the-dubbo-protocol/
-
-
-
-### Dubbo 协议的 message 格式
-
-![img](/imgs/dev/dubbo_protocol_header.png)
-
-
-
-#### Dubbo Header的封装要求
-
-| bits     | Name           | description                                           |
-| -------- | -------------- | ----------------------------------------------------- |
-| 0 - 15   | Magic Number   | 必须为 0xdabb                                         |
-| 16       | message 的类型 | 必须为 1 (request)                                  |
-| 17       | 2-way          | 必须为 1 (需要服务端返回值)                         |
-| 18       | Event          | 必须为 0 不支持事件类型                               |
-| 19 - 23  | 序列化类型     | 可以扩展实现Hessian,Json等序列化类型,类型编号如下表 |
-| 24 - 31  | Status         | 表示 response 的状态,见Status 处理要求               |
-| 32 - 95  | Request Id     | 客户端的请求ID,可以根据需要自行定义                  |
-| 96 - 127 | Data length    | 请求体的长度,请求体的大小                            |
-
-
-
-序列化类型编号:
-
-| Serialization Type | Code |
-| ------------------ | ---- |
-| Hessian2           | 2    |
-| Java               | 3    |
-| Compact Java       | 4    |
-| Fast Json          | 6    |
-| Native Java        | 7    |
-
-
-
-请求Header中的字段应该以大端的形式封装,发送到服务端
-
-
-
-#### Dubbo Body
-
-
-
-请求的body应该包含以下内容:
-
-| name                   | description                                                  |
-| ---------------------- | ------------------------------------------------------------ |
-| Dubbo Version          | 根据网关的配置,或者Http请求获取                             |
-| Service Name           | 服务名                                                       |
-| Method Name            | 调用方法名,采用泛化调用的方式,此项目固定为“$invoke”        |
-| Method parameter types | 参数类型,泛化调用有固定值 "Ljava/lang/String;[Ljava/lang/String;[Ljava/lang/Object;" |
-| Method arguments       | 使用配置的序列化方式将对应的参数序列化,按照用户传入的参数的顺序放入参数 |
-
-以上的各个项目在使用了指定的序列化形式之后,按照上表指定的顺序进行序列化。
-
-attachment 目前不转化
-
-
-
-***注意***:
-
-
-
-使用文本类型的序列化(Json) 在每一个序列化对象后边要加上行分割符( ***"\n"*** or ***"\r\n"*** )
-
-Java 中在使用FastJson 编解码的时候使用了BufferedReader,每次取buffer中的对象的时候,会先调用BufferReader的readLine方法,此方法分割行依靠 ‘/n’ , ’/r/n‘
-
-以下给出了Dubbo 协议中返回header中的status对应于GRPC status的对应列表
-
-
-
-##### Status 的处理
-
-Dubbo resposne status 中,OK延续使用grpc的 OK code,其余的 status Number编号紧接着 grpc 的16个 code进行编号
-
-对应的error详情是 response 中异常的 message。
-
-| Dubbo State                                    | Number |
-| ---------------------------------------------- | ------ |
-| ResponseStatus::Ok                             | 0      |
-| ResponseStatus::ClientTimeout                  | 130    |
-| ResponseStatus::ServerTimeout                  | 131    |
-| ResponseStatus::ServiceNotFound                | 12     |
-| ResponseStatus::ServerThreadpoolExhaustedError | 13     |
-| ResponseStatus::ClientError                    | \      |
-| ResponseStatus::ServerError                    | 13     |
-| ResponseStatus::ServiceError                   | 13     |
-| ResponseStatus::BadResponse                    | 13     |
-| ResponseStatus::BadRequest                     | 3      |
-
-## Triple 协议的具体转化
-
-Triple 是基于GRPC的,定义在Http2 协议之上
-
-### Triple中RPC调用的元信息
-
-
-
-#### Triple 通过 URL 传递调用的服务名和方法名
-
-格式: `[http://host/ {service} / {method](http://host/service/method)}`
-
-我们的规范兼容 Triple 通过http2传递参数的形式,尽量做到dubbo 和 triple 的统一。
-
-
-
-#### Header Frame
-
-header 中应该包含以下条目
-
-- Content-Type:***application/grpc-proto***
-
-标识这是一个 triple 协议的rpc调用
-
-- x-dubbo-service-group
-
-指明调用的服务的分组
-
-- x-dubbo-service-version
-
-指明调用的服务的版本
-
-
-
-#### Data frame
-
-Triple协议将请求参数放在Body中,在triple中,如果服务中的方法定义能够使用pb序列化,则只有一层序列化,如果需要用到其他的序列化,则需要使用TripleRequestWrapper
-
-对参数进行包装。
-
-
-
-我们推广使用 ***Triple + pb*** 的序列化形式,服务的提供方需要给出服务的 proto 定义,对于triple协议网关对于***triple + pb***  的转化是比较容易实现的,如果用户没有提供proto定义,需要返回信息:
-
-| http code | code | detail                       |
-| --------- | ---- | ---------------------------- |
-| 400       | 3    | argument type info not found |
-
-###
\ No newline at end of file
diff --git a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/configurations.md b/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/configurations.md
deleted file mode 100755
index b1996999e9f..00000000000
--- a/content/zh-cn/overview/mannual/dubbo-go-pixiu/user/configurations.md
+++ /dev/null
@@ -1,158 +0,0 @@
----
-aliases:
-    - /zh/docs3-v2/dubbo-go-pixiu/user/configurations/
-    - /zh-cn/docs3-v2/dubbo-go-pixiu/user/configurations/
-description: 启动和配置
-linkTitle: 启动和配置
-title: 启动和配置
-type: docs
-weight: 20
----
-
-
-
-
-
-
-### Pixiu 启动命令
-
-Pixiu 分为两个形态 Gateway 和 Sidecar,目前 Pixiu 可执行程序的命令如下所示,其中 pixiu 是可执行文件名称。注意,-c 后是本地配置文件的绝对路径。
-
-```
-pixiu gateway start -c /config/conf.yaml
-```
-
-### 配置详解 
-
-Pixiu 接受 yaml 格式的文件作为其主配置文件,其中对 Pixiu 的各类组件进行配置。我们以快速开始中的配置文件为例,详细讲解其中的组成部分,并且列出可能的扩展。
-
-```
-static_resources:
-  listeners:
-    - name: "net/http"
-      protocol_type: "HTTP"
-      address:
-        socket_address:
-          address: "0.0.0.0"
-          port: 8883
-      filter_chains:
-          filters:
-            - name: dgp.filter.httpconnectionmanager
-              config:
-                route_config:
-                  routes:
-                    - match:
-                        prefix: "*"
-                http_filters:
-                  - name: dgp.filter.http.dubboproxy
-                    config:
-                      dubboProxyConfig:
-                        auto_resolve: true
-                        registries:
-                          "zookeeper":
-                            protocol: "zookeeper"
-                            timeout: "3s"
-                            address: "127.0.0.1:2181"
-                            username: ""
-                            password: ""
-```
-
-首先,类似 `envoy`的配置,`static_resources` 表示如下都是静态配置。在静态配置中包括 Listener,NetworkFilter,Route,HttpFilter等组件,它们之间并不是完全独立的。
-
-#### Listener
-
-比如说上述配置就声明了一个监听本地 8883 端口的 HTTP 类型的 Listener,更多 Listener 的配置可以查看 [Listener](../listener/http/)。
-
-```
-  listeners:
-    - name: "net/http"
-      protocol_type: "HTTP"
-      address:
-        socket_address:
-          address: "0.0.0.0"
-          port: 8883
-      filter_chains:
-```
-listeners 的配置有 `protocol_type` 表示是 HTTP 类型的 Listener,`address` 则配置了监听的地址和端口,`filter_chains` 则指定了该 Listener 接收到请求要交由哪些 NetworkFilter 处理。
-
-#### NetworkFilter
-
-NetworkFilter 是 Pixiu 的关键组件之一,它可以有 Route 和 HttpFilter 一起组成,负责接收 Listener 传递而来的请求并进行处理。
-
-```
-filters:
-            - name: dgp.filter.httpconnectionmanager
-              config:
-                route_config:
-                http_filters:
-```
-
-上述配置指明了使用 `dgp.filter.httpconnectionmanager` 这款 NetworkFilter,它能够接收 Http 请求的 `Request` 和 `Response` 进行处理,并且可以配置 Route 路由信息和使用 HttpFilter 对请求进行链式处理。更多的 NetworkFilter 可以查看 [NetworkfFilter文档](../networkfilter/http/)
-
-
-
-#### Route 路由 和 Cluster 集群
-
-route 可以用于对请求进行路由分发,以下面配置为例。具体配置文件可以查看 `/samples/http/simple` 案例的配置文件
-
-```
-            - name: dgp.filter.httpconnectionmanager
-              config:
-                route_config:
-                  routes:
-                    - match:
-                        prefix: "/user"
-                      route:
-                        cluster: "user"
-```
-
-上述配置指定了对于 Path 的前缀为 `/user` 的 HTTP 请求,转发给名称为 user 的 cluster 服务集群中。
-
-而具体 cluster 集群的定义如下所示:
-
-```
-  clusters:
-    - name: "user"
-      lb_policy: "RoundRobin"
-      endpoints:
-        - id: 1
-          socket_address:
-            address: 127.0.0.1
-            port: 1314
-```
-
-上述配置定义了名为 user 的 cluster 集群信息,它的负载均衡策略是 RoundRobin,然后它包含一个 endpoint 实例,其地址是 127.0.0.1。
-
-目前,在转发 HTTP 请求或者 Grpc 请求的场景下需要使用 Route 和 Cluster,而涉及到转发 Dubbo 相关请求的场景下暂时不需要二者。
-
-#### HttpFilter
-
-当 NetworkFilter 接收到 Listener 传来的请求后,需要对其进行系列操作,例如限流、鉴权等,最后还需要将这个请求转发给具体上游服务。这些工作都交给 NetworkFilter 所持有的 HttpFilter 链进行处理。
-
-```
-            - name: dgp.filter.httpconnectionmanager
-              config:
-                http_filters:
-                  - name: dgp.filter.http.dubboproxy
-                    config:
-                      dubboProxyConfig:
-                        auto_resolve: true
-                        registries:
-                          "zookeeper":
-                            protocol: "zookeeper"
-                            timeout: "3s"
-                            address: "127.0.0.1:2181"
-                            username: ""
-                            password: ""
-```
-
-如上配置所示,`httpconnectionmanager` 这个 NetworkFilter 下有一个 HttpFilter chain。其中包括 `dgp.filter.http.dubboproxy` 这一款 HttpFilter。
-它负责将 HTTP 请求转换为 Dubbo 请求,并转发出去。它需要配置一个 Dubbo 集群注册中心的地址信息,指定其为 zookeeper 中间件。其中 `auto_resolve` 则指定使用 HTTP to Dubbo 默认转换协议来进行相关数据转换,具体可以参考[《默认转换协议》](../appendix/http-to-dubbo-default-stragety/)。
-
-更多的 HttpFilter 可以查看 [HttpFilter文档](../httpfilter/dubbo/)。
-
... 94390 lines suppressed ...