You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dubbo.apache.org by hy...@apache.org on 2019/06/14 01:53:56 UTC
[dubbo-website] branch master updated: remove genereated htmls from
source branch
This is an automated email from the ASF dual-hosted git repository.
hyunkun 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 9709cb8 remove genereated htmls from source branch
9709cb8 is described below
commit 9709cb8902b855dc50e7ff90ff7b09fd4e2fee80
Author: Huang Yunkun <ht...@gmail.com>
AuthorDate: Fri Jun 14 09:48:50 2019 +0800
remove genereated htmls from source branch
---
en-us/blog/apachecon-na-2018.html | 34 -
en-us/blog/apachecon-na-2018.json | 10 -
en-us/blog/download.html | 161 --
en-us/blog/download.json | 10 -
en-us/blog/dubbo-101.html | 346 ----
en-us/blog/dubbo-101.json | 10 -
en-us/blog/dubbo-annotation.html | 335 ----
en-us/blog/dubbo-annotation.json | 10 -
...o-basic-usage-dubbo-provider-configuration.html | 405 -----
...o-basic-usage-dubbo-provider-configuration.json | 10 -
en-us/blog/dubbo-fescar.html | 215 ---
en-us/blog/dubbo-fescar.json | 10 -
en-us/blog/dubbo-generic-invoke.html | 175 --
en-us/blog/dubbo-generic-invoke.json | 10 -
en-us/blog/dubbo-invoke.html | 193 --
en-us/blog/dubbo-invoke.json | 10 -
en-us/blog/dubbo-k8s.html | 190 --
en-us/blog/dubbo-k8s.json | 10 -
en-us/blog/dubbo-loadbalance.html | 258 ---
en-us/blog/dubbo-loadbalance.json | 10 -
en-us/blog/dubbo-meetup-beijing-may-12th-2018.html | 41 -
en-us/blog/dubbo-meetup-beijing-may-12th-2018.json | 10 -
en-us/blog/dubbo-meetup-chengdu.html | 42 -
en-us/blog/dubbo-meetup-chengdu.json | 10 -
en-us/blog/dubbo-meetup-hangzhou.html | 43 -
en-us/blog/dubbo-meetup-hangzhou.json | 10 -
.../blog/dubbo-meetup-shanghai-jun-23rd-2018.html | 41 -
.../blog/dubbo-meetup-shanghai-jun-23rd-2018.json | 10 -
en-us/blog/dubbo-meetup-shenzhen.html | 40 -
en-us/blog/dubbo-meetup-shenzhen.json | 10 -
en-us/blog/dubbo-new-async.html | 416 -----
en-us/blog/dubbo-new-async.json | 10 -
en-us/blog/dubbo-zk.html | 278 ---
en-us/blog/dubbo-zk.json | 10 -
en-us/blog/dubbo2-js.html | 233 ---
en-us/blog/dubbo2-js.json | 10 -
en-us/blog/gsoc-2018.html | 34 -
en-us/blog/gsoc-2018.json | 10 -
en-us/blog/index.html | 32 -
en-us/blog/introduction-to-dubbo-qos.html | 245 ---
en-us/blog/introduction-to-dubbo-qos.json | 10 -
en-us/blog/introduction-to-dubbo-spi-2.html | 389 ----
en-us/blog/introduction-to-dubbo-spi-2.json | 10 -
en-us/blog/introduction-to-dubbo-spi.html | 205 ---
en-us/blog/introduction-to-dubbo-spi.json | 10 -
en-us/blog/pinpoint.html | 403 ----
en-us/blog/pinpoint.json | 10 -
en-us/blog/prepare-an-apache-release.html | 489 -----
en-us/blog/prepare-an-apache-release.json | 10 -
en-us/blog/qcon-beijing-2018.html | 34 -
en-us/blog/qcon-beijing-2018.json | 10 -
en-us/blog/sentinel-introduction-for-dubbo.html | 97 -
en-us/blog/sentinel-introduction-for-dubbo.json | 10 -
.../spring-boot-dubbo-start-stop-analysis.html | 217 ---
.../spring-boot-dubbo-start-stop-analysis.json | 10 -
en-us/blog/tracing-with-skywalking.html | 131 --
en-us/blog/tracing-with-skywalking.json | 10 -
en-us/community/index.html | 32 -
en-us/docs/admin/README.html | 33 -
en-us/docs/admin/README.json | 6 -
en-us/docs/admin/SUMMARY.html | 41 -
en-us/docs/admin/SUMMARY.json | 6 -
en-us/docs/admin/install/admin-console.html | 61 -
en-us/docs/admin/install/admin-console.json | 6 -
en-us/docs/admin/install/consumer-demo.html | 43 -
en-us/docs/admin/install/consumer-demo.json | 6 -
en-us/docs/admin/install/introduction.html | 38 -
en-us/docs/admin/install/introduction.json | 6 -
en-us/docs/admin/install/provider-demo.html | 43 -
en-us/docs/admin/install/provider-demo.json | 6 -
en-us/docs/admin/install/redis.html | 72 -
en-us/docs/admin/install/redis.json | 6 -
.../docs/admin/install/simple-monitor-center.html | 34 -
.../docs/admin/install/simple-monitor-center.json | 6 -
.../docs/admin/install/simple-registry-center.html | 33 -
.../docs/admin/install/simple-registry-center.json | 6 -
en-us/docs/admin/install/zookeeper.html | 101 -
en-us/docs/admin/install/zookeeper.json | 6 -
en-us/docs/admin/introduction.html | 95 -
en-us/docs/admin/introduction.json | 6 -
en-us/docs/admin/ops/dubbo-ops.html | 44 -
en-us/docs/admin/ops/dubbo-ops.json | 6 -
en-us/docs/admin/ops/introduction.html | 33 -
en-us/docs/admin/ops/introduction.json | 6 -
en-us/docs/admin/ops/pinpoint.html | 403 ----
en-us/docs/admin/ops/pinpoint.json | 6 -
en-us/docs/admin/ops/skywalking.html | 131 --
en-us/docs/admin/ops/skywalking.json | 6 -
en-us/docs/admin/ops/skywalking.md | 121 --
en-us/docs/admin/serviceGovernance.html | 72 -
en-us/docs/admin/serviceGovernance.json | 6 -
en-us/docs/admin/serviceSearch.html | 37 -
en-us/docs/admin/serviceSearch.json | 6 -
en-us/docs/admin/serviceTest.html | 33 -
en-us/docs/admin/serviceTest.json | 6 -
en-us/docs/dev/README.html | 34 -
en-us/docs/dev/README.json | 6 -
en-us/docs/dev/SPI.html | 203 ---
en-us/docs/dev/SPI.json | 6 -
en-us/docs/dev/SUMMARY.html | 76 -
en-us/docs/dev/SUMMARY.json | 6 -
en-us/docs/dev/TCK.html | 46 -
en-us/docs/dev/TCK.json | 6 -
en-us/docs/dev/build.html | 74 -
en-us/docs/dev/build.json | 6 -
en-us/docs/dev/checklist.html | 51 -
en-us/docs/dev/checklist.json | 6 -
en-us/docs/dev/code-smell.html | 160 --
en-us/docs/dev/code-smell.json | 6 -
en-us/docs/dev/coding.html | 91 -
en-us/docs/dev/coding.json | 6 -
en-us/docs/dev/contract.html | 45 -
en-us/docs/dev/contract.json | 6 -
en-us/docs/dev/contribution.html | 395 ----
en-us/docs/dev/contribution.json | 6 -
en-us/docs/dev/design.html | 114 --
en-us/docs/dev/design.json | 6 -
en-us/docs/dev/implementation.html | 131 --
en-us/docs/dev/implementation.json | 6 -
en-us/docs/dev/impls/cache.html | 95 -
en-us/docs/dev/impls/cache.json | 6 -
en-us/docs/dev/impls/cluster.html | 89 -
en-us/docs/dev/impls/cluster.json | 6 -
en-us/docs/dev/impls/compiler.html | 71 -
en-us/docs/dev/impls/compiler.json | 6 -
en-us/docs/dev/impls/container.html | 77 -
en-us/docs/dev/impls/container.json | 6 -
en-us/docs/dev/impls/dispatcher.html | 77 -
en-us/docs/dev/impls/dispatcher.json | 6 -
en-us/docs/dev/impls/exchanger.html | 100 -
en-us/docs/dev/impls/exchanger.json | 6 -
en-us/docs/dev/impls/exporter-listener.html | 78 -
en-us/docs/dev/impls/exporter-listener.json | 6 -
en-us/docs/dev/impls/extension-factory.html | 72 -
en-us/docs/dev/impls/extension-factory.json | 6 -
en-us/docs/dev/impls/filter.html | 104 --
en-us/docs/dev/impls/filter.json | 6 -
en-us/docs/dev/impls/introduction.html | 34 -
en-us/docs/dev/impls/introduction.json | 6 -
en-us/docs/dev/impls/invoker-listener.html | 78 -
en-us/docs/dev/impls/invoker-listener.json | 6 -
en-us/docs/dev/impls/load-balance.html | 78 -
en-us/docs/dev/impls/load-balance.json | 6 -
en-us/docs/dev/impls/logger-adapter.html | 93 -
en-us/docs/dev/impls/logger-adapter.json | 6 -
en-us/docs/dev/impls/merger.html | 74 -
en-us/docs/dev/impls/merger.json | 6 -
en-us/docs/dev/impls/monitor.html | 87 -
en-us/docs/dev/impls/monitor.json | 6 -
en-us/docs/dev/impls/networker.html | 74 -
en-us/docs/dev/impls/networker.json | 6 -
en-us/docs/dev/impls/page.html | 76 -
en-us/docs/dev/impls/page.json | 6 -
en-us/docs/dev/impls/protocol.html | 159 --
en-us/docs/dev/impls/protocol.json | 6 -
en-us/docs/dev/impls/proxy-factory.html | 80 -
en-us/docs/dev/impls/proxy-factory.json | 6 -
en-us/docs/dev/impls/registry.html | 209 ---
en-us/docs/dev/impls/registry.json | 6 -
en-us/docs/dev/impls/remoting.html | 133 --
en-us/docs/dev/impls/remoting.json | 6 -
en-us/docs/dev/impls/router.html | 76 -
en-us/docs/dev/impls/router.json | 6 -
en-us/docs/dev/impls/serialize.html | 89 -
en-us/docs/dev/impls/serialize.json | 6 -
en-us/docs/dev/impls/status-checker.html | 79 -
en-us/docs/dev/impls/status-checker.json | 6 -
en-us/docs/dev/impls/telnet-handler.html | 89 -
en-us/docs/dev/impls/telnet-handler.json | 6 -
en-us/docs/dev/impls/threadpool.html | 75 -
en-us/docs/dev/impls/threadpool.json | 6 -
en-us/docs/dev/impls/validation.html | 85 -
en-us/docs/dev/impls/validation.json | 6 -
en-us/docs/dev/introduction.html | 32 -
en-us/docs/dev/introduction.json | 6 -
en-us/docs/dev/principals/code-detail.html | 53 -
en-us/docs/dev/principals/code-detail.json | 6 -
en-us/docs/dev/principals/configuration.html | 85 -
en-us/docs/dev/principals/configuration.json | 6 -
en-us/docs/dev/principals/dummy.html | 209 ---
en-us/docs/dev/principals/dummy.json | 6 -
en-us/docs/dev/principals/expansibility.html | 43 -
en-us/docs/dev/principals/expansibility.json | 6 -
en-us/docs/dev/principals/extension.html | 117 --
en-us/docs/dev/principals/extension.json | 6 -
en-us/docs/dev/principals/general-knowledge.html | 67 -
en-us/docs/dev/principals/general-knowledge.json | 6 -
en-us/docs/dev/principals/introduction.html | 34 -
en-us/docs/dev/principals/introduction.json | 6 -
en-us/docs/dev/principals/robustness.html | 81 -
en-us/docs/dev/principals/robustness.json | 6 -
en-us/docs/dev/release.html | 65 -
en-us/docs/dev/release.json | 6 -
.../committer-guide/apache-dubbo-page_dev.html | 67 -
.../committer-guide/apache-dubbo-page_dev.json | 6 -
.../committer-guide/label-an-issue-guide_dev.html | 73 -
.../committer-guide/label-an-issue-guide_dev.json | 6 -
.../committer-guide/new-committer-guide_dev.html | 119 --
.../committer-guide/new-committer-guide_dev.json | 6 -
.../developers/committer-guide/release-guide.html | 34 -
.../developers/committer-guide/release-guide.json | 6 -
.../committer-guide/release-guide_dev.html | 450 -----
.../committer-guide/release-guide_dev.json | 9 -
.../committer-guide/website-guide_dev.html | 37 -
.../committer-guide/website-guide_dev.json | 6 -
.../contributor-guide/become-a-committer_dev.html | 40 -
.../contributor-guide/become-a-committer_dev.json | 6 -
.../contributor-guide/cla-signing-guide_dev.html | 59 -
.../contributor-guide/cla-signing-guide_dev.json | 6 -
.../dubbo-extension-guide_dev.html | 67 -
.../dubbo-extension-guide_dev.json | 6 -
.../mailing-list-subscription-guide_dev.html | 111 --
.../mailing-list-subscription-guide_dev.json | 6 -
.../new-contributor-guide_dev.html | 81 -
.../new-contributor-guide_dev.json | 6 -
.../reporting-security-issues_dev.html | 46 -
.../reporting-security-issues_dev.json | 6 -
.../software-donation-guide_dev.html | 132 --
.../software-donation-guide_dev.json | 6 -
.../contributor-guide/test-coverage-guide_dev.html | 53 -
.../contributor-guide/test-coverage-guide_dev.json | 6 -
en-us/docs/developers/developers_dev.html | 344 ----
en-us/docs/developers/developers_dev.json | 6 -
en-us/docs/developers/faq.html | 54 -
en-us/docs/developers/faq.json | 6 -
en-us/docs/developers/guide_dev.html | 107 --
en-us/docs/developers/guide_dev.json | 6 -
en-us/docs/developers/user-guide/faq_dev.html | 54 -
en-us/docs/developers/user-guide/faq_dev.json | 6 -
en-us/docs/user/README.html | 34 -
en-us/docs/user/README.json | 6 -
en-us/docs/user/SUMMARY.html | 146 --
en-us/docs/user/SUMMARY.json | 6 -
en-us/docs/user/benchmark-tool.html | 72 -
en-us/docs/user/benchmark-tool.json | 6 -
en-us/docs/user/best-practice.html | 64 -
en-us/docs/user/best-practice.json | 6 -
en-us/docs/user/capacity-plan.html | 48 -
en-us/docs/user/capacity-plan.json | 6 -
en-us/docs/user/configuration/annotation.html | 119 --
en-us/docs/user/configuration/annotation.json | 6 -
en-us/docs/user/configuration/api.html | 141 --
en-us/docs/user/configuration/api.json | 6 -
en-us/docs/user/configuration/index.html | 33 -
en-us/docs/user/configuration/index.json | 6 -
en-us/docs/user/configuration/properties.html | 67 -
en-us/docs/user/configuration/properties.json | 6 -
en-us/docs/user/configuration/xml.html | 141 --
en-us/docs/user/configuration/xml.json | 6 -
en-us/docs/user/coveragence.html | 48 -
en-us/docs/user/coveragence.json | 6 -
en-us/docs/user/demos/accesslog.html | 76 -
en-us/docs/user/demos/accesslog.json | 6 -
en-us/docs/user/demos/async-call.html | 76 -
en-us/docs/user/demos/async-call.json | 6 -
en-us/docs/user/demos/attachment.html | 50 -
en-us/docs/user/demos/attachment.json | 6 -
en-us/docs/user/demos/callback-parameter.html | 123 --
en-us/docs/user/demos/callback-parameter.json | 6 -
en-us/docs/user/demos/concurrency-control.html | 78 -
en-us/docs/user/demos/concurrency-control.json | 6 -
en-us/docs/user/demos/config-connections.html | 52 -
en-us/docs/user/demos/config-connections.json | 6 -
en-us/docs/user/demos/config-rule.html | 73 -
en-us/docs/user/demos/config-rule.json | 6 -
en-us/docs/user/demos/context.html | 62 -
en-us/docs/user/demos/context.json | 6 -
en-us/docs/user/demos/delay-publish.html | 67 -
en-us/docs/user/demos/delay-publish.json | 6 -
en-us/docs/user/demos/distributed-transaction.html | 36 -
en-us/docs/user/demos/distributed-transaction.json | 6 -
en-us/docs/user/demos/dump.html | 47 -
en-us/docs/user/demos/dump.json | 6 -
en-us/docs/user/demos/echo-service.html | 49 -
en-us/docs/user/demos/echo-service.json | 6 -
en-us/docs/user/demos/events-notify.html | 104 --
en-us/docs/user/demos/events-notify.json | 6 -
en-us/docs/user/demos/explicit-target.html | 51 -
en-us/docs/user/demos/explicit-target.json | 6 -
en-us/docs/user/demos/fault-tolerent-strategy.html | 75 -
en-us/docs/user/demos/fault-tolerent-strategy.json | 6 -
en-us/docs/user/demos/generic-reference.html | 108 --
en-us/docs/user/demos/generic-reference.json | 6 -
en-us/docs/user/demos/generic-service.html | 66 -
en-us/docs/user/demos/generic-service.json | 6 -
en-us/docs/user/demos/graceful-shutdown.html | 53 -
en-us/docs/user/demos/graceful-shutdown.json | 6 -
en-us/docs/user/demos/group-merger.html | 71 -
en-us/docs/user/demos/group-merger.json | 6 -
en-us/docs/user/demos/hostname-binding.html | 111 --
en-us/docs/user/demos/hostname-binding.json | 6 -
en-us/docs/user/demos/index.html | 33 -
en-us/docs/user/demos/index.json | 6 -
en-us/docs/user/demos/introduction.html | 36 -
en-us/docs/user/demos/introduction.json | 6 -
en-us/docs/user/demos/lazy-connect.html | 43 -
en-us/docs/user/demos/lazy-connect.json | 6 -
en-us/docs/user/demos/loadbalance.html | 77 -
en-us/docs/user/demos/loadbalance.json | 6 -
en-us/docs/user/demos/local-call.html | 57 -
en-us/docs/user/demos/local-call.json | 6 -
en-us/docs/user/demos/local-mock.html | 101 -
en-us/docs/user/demos/local-mock.json | 6 -
en-us/docs/user/demos/local-stub.html | 72 -
en-us/docs/user/demos/local-stub.json | 6 -
en-us/docs/user/demos/logger-strategy.html | 58 -
en-us/docs/user/demos/logger-strategy.json | 6 -
en-us/docs/user/demos/multi-protocols.html | 67 -
en-us/docs/user/demos/multi-protocols.json | 6 -
en-us/docs/user/demos/multi-registry.html | 103 --
en-us/docs/user/demos/multi-registry.json | 6 -
en-us/docs/user/demos/multi-versions.html | 62 -
en-us/docs/user/demos/multi-versions.json | 6 -
en-us/docs/user/demos/netty4.html | 64 -
en-us/docs/user/demos/netty4.json | 6 -
en-us/docs/user/demos/parameter-validation.html | 194 --
en-us/docs/user/demos/parameter-validation.json | 6 -
en-us/docs/user/demos/preflight-check.html | 64 -
en-us/docs/user/demos/preflight-check.json | 6 -
en-us/docs/user/demos/reference-config-cache.html | 56 -
en-us/docs/user/demos/reference-config-cache.json | 6 -
en-us/docs/user/demos/registry-only.html | 44 -
en-us/docs/user/demos/registry-only.json | 6 -
en-us/docs/user/demos/result-cache.html | 58 -
en-us/docs/user/demos/result-cache.json | 6 -
en-us/docs/user/demos/routing-rule.html | 207 ---
en-us/docs/user/demos/routing-rule.json | 6 -
en-us/docs/user/demos/serialization.html | 92 -
en-us/docs/user/demos/serialization.json | 6 -
en-us/docs/user/demos/service-container.html | 80 -
en-us/docs/user/demos/service-container.json | 6 -
en-us/docs/user/demos/service-downgrade.html | 47 -
en-us/docs/user/demos/service-downgrade.json | 6 -
en-us/docs/user/demos/service-group.html | 52 -
en-us/docs/user/demos/service-group.json | 6 -
en-us/docs/user/demos/static-service.html | 47 -
en-us/docs/user/demos/static-service.json | 6 -
en-us/docs/user/demos/stickiness.html | 42 -
en-us/docs/user/demos/stickiness.json | 6 -
en-us/docs/user/demos/subscribe-only.html | 42 -
en-us/docs/user/demos/subscribe-only.json | 6 -
en-us/docs/user/demos/thread-model.html | 57 -
en-us/docs/user/demos/thread-model.json | 6 -
en-us/docs/user/demos/token-authorization.html | 59 -
en-us/docs/user/demos/token-authorization.json | 6 -
en-us/docs/user/dependencies.html | 94 -
en-us/docs/user/dependencies.json | 6 -
en-us/docs/user/languages/erlang/reference.html | 45 -
en-us/docs/user/languages/erlang/reference.json | 6 -
.../docs/user/languages/erlang/serialization.html | 59 -
.../docs/user/languages/erlang/serialization.json | 6 -
en-us/docs/user/languages/erlang/service.html | 75 -
en-us/docs/user/languages/erlang/service.json | 6 -
en-us/docs/user/languages/erlang/start.html | 78 -
en-us/docs/user/languages/erlang/start.json | 6 -
en-us/docs/user/maturity.html | 583 ------
en-us/docs/user/maturity.json | 6 -
en-us/docs/user/perf-test.html | 367 ----
en-us/docs/user/perf-test.json | 6 -
en-us/docs/user/preface/architecture.html | 138 --
en-us/docs/user/preface/architecture.json | 6 -
en-us/docs/user/preface/background.html | 43 -
en-us/docs/user/preface/background.json | 6 -
en-us/docs/user/preface/index.html | 33 -
en-us/docs/user/preface/index.json | 6 -
en-us/docs/user/preface/requirements.html | 39 -
en-us/docs/user/preface/requirements.json | 6 -
en-us/docs/user/preface/usage.html | 60 -
en-us/docs/user/preface/usage.json | 6 -
en-us/docs/user/quick-start.html | 232 ---
en-us/docs/user/quick-start.json | 6 -
en-us/docs/user/recommend.html | 171 --
en-us/docs/user/recommend.json | 6 -
en-us/docs/user/references/api.html | 77 -
en-us/docs/user/references/api.json | 6 -
en-us/docs/user/references/maven.html | 48 -
en-us/docs/user/references/maven.json | 6 -
en-us/docs/user/references/protocol/dubbo.html | 130 --
en-us/docs/user/references/protocol/dubbo.json | 6 -
en-us/docs/user/references/protocol/hessian.html | 78 -
en-us/docs/user/references/protocol/hessian.json | 6 -
en-us/docs/user/references/protocol/http.html | 74 -
en-us/docs/user/references/protocol/http.json | 6 -
.../user/references/protocol/introduction.html | 34 -
.../user/references/protocol/introduction.json | 6 -
en-us/docs/user/references/protocol/memcached.html | 53 -
en-us/docs/user/references/protocol/memcached.json | 6 -
en-us/docs/user/references/protocol/redis.html | 53 -
en-us/docs/user/references/protocol/redis.json | 6 -
en-us/docs/user/references/protocol/rest.html | 533 ------
en-us/docs/user/references/protocol/rest.json | 6 -
en-us/docs/user/references/protocol/rmi.html | 86 -
en-us/docs/user/references/protocol/rmi.json | 6 -
en-us/docs/user/references/protocol/thrift.html | 51 -
en-us/docs/user/references/protocol/thrift.json | 6 -
.../docs/user/references/protocol/webservice.html | 107 --
.../docs/user/references/protocol/webservice.json | 6 -
en-us/docs/user/references/qos.html | 224 ---
en-us/docs/user/references/qos.json | 6 -
.../user/references/registry/introduction.html | 34 -
.../user/references/registry/introduction.json | 6 -
en-us/docs/user/references/registry/multicast.html | 56 -
en-us/docs/user/references/registry/multicast.json | 6 -
en-us/docs/user/references/registry/nacos.html | 111 --
en-us/docs/user/references/registry/nacos.json | 6 -
en-us/docs/user/references/registry/redis.html | 95 -
en-us/docs/user/references/registry/redis.json | 6 -
en-us/docs/user/references/registry/simple.html | 65 -
en-us/docs/user/references/registry/simple.json | 6 -
en-us/docs/user/references/registry/zookeeper.html | 130 --
en-us/docs/user/references/registry/zookeeper.json | 6 -
en-us/docs/user/references/telnet.html | 124 --
en-us/docs/user/references/telnet.json | 6 -
.../user/references/xml/dubbo-application.html | 130 --
.../user/references/xml/dubbo-application.json | 6 -
en-us/docs/user/references/xml/dubbo-argument.html | 84 -
en-us/docs/user/references/xml/dubbo-argument.json | 6 -
en-us/docs/user/references/xml/dubbo-consumer.html | 230 ---
en-us/docs/user/references/xml/dubbo-consumer.json | 6 -
en-us/docs/user/references/xml/dubbo-method.html | 215 ---
en-us/docs/user/references/xml/dubbo-method.json | 6 -
en-us/docs/user/references/xml/dubbo-module.html | 90 -
en-us/docs/user/references/xml/dubbo-module.json | 6 -
en-us/docs/user/references/xml/dubbo-monitor.html | 70 -
en-us/docs/user/references/xml/dubbo-monitor.json | 6 -
.../docs/user/references/xml/dubbo-parameter.html | 78 -
.../docs/user/references/xml/dubbo-parameter.json | 6 -
en-us/docs/user/references/xml/dubbo-protocol.html | 290 ---
en-us/docs/user/references/xml/dubbo-protocol.json | 6 -
en-us/docs/user/references/xml/dubbo-provider.html | 490 -----
en-us/docs/user/references/xml/dubbo-provider.json | 6 -
.../docs/user/references/xml/dubbo-reference.html | 320 ----
.../docs/user/references/xml/dubbo-reference.json | 6 -
en-us/docs/user/references/xml/dubbo-registry.html | 200 --
en-us/docs/user/references/xml/dubbo-registry.json | 6 -
en-us/docs/user/references/xml/dubbo-service.html | 360 ----
en-us/docs/user/references/xml/dubbo-service.json | 6 -
en-us/docs/user/references/xml/introduction.html | 52 -
en-us/docs/user/references/xml/introduction.json | 6 -
en-us/docs/user/rest.html | 982 ----------
en-us/docs/user/rest.json | 6 -
en-us/docs/user/simple-monitor.html | 106 --
en-us/docs/user/simple-monitor.json | 6 -
en-us/download/index.html | 32 -
en-us/index.html | 32 -
zh-cn/blog/Configuration Conclude.html | 189 --
zh-cn/blog/Configuration Conclude.json | 6 -
zh-cn/blog/Guides for upgrading to 2.7.x.html | 342 ----
zh-cn/blog/Guides for upgrading to 2.7.x.json | 6 -
zh-cn/blog/Guides-for-upgrading-to-27x.html | 342 ----
zh-cn/blog/Guides-for-upgrading-to-27x.json | 6 -
zh-cn/blog/apachecon-na-2018.html | 34 -
zh-cn/blog/apachecon-na-2018.json | 10 -
.../blog/build-new-docker-image-in-dockerhub.html | 73 -
.../blog/build-new-docker-image-in-dockerhub.json | 10 -
zh-cn/blog/download.html | 162 --
zh-cn/blog/download.json | 10 -
zh-cn/blog/dubbo-101.html | 350 ----
zh-cn/blog/dubbo-101.json | 10 -
zh-cn/blog/dubbo-27-features.html | 197 --
zh-cn/blog/dubbo-27-features.json | 10 -
zh-cn/blog/dubbo-admin.html | 96 -
zh-cn/blog/dubbo-admin.json | 6 -
zh-cn/blog/dubbo-annotation-driven.html | 554 ------
zh-cn/blog/dubbo-annotation-driven.json | 6 -
zh-cn/blog/dubbo-annotation.html | 356 ----
zh-cn/blog/dubbo-annotation.json | 10 -
...o-basic-usage-dubbo-consumer-configuration.html | 247 ---
...o-basic-usage-dubbo-consumer-configuration.json | 6 -
...o-basic-usage-dubbo-provider-configuration.html | 400 ----
...o-basic-usage-dubbo-provider-configuration.json | 10 -
zh-cn/blog/dubbo-cluster-error-handling.html | 232 ---
zh-cn/blog/dubbo-cluster-error-handling.json | 10 -
zh-cn/blog/dubbo-compatible.html | 198 --
zh-cn/blog/dubbo-compatible.json | 10 -
zh-cn/blog/dubbo-context-information.html | 156 --
zh-cn/blog/dubbo-context-information.json | 10 -
zh-cn/blog/dubbo-contribute-to-opensource.html | 157 --
zh-cn/blog/dubbo-contribute-to-opensource.json | 10 -
zh-cn/blog/dubbo-copywriting-style.html | 396 ----
zh-cn/blog/dubbo-copywriting-style.json | 10 -
zh-cn/blog/dubbo-echo-test.html | 111 --
zh-cn/blog/dubbo-echo-test.json | 6 -
zh-cn/blog/dubbo-externalized-configuration.html | 543 ------
zh-cn/blog/dubbo-externalized-configuration.json | 6 -
zh-cn/blog/dubbo-fescar.html | 215 ---
zh-cn/blog/dubbo-fescar.json | 10 -
zh-cn/blog/dubbo-generic-invoke.html | 171 --
zh-cn/blog/dubbo-generic-invoke.json | 10 -
zh-cn/blog/dubbo-gracefully-shutdown.html | 130 --
zh-cn/blog/dubbo-gracefully-shutdown.json | 10 -
zh-cn/blog/dubbo-heartbeat-design.html | 358 ----
zh-cn/blog/dubbo-heartbeat-design.json | 10 -
zh-cn/blog/dubbo-integrate-with-hystrix.html | 198 --
zh-cn/blog/dubbo-integrate-with-hystrix.json | 10 -
zh-cn/blog/dubbo-invoke.html | 193 --
zh-cn/blog/dubbo-invoke.json | 10 -
zh-cn/blog/dubbo-k8s.html | 120 --
zh-cn/blog/dubbo-k8s.json | 10 -
zh-cn/blog/dubbo-loadbalance.html | 251 ---
zh-cn/blog/dubbo-loadbalance.json | 10 -
zh-cn/blog/dubbo-local-call.html | 85 -
zh-cn/blog/dubbo-local-call.json | 6 -
zh-cn/blog/dubbo-meet-arthas.html | 325 ----
zh-cn/blog/dubbo-meet-arthas.json | 10 -
zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html | 41 -
zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json | 10 -
zh-cn/blog/dubbo-meetup-chengdu.html | 41 -
zh-cn/blog/dubbo-meetup-chengdu.json | 10 -
zh-cn/blog/dubbo-meetup-hangzhou.html | 43 -
zh-cn/blog/dubbo-meetup-hangzhou.json | 10 -
.../blog/dubbo-meetup-shanghai-jun-23rd-2018.html | 41 -
.../blog/dubbo-meetup-shanghai-jun-23rd-2018.json | 10 -
zh-cn/blog/dubbo-meetup-shenzhen.html | 40 -
zh-cn/blog/dubbo-meetup-shenzhen.json | 10 -
zh-cn/blog/dubbo-mesh-in-thinking.html | 115 --
zh-cn/blog/dubbo-mesh-in-thinking.json | 10 -
zh-cn/blog/dubbo-mesh-service-mesh-exploring.html | 147 --
zh-cn/blog/dubbo-mesh-service-mesh-exploring.json | 10 -
zh-cn/blog/dubbo-network-interfaces.html | 406 -----
zh-cn/blog/dubbo-network-interfaces.json | 10 -
zh-cn/blog/dubbo-new-async.html | 412 -----
zh-cn/blog/dubbo-new-async.json | 10 -
zh-cn/blog/dubbo-protocol.html | 195 --
zh-cn/blog/dubbo-protocol.json | 10 -
zh-cn/blog/dubbo-registry-nacos-integration.html | 435 -----
zh-cn/blog/dubbo-registry-nacos-integration.json | 6 -
zh-cn/blog/dubbo-rest.html | 671 -------
zh-cn/blog/dubbo-rest.json | 6 -
zh-cn/blog/dubbo-stub-mock.html | 238 ---
zh-cn/blog/dubbo-stub-mock.json | 6 -
zh-cn/blog/dubbo-zk.html | 275 ---
zh-cn/blog/dubbo-zk.json | 10 -
zh-cn/blog/dubbo2-js.html | 243 ---
zh-cn/blog/dubbo2-js.json | 10 -
zh-cn/blog/dubboAsync_client.html | 102 --
zh-cn/blog/dubboAsync_client.json | 10 -
zh-cn/blog/dubboAsync_server.html | 103 --
zh-cn/blog/dubboAsync_server.json | 10 -
zh-cn/blog/first-dubbo-filter.html | 200 --
zh-cn/blog/first-dubbo-filter.json | 6 -
zh-cn/blog/gsoc-2018.html | 34 -
zh-cn/blog/gsoc-2018.json | 10 -
zh-cn/blog/how-to-involve-dubbo-community.html | 107 --
zh-cn/blog/how-to-involve-dubbo-community.json | 10 -
zh-cn/blog/index.html | 32 -
zh-cn/blog/introduction-to-dubbo-qos.html | 245 ---
zh-cn/blog/introduction-to-dubbo-qos.json | 10 -
zh-cn/blog/introduction-to-dubbo-spi-2.html | 395 ----
zh-cn/blog/introduction-to-dubbo-spi-2.json | 10 -
zh-cn/blog/introduction-to-dubbo-spi.html | 217 ---
zh-cn/blog/introduction-to-dubbo-spi.json | 10 -
zh-cn/blog/introduction-to-dubbo-url.html | 153 --
zh-cn/blog/introduction-to-dubbo-url.json | 10 -
zh-cn/blog/meet-dubbo.html | 68 -
zh-cn/blog/meet-dubbo.json | 10 -
zh-cn/blog/optimization-branch-prediction.html | 151 --
zh-cn/blog/optimization-branch-prediction.json | 8 -
zh-cn/blog/pinpoint.html | 411 -----
zh-cn/blog/pinpoint.json | 10 -
zh-cn/blog/prepare-an-apache-release.html | 438 -----
zh-cn/blog/prepare-an-apache-release.json | 10 -
zh-cn/blog/qcon-beijing-2018.html | 34 -
zh-cn/blog/qcon-beijing-2018.json | 10 -
zh-cn/blog/sentinel-introduction-for-dubbo.html | 137 --
zh-cn/blog/sentinel-introduction-for-dubbo.json | 10 -
zh-cn/blog/service-and-version.html | 213 ---
zh-cn/blog/service-and-version.json | 6 -
zh-cn/blog/service-test.html | 179 --
zh-cn/blog/service-test.json | 6 -
.../spring-boot-dubbo-start-stop-analysis.html | 220 ---
.../spring-boot-dubbo-start-stop-analysis.json | 10 -
zh-cn/blog/test-verification.html | 111 --
zh-cn/blog/test-verification.json | 6 -
zh-cn/blog/tracing-with-skywalking.html | 138 --
zh-cn/blog/tracing-with-skywalking.json | 10 -
zh-cn/blog/use-zipkin-in-dubbo.html | 538 ------
zh-cn/blog/use-zipkin-in-dubbo.json | 10 -
zh-cn/community/index.html | 32 -
zh-cn/docs/admin/README.html | 33 -
zh-cn/docs/admin/README.json | 6 -
zh-cn/docs/admin/SUMMARY.html | 41 -
zh-cn/docs/admin/SUMMARY.json | 6 -
zh-cn/docs/admin/install/admin-console.html | 61 -
zh-cn/docs/admin/install/admin-console.json | 6 -
zh-cn/docs/admin/install/consumer-demo.html | 44 -
zh-cn/docs/admin/install/consumer-demo.json | 6 -
zh-cn/docs/admin/install/introduction.html | 45 -
zh-cn/docs/admin/install/introduction.json | 6 -
zh-cn/docs/admin/install/provider-demo.html | 43 -
zh-cn/docs/admin/install/provider-demo.json | 6 -
zh-cn/docs/admin/install/redis.html | 72 -
zh-cn/docs/admin/install/redis.json | 6 -
.../docs/admin/install/simple-monitor-center.html | 34 -
.../docs/admin/install/simple-monitor-center.json | 6 -
.../docs/admin/install/simple-registry-center.html | 33 -
.../docs/admin/install/simple-registry-center.json | 6 -
zh-cn/docs/admin/install/zookeeper.html | 101 -
zh-cn/docs/admin/install/zookeeper.json | 6 -
zh-cn/docs/admin/introduction.html | 95 -
zh-cn/docs/admin/introduction.json | 6 -
zh-cn/docs/admin/ops/dubbo-ops.html | 45 -
zh-cn/docs/admin/ops/dubbo-ops.json | 6 -
zh-cn/docs/admin/ops/introduction.html | 33 -
zh-cn/docs/admin/ops/introduction.json | 6 -
zh-cn/docs/admin/ops/pinpoint.html | 411 -----
zh-cn/docs/admin/ops/pinpoint.json | 6 -
zh-cn/docs/admin/ops/skywalking.html | 138 --
zh-cn/docs/admin/ops/skywalking.json | 6 -
zh-cn/docs/admin/serviceGovernance.html | 68 -
zh-cn/docs/admin/serviceGovernance.json | 6 -
zh-cn/docs/admin/serviceSearch.html | 37 -
zh-cn/docs/admin/serviceSearch.json | 6 -
zh-cn/docs/admin/serviceTest.html | 33 -
zh-cn/docs/admin/serviceTest.json | 6 -
zh-cn/docs/dev/README.html | 33 -
zh-cn/docs/dev/README.json | 6 -
zh-cn/docs/dev/SPI.html | 203 ---
zh-cn/docs/dev/SPI.json | 6 -
zh-cn/docs/dev/SUMMARY.html | 87 -
zh-cn/docs/dev/SUMMARY.json | 6 -
zh-cn/docs/dev/TCK.html | 46 -
zh-cn/docs/dev/TCK.json | 6 -
zh-cn/docs/dev/build.html | 81 -
zh-cn/docs/dev/build.json | 6 -
zh-cn/docs/dev/checklist.html | 59 -
zh-cn/docs/dev/checklist.json | 6 -
zh-cn/docs/dev/code-smell.html | 160 --
zh-cn/docs/dev/code-smell.json | 6 -
zh-cn/docs/dev/coding.html | 91 -
zh-cn/docs/dev/coding.json | 6 -
zh-cn/docs/dev/contract.html | 45 -
zh-cn/docs/dev/contract.json | 6 -
zh-cn/docs/dev/contribution.html | 352 ----
zh-cn/docs/dev/contribution.json | 6 -
zh-cn/docs/dev/design.html | 114 --
zh-cn/docs/dev/design.json | 6 -
zh-cn/docs/dev/implementation.html | 209 ---
zh-cn/docs/dev/implementation.json | 6 -
zh-cn/docs/dev/impls/cache.html | 94 -
zh-cn/docs/dev/impls/cache.json | 6 -
zh-cn/docs/dev/impls/cluster.html | 89 -
zh-cn/docs/dev/impls/cluster.json | 6 -
zh-cn/docs/dev/impls/compiler.html | 71 -
zh-cn/docs/dev/impls/compiler.json | 6 -
zh-cn/docs/dev/impls/container.html | 77 -
zh-cn/docs/dev/impls/container.json | 6 -
zh-cn/docs/dev/impls/dispatcher.html | 77 -
zh-cn/docs/dev/impls/dispatcher.json | 6 -
zh-cn/docs/dev/impls/exchanger.html | 100 -
zh-cn/docs/dev/impls/exchanger.json | 6 -
zh-cn/docs/dev/impls/exporter-listener.html | 78 -
zh-cn/docs/dev/impls/exporter-listener.json | 6 -
zh-cn/docs/dev/impls/extension-factory.html | 72 -
zh-cn/docs/dev/impls/extension-factory.json | 6 -
zh-cn/docs/dev/impls/filter.html | 104 --
zh-cn/docs/dev/impls/filter.json | 6 -
zh-cn/docs/dev/impls/introduction.html | 34 -
zh-cn/docs/dev/impls/introduction.json | 6 -
zh-cn/docs/dev/impls/invoker-listener.html | 77 -
zh-cn/docs/dev/impls/invoker-listener.json | 6 -
zh-cn/docs/dev/impls/load-balance.html | 78 -
zh-cn/docs/dev/impls/load-balance.json | 6 -
zh-cn/docs/dev/impls/logger-adapter.html | 93 -
zh-cn/docs/dev/impls/logger-adapter.json | 6 -
zh-cn/docs/dev/impls/merger.html | 74 -
zh-cn/docs/dev/impls/merger.json | 6 -
zh-cn/docs/dev/impls/monitor.html | 87 -
zh-cn/docs/dev/impls/monitor.json | 6 -
zh-cn/docs/dev/impls/networker.html | 74 -
zh-cn/docs/dev/impls/networker.json | 6 -
zh-cn/docs/dev/impls/page.html | 76 -
zh-cn/docs/dev/impls/page.json | 6 -
zh-cn/docs/dev/impls/protocol.html | 160 --
zh-cn/docs/dev/impls/protocol.json | 6 -
zh-cn/docs/dev/impls/proxy-factory.html | 80 -
zh-cn/docs/dev/impls/proxy-factory.json | 6 -
zh-cn/docs/dev/impls/registry.html | 207 ---
zh-cn/docs/dev/impls/registry.json | 6 -
zh-cn/docs/dev/impls/remoting.html | 133 --
zh-cn/docs/dev/impls/remoting.json | 6 -
zh-cn/docs/dev/impls/router.html | 76 -
zh-cn/docs/dev/impls/router.json | 6 -
zh-cn/docs/dev/impls/serialize.html | 89 -
zh-cn/docs/dev/impls/serialize.json | 6 -
zh-cn/docs/dev/impls/status-checker.html | 79 -
zh-cn/docs/dev/impls/status-checker.json | 6 -
zh-cn/docs/dev/impls/telnet-handler.html | 89 -
zh-cn/docs/dev/impls/telnet-handler.json | 6 -
zh-cn/docs/dev/impls/threadpool.html | 75 -
zh-cn/docs/dev/impls/threadpool.json | 6 -
zh-cn/docs/dev/impls/validation.html | 85 -
zh-cn/docs/dev/impls/validation.json | 6 -
zh-cn/docs/dev/introduction.html | 33 -
zh-cn/docs/dev/introduction.json | 6 -
zh-cn/docs/dev/principals/code-detail.html | 53 -
zh-cn/docs/dev/principals/code-detail.json | 6 -
zh-cn/docs/dev/principals/configuration.html | 96 -
zh-cn/docs/dev/principals/configuration.json | 6 -
zh-cn/docs/dev/principals/dummy.html | 210 ---
zh-cn/docs/dev/principals/dummy.json | 6 -
zh-cn/docs/dev/principals/expansibility.html | 43 -
zh-cn/docs/dev/principals/expansibility.json | 6 -
zh-cn/docs/dev/principals/extension.html | 118 --
zh-cn/docs/dev/principals/extension.json | 6 -
zh-cn/docs/dev/principals/general-knowledge.html | 68 -
zh-cn/docs/dev/principals/general-knowledge.json | 6 -
zh-cn/docs/dev/principals/introduction.html | 34 -
zh-cn/docs/dev/principals/introduction.json | 6 -
zh-cn/docs/dev/principals/robustness.html | 81 -
zh-cn/docs/dev/principals/robustness.json | 6 -
zh-cn/docs/dev/release.html | 65 -
zh-cn/docs/dev/release.json | 6 -
.../committer-guide/apache-dubbo-page_dev.html | 48 -
.../committer-guide/apache-dubbo-page_dev.json | 6 -
.../committer-guide/label-an-issue-guide_dev.html | 69 -
.../committer-guide/label-an-issue-guide_dev.json | 6 -
.../committer-guide/new-committer-guide_dev.html | 103 --
.../committer-guide/new-committer-guide_dev.json | 6 -
.../developers/committer-guide/release-guide.html | 34 -
.../developers/committer-guide/release-guide.json | 6 -
.../committer-guide/release-guide_dev.html | 401 ----
.../committer-guide/release-guide_dev.json | 9 -
.../committer-guide/website-guide_dev.html | 37 -
.../committer-guide/website-guide_dev.json | 6 -
.../contributor-guide/become-a-committer_dev.html | 34 -
.../contributor-guide/become-a-committer_dev.json | 6 -
.../contributor-guide/cla-signing-guide_dev.html | 59 -
.../contributor-guide/cla-signing-guide_dev.json | 6 -
.../dubbo-extension-guide_dev.html | 66 -
.../dubbo-extension-guide_dev.json | 6 -
.../mailing-list-subscription-guide_dev.html | 111 --
.../mailing-list-subscription-guide_dev.json | 6 -
.../new-contributor-guide_dev.html | 58 -
.../new-contributor-guide_dev.json | 6 -
.../reporting-security-issues_dev.html | 46 -
.../reporting-security-issues_dev.json | 6 -
.../software-donation-guide_dev.html | 144 --
.../software-donation-guide_dev.json | 6 -
.../contributor-guide/test-coverage-guide_dev.html | 53 -
.../contributor-guide/test-coverage-guide_dev.json | 6 -
zh-cn/docs/developers/developers_dev.html | 344 ----
zh-cn/docs/developers/developers_dev.json | 6 -
zh-cn/docs/developers/guide_dev.html | 108 --
zh-cn/docs/developers/guide_dev.json | 6 -
zh-cn/docs/developers/user-guide/faq_dev.html | 48 -
zh-cn/docs/developers/user-guide/faq_dev.json | 6 -
.../docs/source_code_guide/adaptive-extension.html | 697 -------
.../docs/source_code_guide/adaptive-extension.json | 10 -
zh-cn/docs/source_code_guide/cluster.html | 559 ------
zh-cn/docs/source_code_guide/cluster.json | 10 -
zh-cn/docs/source_code_guide/directory.html | 516 ------
zh-cn/docs/source_code_guide/directory.json | 10 -
zh-cn/docs/source_code_guide/dubbo-spi.html | 394 ----
zh-cn/docs/source_code_guide/dubbo-spi.json | 10 -
zh-cn/docs/source_code_guide/export-service.html | 1387 --------------
zh-cn/docs/source_code_guide/export-service.json | 10 -
zh-cn/docs/source_code_guide/loadbalance.html | 745 --------
zh-cn/docs/source_code_guide/loadbalance.json | 10 -
zh-cn/docs/source_code_guide/refer-service.html | 856 ---------
zh-cn/docs/source_code_guide/refer-service.json | 10 -
zh-cn/docs/source_code_guide/router.html | 460 -----
zh-cn/docs/source_code_guide/router.json | 10 -
.../service-invoking-process.html | 1921 --------------------
.../service-invoking-process.json | 10 -
zh-cn/docs/user/README.html | 34 -
zh-cn/docs/user/README.json | 6 -
zh-cn/docs/user/SUMMARY.html | 164 --
zh-cn/docs/user/SUMMARY.json | 6 -
zh-cn/docs/user/benchmark-tool.html | 72 -
zh-cn/docs/user/benchmark-tool.json | 6 -
zh-cn/docs/user/best-practice.html | 64 -
zh-cn/docs/user/best-practice.json | 10 -
zh-cn/docs/user/capacity-plan.html | 48 -
zh-cn/docs/user/capacity-plan.json | 10 -
zh-cn/docs/user/configuration/annotation.html | 97 -
zh-cn/docs/user/configuration/annotation.json | 6 -
zh-cn/docs/user/configuration/api.html | 143 --
zh-cn/docs/user/configuration/api.json | 6 -
zh-cn/docs/user/configuration/config-center.html | 129 --
zh-cn/docs/user/configuration/config-center.json | 6 -
.../configuration/configuration-load-process.html | 175 --
.../configuration/configuration-load-process.json | 6 -
zh-cn/docs/user/configuration/index.html | 33 -
zh-cn/docs/user/configuration/index.json | 6 -
.../user/configuration/properties deprecated.html | 65 -
.../user/configuration/properties deprecated.json | 6 -
.../user/configuration/properties-deprecated.html | 65 -
.../user/configuration/properties-deprecated.json | 6 -
zh-cn/docs/user/configuration/properties.html | 65 -
zh-cn/docs/user/configuration/properties.json | 6 -
zh-cn/docs/user/configuration/xml.html | 160 --
zh-cn/docs/user/configuration/xml.json | 6 -
zh-cn/docs/user/coveragence.html | 43 -
zh-cn/docs/user/coveragence.json | 6 -
zh-cn/docs/user/demos/accesslog.html | 40 -
zh-cn/docs/user/demos/accesslog.json | 6 -
zh-cn/docs/user/demos/async-call-deprecated.html | 82 -
zh-cn/docs/user/demos/async-call-deprecated.json | 6 -
zh-cn/docs/user/demos/async-call.html | 129 --
zh-cn/docs/user/demos/async-call.json | 6 -
.../docs/user/demos/async-execute-on-provider.html | 98 -
.../docs/user/demos/async-execute-on-provider.json | 6 -
zh-cn/docs/user/demos/attachment.html | 57 -
zh-cn/docs/user/demos/attachment.json | 6 -
zh-cn/docs/user/demos/callback-parameter.html | 129 --
zh-cn/docs/user/demos/callback-parameter.json | 6 -
zh-cn/docs/user/demos/concurrency-control.html | 70 -
zh-cn/docs/user/demos/concurrency-control.json | 6 -
zh-cn/docs/user/demos/config-connections.html | 57 -
zh-cn/docs/user/demos/config-connections.json | 6 -
zh-cn/docs/user/demos/config-rule-deprecated.html | 79 -
zh-cn/docs/user/demos/config-rule-deprecated.json | 6 -
zh-cn/docs/user/demos/config-rule.html | 202 --
zh-cn/docs/user/demos/config-rule.json | 6 -
zh-cn/docs/user/demos/context.html | 64 -
zh-cn/docs/user/demos/context.json | 6 -
zh-cn/docs/user/demos/delay-publish.html | 75 -
zh-cn/docs/user/demos/delay-publish.json | 6 -
zh-cn/docs/user/demos/distributed-transaction.html | 43 -
zh-cn/docs/user/demos/distributed-transaction.json | 6 -
zh-cn/docs/user/demos/dump.html | 46 -
zh-cn/docs/user/demos/dump.json | 6 -
zh-cn/docs/user/demos/echo-service.html | 49 -
zh-cn/docs/user/demos/echo-service.json | 6 -
zh-cn/docs/user/demos/events-notify.html | 112 --
zh-cn/docs/user/demos/events-notify.json | 6 -
zh-cn/docs/user/demos/explicit-target.html | 62 -
zh-cn/docs/user/demos/explicit-target.json | 6 -
zh-cn/docs/user/demos/fault-tolerent-strategy.html | 84 -
zh-cn/docs/user/demos/fault-tolerent-strategy.json | 6 -
zh-cn/docs/user/demos/generic-reference.html | 108 --
zh-cn/docs/user/demos/generic-reference.json | 6 -
zh-cn/docs/user/demos/generic-service.html | 66 -
zh-cn/docs/user/demos/generic-service.json | 6 -
zh-cn/docs/user/demos/graceful-shutdown.html | 53 -
zh-cn/docs/user/demos/graceful-shutdown.json | 6 -
zh-cn/docs/user/demos/group-merger.html | 71 -
zh-cn/docs/user/demos/group-merger.json | 6 -
zh-cn/docs/user/demos/hostname-binding.html | 111 --
zh-cn/docs/user/demos/hostname-binding.json | 6 -
zh-cn/docs/user/demos/index.html | 33 -
zh-cn/docs/user/demos/index.json | 6 -
zh-cn/docs/user/demos/introduction.html | 36 -
zh-cn/docs/user/demos/introduction.json | 6 -
zh-cn/docs/user/demos/lazy-connect.html | 43 -
zh-cn/docs/user/demos/lazy-connect.json | 6 -
zh-cn/docs/user/demos/loadbalance.html | 76 -
zh-cn/docs/user/demos/loadbalance.json | 6 -
zh-cn/docs/user/demos/local-call.html | 57 -
zh-cn/docs/user/demos/local-call.json | 6 -
zh-cn/docs/user/demos/local-mock.html | 101 -
zh-cn/docs/user/demos/local-mock.json | 6 -
zh-cn/docs/user/demos/local-stub.html | 71 -
zh-cn/docs/user/demos/local-stub.json | 6 -
zh-cn/docs/user/demos/logger-strategy.html | 52 -
zh-cn/docs/user/demos/logger-strategy.json | 6 -
zh-cn/docs/user/demos/metadata-report.html | 328 ----
zh-cn/docs/user/demos/metadata-report.json | 6 -
zh-cn/docs/user/demos/multi-protocols.html | 68 -
zh-cn/docs/user/demos/multi-protocols.json | 6 -
zh-cn/docs/user/demos/multi-registry.html | 103 --
zh-cn/docs/user/demos/multi-registry.json | 6 -
zh-cn/docs/user/demos/multi-versions.html | 62 -
zh-cn/docs/user/demos/multi-versions.json | 6 -
zh-cn/docs/user/demos/netty4.html | 64 -
zh-cn/docs/user/demos/netty4.json | 6 -
zh-cn/docs/user/demos/parameter-validation.html | 194 --
zh-cn/docs/user/demos/parameter-validation.json | 6 -
zh-cn/docs/user/demos/preflight-check.html | 63 -
zh-cn/docs/user/demos/preflight-check.json | 6 -
zh-cn/docs/user/demos/reference-config-cache.html | 56 -
zh-cn/docs/user/demos/reference-config-cache.json | 6 -
zh-cn/docs/user/demos/registry-only.html | 42 -
zh-cn/docs/user/demos/registry-only.json | 6 -
zh-cn/docs/user/demos/result-cache.html | 58 -
zh-cn/docs/user/demos/result-cache.json | 6 -
zh-cn/docs/user/demos/routing-rule deprecated.html | 207 ---
zh-cn/docs/user/demos/routing-rule deprecated.json | 6 -
zh-cn/docs/user/demos/routing-rule-deprecated.html | 207 ---
zh-cn/docs/user/demos/routing-rule-deprecated.json | 6 -
zh-cn/docs/user/demos/routing-rule.html | 254 ---
zh-cn/docs/user/demos/routing-rule.json | 6 -
zh-cn/docs/user/demos/serialization.html | 92 -
zh-cn/docs/user/demos/serialization.json | 6 -
zh-cn/docs/user/demos/service-container.html | 83 -
zh-cn/docs/user/demos/service-container.json | 6 -
zh-cn/docs/user/demos/service-downgrade.html | 51 -
zh-cn/docs/user/demos/service-downgrade.json | 6 -
zh-cn/docs/user/demos/service-group.html | 52 -
zh-cn/docs/user/demos/service-group.json | 6 -
zh-cn/docs/user/demos/set-host.html | 88 -
zh-cn/docs/user/demos/set-host.json | 6 -
zh-cn/docs/user/demos/simplify-registry-data.html | 328 ----
zh-cn/docs/user/demos/simplify-registry-data.json | 6 -
zh-cn/docs/user/demos/static-service.html | 52 -
zh-cn/docs/user/demos/static-service.json | 6 -
zh-cn/docs/user/demos/stickiness.html | 42 -
zh-cn/docs/user/demos/stickiness.json | 6 -
zh-cn/docs/user/demos/subscribe-only.html | 42 -
zh-cn/docs/user/demos/subscribe-only.json | 6 -
zh-cn/docs/user/demos/thread-model.html | 55 -
zh-cn/docs/user/demos/thread-model.json | 6 -
zh-cn/docs/user/demos/token-authorization.html | 51 -
zh-cn/docs/user/demos/token-authorization.json | 6 -
zh-cn/docs/user/dependencies.html | 94 -
zh-cn/docs/user/dependencies.json | 10 -
zh-cn/docs/user/languages/erlang/reference.html | 45 -
zh-cn/docs/user/languages/erlang/reference.json | 6 -
.../docs/user/languages/erlang/serialization.html | 60 -
.../docs/user/languages/erlang/serialization.json | 6 -
zh-cn/docs/user/languages/erlang/service.html | 75 -
zh-cn/docs/user/languages/erlang/service.json | 6 -
zh-cn/docs/user/languages/erlang/start.html | 77 -
zh-cn/docs/user/languages/erlang/start.json | 6 -
zh-cn/docs/user/maturity.html | 583 ------
zh-cn/docs/user/maturity.json | 10 -
zh-cn/docs/user/perf-test.html | 349 ----
zh-cn/docs/user/perf-test.json | 10 -
zh-cn/docs/user/preface/architecture.html | 138 --
zh-cn/docs/user/preface/architecture.json | 6 -
zh-cn/docs/user/preface/background.html | 43 -
zh-cn/docs/user/preface/background.json | 6 -
zh-cn/docs/user/preface/index.html | 33 -
zh-cn/docs/user/preface/index.json | 6 -
zh-cn/docs/user/preface/requirements.html | 39 -
zh-cn/docs/user/preface/requirements.json | 6 -
zh-cn/docs/user/preface/usage.html | 60 -
zh-cn/docs/user/preface/usage.json | 6 -
zh-cn/docs/user/quick-start.html | 140 --
zh-cn/docs/user/quick-start.json | 10 -
zh-cn/docs/user/recommend.html | 168 --
zh-cn/docs/user/recommend.json | 10 -
zh-cn/docs/user/references/api.html | 77 -
zh-cn/docs/user/references/api.json | 6 -
zh-cn/docs/user/references/maven.html | 48 -
zh-cn/docs/user/references/maven.json | 6 -
.../user/references/metadata/introduction.html | 328 ----
.../user/references/metadata/introduction.json | 6 -
.../user/references/metadata/metadata-redis.html | 33 -
.../user/references/metadata/metadata-redis.json | 6 -
.../references/metadata/metadata-zookeeper.html | 33 -
.../references/metadata/metadata-zookeeper.json | 6 -
zh-cn/docs/user/references/protocol/dubbo.html | 149 --
zh-cn/docs/user/references/protocol/dubbo.json | 6 -
zh-cn/docs/user/references/protocol/hessian.html | 85 -
zh-cn/docs/user/references/protocol/hessian.json | 6 -
zh-cn/docs/user/references/protocol/http.html | 81 -
zh-cn/docs/user/references/protocol/http.json | 6 -
.../user/references/protocol/introduction.html | 34 -
.../user/references/protocol/introduction.json | 6 -
zh-cn/docs/user/references/protocol/memcached.html | 66 -
zh-cn/docs/user/references/protocol/memcached.json | 6 -
zh-cn/docs/user/references/protocol/redis.html | 66 -
zh-cn/docs/user/references/protocol/redis.json | 6 -
zh-cn/docs/user/references/protocol/rest.html | 533 ------
zh-cn/docs/user/references/protocol/rest.json | 6 -
zh-cn/docs/user/references/protocol/rmi.html | 98 -
zh-cn/docs/user/references/protocol/rmi.json | 6 -
zh-cn/docs/user/references/protocol/thrift.html | 63 -
zh-cn/docs/user/references/protocol/thrift.json | 6 -
.../docs/user/references/protocol/webservice.html | 116 --
.../docs/user/references/protocol/webservice.json | 6 -
zh-cn/docs/user/references/qos.html | 225 ---
zh-cn/docs/user/references/qos.json | 6 -
.../user/references/registry/introduction.html | 34 -
.../user/references/registry/introduction.json | 6 -
zh-cn/docs/user/references/registry/multicast.html | 56 -
zh-cn/docs/user/references/registry/multicast.json | 6 -
zh-cn/docs/user/references/registry/nacos.html | 111 --
zh-cn/docs/user/references/registry/nacos.json | 6 -
zh-cn/docs/user/references/registry/redis.html | 95 -
zh-cn/docs/user/references/registry/redis.json | 6 -
zh-cn/docs/user/references/registry/simple.html | 65 -
zh-cn/docs/user/references/registry/simple.json | 6 -
zh-cn/docs/user/references/registry/zookeeper.html | 128 --
zh-cn/docs/user/references/registry/zookeeper.json | 6 -
zh-cn/docs/user/references/telnet.html | 123 --
zh-cn/docs/user/references/telnet.json | 6 -
.../user/references/xml/dubbo-application.html | 130 --
.../user/references/xml/dubbo-application.json | 6 -
zh-cn/docs/user/references/xml/dubbo-argument.html | 84 -
zh-cn/docs/user/references/xml/dubbo-argument.json | 6 -
.../user/references/xml/dubbo-config-center.html | 166 --
.../user/references/xml/dubbo-config-center.json | 6 -
zh-cn/docs/user/references/xml/dubbo-consumer.html | 230 ---
zh-cn/docs/user/references/xml/dubbo-consumer.json | 6 -
zh-cn/docs/user/references/xml/dubbo-method.html | 215 ---
zh-cn/docs/user/references/xml/dubbo-method.json | 6 -
zh-cn/docs/user/references/xml/dubbo-module.html | 90 -
zh-cn/docs/user/references/xml/dubbo-module.json | 6 -
zh-cn/docs/user/references/xml/dubbo-monitor.html | 70 -
zh-cn/docs/user/references/xml/dubbo-monitor.json | 6 -
.../docs/user/references/xml/dubbo-parameter.html | 78 -
.../docs/user/references/xml/dubbo-parameter.json | 6 -
zh-cn/docs/user/references/xml/dubbo-protocol.html | 290 ---
zh-cn/docs/user/references/xml/dubbo-protocol.json | 6 -
zh-cn/docs/user/references/xml/dubbo-provider.html | 490 -----
zh-cn/docs/user/references/xml/dubbo-provider.json | 6 -
.../docs/user/references/xml/dubbo-reference.html | 320 ----
.../docs/user/references/xml/dubbo-reference.json | 6 -
zh-cn/docs/user/references/xml/dubbo-registry.html | 230 ---
zh-cn/docs/user/references/xml/dubbo-registry.json | 6 -
zh-cn/docs/user/references/xml/dubbo-service.html | 360 ----
zh-cn/docs/user/references/xml/dubbo-service.json | 6 -
zh-cn/docs/user/references/xml/introduction.html | 52 -
zh-cn/docs/user/references/xml/introduction.json | 6 -
zh-cn/docs/user/rest.html | 955 ----------
zh-cn/docs/user/rest.json | 10 -
zh-cn/docs/user/serialization.html | 299 ---
zh-cn/docs/user/serialization.json | 6 -
zh-cn/docs/user/simple-monitor.html | 112 --
zh-cn/docs/user/simple-monitor.json | 6 -
zh-cn/docs/user/version-upgrading.html | 38 -
zh-cn/docs/user/version-upgrading.json | 6 -
zh-cn/docs/user/versions/index.html | 34 -
zh-cn/docs/user/versions/index.json | 6 -
zh-cn/docs/user/versions/version-270.html | 342 ----
zh-cn/docs/user/versions/version-270.json | 6 -
zh-cn/docs/user/versions/version-upgrading.html | 38 -
zh-cn/docs/user/versions/version-upgrading.json | 6 -
zh-cn/download/index.html | 32 -
zh-cn/index.html | 32 -
1023 files changed, 75158 deletions(-)
diff --git a/en-us/blog/apachecon-na-2018.html b/en-us/blog/apachecon-na-2018.html
deleted file mode 100644
index acd2ee9..0000000
--- a/en-us/blog/apachecon-na-2018.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, ApacheCon NA" />
- <meta name="description" content="This article will introduce you that the ApacheCon NA schedule has been announced attention." />
- <!-- 网页标签标题 -->
- <title>The ApacheCon NA schedule has been announced</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>Ian Luo(PMC) and Jun Liu(PMC) will talk about "Introducing Apache Dubbo(Incubating): What is Dubbo and How it Works" at ApacheCon NA this year in Montréal! Please check out the schedule <a href="https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/b8db9dc580d85853f">here</a> and register <a href="https://www.eventbrite.com/e/apachecon-north-america-2018-registration-43200327342">here</a>.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/apachecon-na-2018.json b/en-us/blog/apachecon-na-2018.json
deleted file mode 100644
index 2351fd0..0000000
--- a/en-us/blog/apachecon-na-2018.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "apachecon-na-2018.md",
- "__html": "<h2>The ApacheCon NA schedule has been announced</h2>\n<p>Ian Luo(PMC) and Jun Liu(PMC) will talk about "Introducing Apache Dubbo(Incubating): What is Dubbo and How it Works" at ApacheCon NA this year in Montréal! Please check out the schedule <a href=\"https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/b8db9dc580d85853f\">here</a> and register <a href=\"https://www.eventbrite.com/e/apachecon-north-america-2018-registration-43200327342\">here</a>.</p>\n",
- "link": "/en-us/blog/apachecon-na-2018.html",
- "meta": {
- "title": "The ApacheCon NA schedule has been announced",
- "keywords": "Dubbo, ApacheCon NA",
- "description": "This article will introduce you that the ApacheCon NA schedule has been announced attention."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/download.html b/en-us/blog/download.html
deleted file mode 100644
index 0d27efd..0000000
--- a/en-us/blog/download.html
+++ /dev/null
@@ -1,161 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Downloads, Version" />
- <meta name="description" content="This article will introduce you how to understand the details of each version and upgrade matters needing attention." />
- <!-- 网页标签标题 -->
- <title>Downloads</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Verification</h2>
-<p>you can follow these <a href="https://www.apache.org/info/verification">procedures</a> and the <a href="https://www.apache.org/dist/dubbo/KEYS">KEYS</a> file to verify the download files</p>
-<h2>Apache Dubbo</h2>
-<blockquote>
-<p>GitHub: <a href="https://github.com/apache/dubbo">https://github.com/apache/dubbo</a> <br>
-Release Notes: <a href="https://github.com/apache/dubbo/releases">https://github.com/apache/dubbo/releases</a></p>
-</blockquote>
-<h3>2.7.2 (2019-06-06)</h3>
-<ul>
-<li><a href="https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.2/apache-dubbo-2.7.2-src.zip">source</a> |
-<a href="https://www.apache.org/dist/dubbo/2.7.2/apache-dubbo-2.7.2-src.zip.asc">asc</a> |
-<a href="https://www.apache.org/dist/dubbo/2.7.2/apache-dubbo-2.7.2-src.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.7.1 (2019-03-26)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.7.0 (2019-01-29)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.6.6 (2019-03-07)</h3>
-<ul>
-<li><a href="https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip">source</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip.asc">asc</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip">binary</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip.asc">asc</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.6.5 (2018-11-23)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.6.4 (2018-10-08)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.6.3 (2018-09-11)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.6.2 (2018-06-07)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h2>Dubbo Spring Boot Starter</h2>
-<blockquote>
-<p>GitHub: <a href="https://github.com/apache/incubator-dubbo-spring-boot-project">https://github.com/apache/incubator-dubbo-spring-boot-project</a> <br>
-Release Notes: <a href="https://github.com/apache/incubator-dubbo-spring-boot-project/releases">https://github.com/apache/incubator-dubbo-spring-boot-project/releases</a></p>
-</blockquote>
-<h3>2.7.1 (2019-04-09)</h3>
-<ul>
-<li><a href="https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip">source</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip.asc">asc</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip">binary</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip.asc">asc</a> |
-<a href="https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>2.7.0 (2019-02-14)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>0.2.1 (2019-01-27)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h3>0.1.2 (2019-01-27)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip.sha512">sha512</a></li>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip">binary</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip.sha512">sha512</a></li>
-</ul>
-<h2>Dubbo Admin</h2>
-<blockquote>
-<p>GitHub: <a href="https://github.com/apache/incubator-dubbo-admin">https://github.com/apache/incubator-dubbo-admin</a> <br>
-Release Notes: <a href="https://github.com/apache/incubator-dubbo-admin/releases">https://github.com/apache/incubator-dubbo-admin/releases</a></p>
-</blockquote>
-<h3>0.1 (2019-02-15)</h3>
-<ul>
-<li><a href="https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip">source</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip.asc">asc</a> |
-<a href="https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip.sha512">sha512</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/download.json b/en-us/blog/download.json
deleted file mode 100644
index bebdbe2..0000000
--- a/en-us/blog/download.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "download.md",
- "__html": "<h1>Downloads</h1>\n<h2>Verification</h2>\n<p>you can follow these <a href=\"https://www.apache.org/info/verification\">procedures</a> and the <a href=\"https://www.apache.org/dist/dubbo/KEYS\">KEYS</a> file to verify the download files</p>\n<h2>Apache Dubbo</h2>\n<blockquote>\n<p>GitHub: <a href=\"https://github.com/apache/dubbo\">https://github.com/apache/dubbo</a> <br>\nRelease Notes: <a href=\"https://github.com/apache/dubbo/releases\">https://github.com/apache/dubbo/rel [...]
- "link": "/en-us/blog/download.html",
- "meta": {
- "title": "Downloads",
- "keywords": "Dubbo, Downloads, Version",
- "description": "This article will introduce you how to understand the details of each version and upgrade matters needing attention."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-101.html b/en-us/blog/dubbo-101.html
deleted file mode 100644
index 6f54f0b..0000000
--- a/en-us/blog/dubbo-101.html
+++ /dev/null
@@ -1,346 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, RPC, RMI" />
- <meta name="description" content="Modern distributed frameworks is similiar to RMI in terms of concepts. They both use Java interface as a service contract, archive service registry and discovery by a registry center, and Shield communication details by a proxy." />
- <!-- 网页标签标题 -->
- <title>Your First Dubbo Demo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Java RMI Introduction</h2>
-<p>Java RMI (Remote Method Invocation) is a mechanism that allows users to access or invocate an object and a method running on another JVM (Java Virtual Machine). RMI is an implementation of RPC (Remote Procedure Call) in java with support of OOP (Object Oriented Paradigms). Instead of bothering IDL (Interface Define Language), users can build distributed applications by depending on interfaces in an easy and natural way.</p>
-<h3>Java RMI Work Flow</h3>
-<p>Here is how a typical RMI invocation usually works：</p>
-<ol>
-<li>The server registers service from RMI and binds its address.</li>
-<li>The client registers service from RMI and obtains target address.</li>
-<li>The client invokes methods of local stub object in the same way of invoking other local objects.</li>
-<li>Local stub object zips invoking information and send it to the server via network.</li>
-<li>The Skeleton object of server receives the network request and unzips the information.</li>
-<li>Server runs invocation on the target object based on the information and return the zipped results back to client via network.</li>
-</ol>
-<p><img src="../../img/blog/rmi-flow.png" alt="RMI Flow"></p>
-<p>(source：<a href="https://www.cs.rutgers.edu/~pxk/417/notes/images/rpc-rmi_flow.png">https://www.cs.rutgers.edu/~pxk/417/notes/images/rpc-rmi_flow.png</a>)</p>
-<h3>Java RMI Concepts</h3>
-<p>Java RMI is a technique foundation stone of creating distributed applications in Java. The following EJB techniques and current framework of distributed services still inherit the fundamental concepts of Java RMI. In RMI invocation, there are some core concepts：</p>
-<ol>
-<li>The invocation is run remotely on <strong>interface</strong>.</li>
-<li>Disguise remote invocation as local invocation by <strong>Stub object</strong> on client and <strong>Skeleton object</strong> on server.</li>
-<li>The service is registered and looked up by <strong>RMI</strong> registry service.</li>
-</ol>
-<p>For 1. users are dependent on interfaces which should be implemented by server.</p>
-<p>For 2. In J2SE 1.5 version and before, it needs to pre-compile Stub on client and Skeleton on server by rmic. In the later versions there is no need to do so.</p>
-<p>The following is a code example of registry and look-up in RMI.</p>
-<h4>Server service registry</h4>
-<pre><code class="language-java">Hello obj = <span class="hljs-keyword">new</span> HelloImpl(); <span class="hljs-comment">// #1</span>
-Hello stub = (Hello) UnicastRemoteObject.exportObject(obj, <span class="hljs-number">0</span>); <span class="hljs-comment">// #2</span>
-Registry registry = LocateRegistry.createRegistry(<span class="hljs-number">1099</span>); <span class="hljs-comment">// #3</span>
-registry.rebind(<span class="hljs-string">"Hello"</span>, stub); <span class="hljs-comment">// #4</span>
-</code></pre>
-<p>Notes:</p>
-<ol>
-<li>
-<p>Initiate service object instance.</p>
-</li>
-<li>
-<p>Create stub object to communicate with the server by UnicastRemoteObject.exportObject.</p>
-</li>
-<li>
-<p>Create a local RMI registry service on port 1099 which is run on server. It can also be registered as an independent process.</p>
-</li>
-<li>
-<p>Bind stub object into registry so the client can find the remote object by looking up Hello.</p>
-</li>
-</ol>
-<h4>Client service look-up</h4>
-<pre><code class="language-java">Registry registry = LocateRegistry.getRegistry(); <span class="hljs-comment">// #1</span>
-Hello stub = (Hello) registry.lookup(<span class="hljs-string">"Hello"</span>); <span class="hljs-comment">// #2</span>
-String response = stub.sayHello(); <span class="hljs-comment">// #3</span>
-</code></pre>
-<p>Notes:</p>
-<ol>
-<li>Acquire registry service instances. In this case, there is no input parameters so it is assumed that the acquired instance is located on port 1099.</li>
-<li>Look up the remote object named Hello in registry service.</li>
-<li>Run a RMI invocation via acquired Stub object and get results.
-Understand the work flow and basic concepts of RMI is helpful to handle current framework of distributed service. It is recommended to refer to RMI official documents for further information[^1].</li>
-</ol>
-<h2>Basic Concepts of Dubbo</h2>
-<p>The basic concepts of current framework of distributed service is similar to the one of RMI. They both use Java interface as service contract, register and look up by registry center and use agency to block the details of remote communications. Specifically, Dubbo has following four types of roles to play when running：</p>
-<ol>
-<li>Serve the provider – Expose service at assigned ports at initialization and register the service address and ports at registry center</li>
-<li>Serve the consumer – Subscribe the service of interests at registry center at initialization to acquire the list of addresses provided by the service provider.</li>
-<li>Registry center – Register and look up service. Store the address provided by the service provider and send it to the consumer.</li>
-<li>Monitor center – Collect and monitor running status of providers and consumers, e.g., times of invocations, delay of invocations, etc.</li>
-<li>Running container – Initialize and load the provider and manage the lifecycle of running.</li>
-</ol>
-<p><img src="../../img/blog/dubbo-architecture.png" alt="dubbo-architecture"></p>
-<p><strong>Deploy stage</strong></p>
-<ul>
-<li>Service providers expose service at assigned ports and register information of service at registry center.</li>
-<li>Service consumers subscribe the list of service addresses from registry center.</li>
-</ul>
-<p><strong>Run stage</strong></p>
-<ul>
-<li>Registry center sends the address to service consumers.</li>
-<li>After receiving the list of addresses, service consumers select one of them and invoke an object service.</li>
-<li>During invocation, the running status of service providers and consumers is reported to the monitor center.</li>
-</ul>
-<h2>Dubbo Applications Based on API</h2>
-<p>The applications of Dubbo are usually assembled by Spring. To obtain an available Dubbo application quickly, the example shown here abandons complex configurations but to create service provider and consumer in Dubbo API oriented way. Additionally, the registry center and monitor center do not need installation or configuration in this example.</p>
-<p>In production environment, the service of Dubbo usually requires cooperation with a distributed service registry center, such as ZooKeeper. For convenience, Dubbo offers two ways to avoid extra work of building registry center, namely direct connection [2] and assembled podcast [3] respectively. In this example, the latter way is applied to register and look up service.</p>
-<h3>Define Service Contract</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">GreetingsService</span> </span>{
- <span class="hljs-function">String <span class="hljs-title">sayHi</span><span class="hljs-params">(String name)</span></span>; <span class="hljs-comment">// #1</span>
-}
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>The codes define a simple service contract where there is only one function, sayHi, can be invoked. The type of input parameter and return value are both String.</li>
-</ol>
-<h3>Provide Contract Implementation</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">GreetingsServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">GreetingsService</span> </span>{ <span class="hljs-comment">// #1</span>
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHi</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hi, "</span> + name; <span class="hljs-comment">// #2</span>
- }
-}
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>Service providers need to implement the interface of service contract, GreetingsService.</li>
-<li>This function simply returns a welcome message. For example, if the input value is <em>dubbo</em>，it will return <em>hi, dubbo</em>.</li>
-</ol>
-<h3>Implement Dubbo Service Provider</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Application</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> <span class="hljs-keyword">throws</span> IOException </span>{
- ServiceConfig<GreetingsService> service = <span class="hljs-keyword">new</span> ServiceConfig<>(); <span class="hljs-comment">// #1</span>
- service.setApplication(<span class="hljs-keyword">new</span> ApplicationConfig(<span class="hljs-string">"first-dubbo-provider"</span>)); <span class="hljs-comment">// #2</span>
- service.setRegistry(<span class="hljs-keyword">new</span> RegistryConfig(<span class="hljs-string">"multicast://224.5.6.7:1234"</span>)); <span class="hljs-comment">// #3</span>
- service.setInterface(GreetingsService.class); <span class="hljs-comment">// #4</span>
- service.setRef(<span class="hljs-keyword">new</span> GreetingsServiceImpl()); <span class="hljs-comment">// #5</span>
- service.export(); <span class="hljs-comment">// #6</span>
- System.in.read(); <span class="hljs-comment">// #7</span>
- }
-}
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>Create an instance <em>ServiceConfig</em> with service interface type as generics parameters, which is <em>GreetingsService</em> in this example.</li>
-<li>Generate an instance of <em>ApplicationConfig</em> and assemble it into <em>ServiceConfig</em>.</li>
-<li>Generate an instance <em>RegistryConfig</em> and assemble it into <em>ServiceConfig</em>. Since the assembled way is applied here, the parameter should be <code>multicast://224.5.6.7:1234</code>. The valid range of assembled address is <em>224.0.0.0 - 239.255.255.255</em></li>
-<li>Assemble the service contract <em>GreetingsService</em> into <em>ServiceConfig</em>.</li>
-<li>Assemble the instance with implementation of <em>GreetingsServicelmpl</em> provided by service providers into <em>ServiceConfig</em>.</li>
-<li><em>ServiceConfig</em> starts to expose itself at default ports <em>20880</em>. after being equipped with enough information.</li>
-<li>Press any key or <em>ctrl-C</em> to exit to avoid server halt.</li>
-</ol>
-<h3>Implement Dubbo Service Consumer</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Application</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- ReferenceConfig<GreetingsService> reference = <span class="hljs-keyword">new</span> ReferenceConfig<>(); <span class="hljs-comment">// #1</span>
- reference.setApplication(<span class="hljs-keyword">new</span> ApplicationConfig(<span class="hljs-string">"first-dubbo-client"</span>)); <span class="hljs-comment">// #2</span>
- reference.setRegistry(<span class="hljs-keyword">new</span> RegistryConfig(<span class="hljs-string">"multicast://224.5.6.7:1234"</span>)); <span class="hljs-comment">// #3</span>
- reference.setInterface(GreetingsService.class); <span class="hljs-comment">// #4</span>
- GreetingsService greetingsService = reference.get(); <span class="hljs-comment">// #5</span>
- String message = greetingsService.sayHi(<span class="hljs-string">"dubbo"</span>); <span class="hljs-comment">// #6</span>
- System.out.println(message); <span class="hljs-comment">// #7</span>
- }
-}
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>Create an instance of <em>ReferenceConfig</em> with service interface type as generics parameters, which is <em>GreetingsService</em> in this example.</li>
-<li>Create an instance of <em>AplicatonConfig</em>, and assemble it into <em>ReferenceConfig</em>.</li>
-<li>Generate an instance <em>RegistryConfig</em>, and assemble it into <em>ReferenceConfig</em>. Note that the address information here should be the same as the one of the service provider.</li>
-<li>Assemble the service contract <em>GreetingsService</em> into <em>ReferenceConfig</em>.</li>
-<li>Obtain the agency of <em>GreetingsService</em> from <em>ReferenceConfig</em>.</li>
-<li>Invoke a remote call through <em>GreetingsSerive</em>’s agency and pass in <code>dubbo</code> as input parameter.</li>
-<li>Return and print results <code>hi, dubbo</code>.</li>
-</ol>
-<h3>Run</h3>
-<p>The complete example can be found at <a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-api">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-api</a>. In the complete version, it is convenient to execute by maven in command line with the configuration of <em>exec-maven-plugin</em>. Of course, it can also be executed directly in IDE. However, there is one noteworthy thing that because of using assembled way to look up service, it needs to assign < [...]
-<h4>Build Example</h4>
-<p>Synchronize the example codes and build by the following command lines:</p>
-<ol>
-<li>Synchronize the example codes: git clone <a href="https://github.com/dubbo/dubbo-samples.git">https://github.com/dubbo/dubbo-samples.git</a></li>
-<li>Build：mvn clean package</li>
-</ol>
-<pre><code class="language-bash">$ git <span class="hljs-built_in">clone</span> https://github.com/dubbo/dubbo-samples.git
-$ <span class="hljs-built_in">cd</span> dubbo-samples/dubbo-samples-api/
-$ mvn clean package
-INFO] Scanning <span class="hljs-keyword">for</span> projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ dubbo-samples-api ---
-...
-[INFO] ------------------------------------------------------------------------
-[INFO] BUILD SUCCESS
-[INFO] ------------------------------------------------------------------------
-[INFO] Total time: 2.182 s
-[INFO] Finished at: 2018-05-28T14:56:08+08:00
-[INFO] Final Memory: 20M/353M
-[INFO] ------------------------------------------------------------------------
-</code></pre>
-<p>The build is finished when it shows <code>BUILD SUCCESS</code>. Then comes the running stage.</p>
-<h4>Run the server</h4>
-<p>Run the service provider by the following maven command lines:</p>
-<pre><code class="language-bash">$ mvn -Djava.net.preferIPv4Stack=<span class="hljs-literal">true</span> -Dexec.mainClass=org.apache.dubbo.samples.provider.Application <span class="hljs-built_in">exec</span>:java
-[INFO] Scanning <span class="hljs-keyword">for</span> projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- <span class="hljs-built_in">exec</span>-maven-plugin:1.6.0:java (default-cli) @ dubbo-samples-api ---
-log4j:WARN No appenders could be found <span class="hljs-keyword">for</span> logger (org.apache.dubbo.common.logger.LoggerFactory).
-log4j:WARN Please initialize the log4j system properly.
-log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html<span class="hljs-comment">#noconfig for more info.</span>
-first-dubbo-provider is running.
-</code></pre>
-<p>When <em>first-dubbo-provider is running</em> appears, the service provider is ready to be called by the client.</p>
-<h4>Run the client</h4>
-<p>Run the service consumer by the following maven command lines:</p>
-<pre><code class="language-bash">$ mvn -Djava.net.preferIPv4Stack=<span class="hljs-literal">true</span> -Dexec.mainClass=org.apache.dubbo.samples.consumer.Application <span class="hljs-built_in">exec</span>:java
-[INFO] Scanning <span class="hljs-keyword">for</span> projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- <span class="hljs-built_in">exec</span>-maven-plugin:1.6.0:java (default-cli) @ dubbo-samples-api ---
-log4j:WARN No appenders could be found <span class="hljs-keyword">for</span> logger (org.apache.dubbo.common.logger.LoggerFactory).
-log4j:WARN Please initialize the log4j system properly.
-log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html<span class="hljs-comment">#noconfig for more info.</span>
-hi, dubbo
-</code></pre>
-<p><code>hi, dubbo</code> is the execution results from service provider.</p>
-<h2>Quick Creation of A Dubbo Application</h2>
-<p>Dubbo also provides a public platform that can create a Dubbo application quickly based on Spring Boot. Visit <a href="http://start.dubbo.io">http://start.dubbo.io</a> and follow the figure below to create an example project:</p>
-<p><img src="../../img/blog/dubbo-initializr.png" alt="dubbo initializr"></p>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>Provide maven groupId in <em>Group</em> with default value <code>com.example</code>.</li>
-<li>Provide maven artifactId in <em>Artifact</em> with default value <code>demo</code>.</li>
-<li>Provide the name of service in <em>DubboServiceName</em> with default value <code>com.example.HelloService</code>.</li>
-<li>Provide the version of service in <em>DubboServiceVersion</em> with default value <code>1.0.0</code>.</li>
-<li>Choose server or client in <em>Client/Server</em> with default value <code>server</code>.</li>
-<li><em>embeddedZookeeper</em> is selected by default as service registry look up.</li>
-<li>qos ports activation is not selected by default but if it is, it can be accessed by port <em>22222</em>.</li>
-<li>Click <em>Generate Project</em> to download the generated project.</li>
-</ol>
-<p>This example shows how to generate a server. Similarly, it can generate a <em>client</em> by selecting client on the generation interface.</p>
-<h3>Run</h3>
-<p>Open the generated project with an IDE and to see the application is a typical Spring Boot application with the following program entry:</p>
-<pre><code class="language-java"><span class="hljs-meta">@SpringBootApplication</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoApplication</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- <span class="hljs-keyword">new</span> EmbeddedZooKeeper(<span class="hljs-number">2181</span>, <span class="hljs-keyword">false</span>).start(); <span class="hljs-comment">// #1</span>
- SpringApplication.run(DemoApplication.class, args); <span class="hljs-comment">// #2</span>
- }
-}
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>Launch embedded <em>ZooKeeper</em> on port <em>2181</em>.</li>
-<li>Launch the context of <em>Spring Boot</em>.</li>
-</ol>
-<p>Run it directly in IDE and here are the results:</p>
-<pre><code class="language-bash">2018-05-28 16:59:38.072 INFO 59943 --- [ main] a.b.d.c.e.WelcomeLogoApplicationListener :
-
- ████████▄ ███ █▄ ▀█████████▄ ▀█████████▄ ▄██████▄
- ███ ▀███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ▄███▄▄▄██▀ ▄███▄▄▄██▀ ███ ███
- ███ ███ ███ ███ ▀▀███▀▀▀██▄ ▀▀███▀▀▀██▄ ███ ███
- ███ ███ ███ ███ ███ ██▄ ███ ██▄ ███ ███
- ███ ▄███ ███ ███ ███ ███ ███ ███ ███ ███
- ████████▀ ████████▀ ▄█████████▀ ▄█████████▀ ▀██████▀
-
-
- :: Dubbo Spring Boot (v0.1.0) : https://github.com/dubbo/dubbo-spring-boot-project
- :: Dubbo (v2.0.1) : https://github.com/alibaba/dubbo
- :: Google group : http://groups.google.com/group/dubbo
-
-2018-05-28 16:59:38.079 INFO 59943 --- [ main] e.OverrideDubboConfigApplicationListener : Dubbo Config was overridden by externalized configuration {dubbo.application.name=dubbo-demo-server, dubbo.application.qosAcceptForeignIp=<span class="hljs-literal">false</span>, dubbo.application.qosEnable=<span class="hljs-literal">true</span>, dubbo.application.qosPort=22222, dubbo.registry.address=zookeeper://localhost:2181?client=curator, dubbo.registry.id=my-registry, dubbo.scan.bas [...]
-
-...
-
-2018-05-28 16:59:39.624 INFO 59943 --- [ main] com.example.demo.DemoApplication : Started DemoApplication <span class="hljs-keyword">in</span> 1.746 seconds (JVM running <span class="hljs-keyword">for</span> 2.963)
-</code></pre>
-<p><strong>Notes</strong>：</p>
-<ol>
-<li>In the printouts, the configuration starting with <code>dubbo.</code> Is defined in <em>main/resources/application.properties</em>.</li>
-</ol>
-<h3>Manage service by Telnet</h3>
-<p>If <em>qos</em> is actived during generation, the service can be watched and managed by <em>telnet</em> or <em>nc</em>.</p>
-<pre><code class="language-bash">$ telnet localhost 22222
-Trying 127.0.0.1...
-Connected to localhost.
-Escape character is <span class="hljs-string">'^]'</span>.
- ████████▄ ███ █▄ ▀█████████▄ ▀█████████▄ ▄██████▄
- ███ ▀███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ▄███▄▄▄██▀ ▄███▄▄▄██▀ ███ ███
- ███ ███ ███ ███ ▀▀███▀▀▀██▄ ▀▀███▀▀▀██▄ ███ ███
- ███ ███ ███ ███ ███ ██▄ ███ ██▄ ███ ███
- ███ ▄███ ███ ███ ███ ███ ███ ███ ███ ███
- ████████▀ ████████▀ ▄█████████▀ ▄█████████▀ ▀██████▀
-
-
-dubbo>
-dubbo>ls
-As Provider side:
-+------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------+---+
-|com.example.HelloService:1.0.0| Y |
-+------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-</code></pre>
-<p>Currently, <em>qos</em> supports following command lines. For more information please refer to the official document. [^4]:</p>
-<ul>
-<li><em>ls</em>：List the information of client and server.</li>
-<li><em>online</em>：Bring the service online.</li>
-<li><em>offline</em>：Bring the service offline.</li>
-<li><em>help</em>：View online help.</li>
-</ul>
-<h2>Summary</h2>
-<p>In this tutorial, we start with RMI and introduce the basic concepts in Java distributed invocations. Based on interface programming, it disguises remote calls as local by agency and run the service registry and looking up by registry center.</p>
-<p>Then for simplicity, we introduce how to develop a complete Dubbo demo in an easy way of assembled registry and direct Dubbo API oriented programming. Additionally, we look into the usage of <em>ServiceConfig</em> and <em>RefenceConfig</em>, which is of great help for further using Spring XML configuration and the programming pattern of Spring Boot.</p>
-<p>Eventually, we give an outline of how to create a Dubbo application quickly based on Spring Boot using the public resources, <a href="http://start.dubbo.io">start.dubbo.io</a>, provided by the Dubbo development team and operate and maintain the Dubbo service by <em>qos</em>.</p>
-<hr>
-<ol>
-<li><a href="https://docs.oracle.com/javase/6/docs/technotes/guides/rmi/hello/hello-world.html">Getting Started Using JavaTM RMI</a></li>
-<li><a href="http://dubbo.apache.org/en-us/docs/user/demos/explicit-target.html">Explicit target</a></li>
-<li><a href="http://dubbo.apache.org/en-us/docs/user/references/registry/multicast.html">Multicast Registry</a></li>
-<li><a href="http://dubbo.apache.org/en-us/docs/user/references/qos.html">Online QOS command</a></li>
-</ol>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-101.json b/en-us/blog/dubbo-101.json
deleted file mode 100644
index dd2ae04..0000000
--- a/en-us/blog/dubbo-101.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-101.md",
- "__html": "<h1>Your First Dubbo Demo</h1>\n<h2>Java RMI Introduction</h2>\n<p>Java RMI (Remote Method Invocation) is a mechanism that allows users to access or invocate an object and a method running on another JVM (Java Virtual Machine). RMI is an implementation of RPC (Remote Procedure Call) in java with support of OOP (Object Oriented Paradigms). Instead of bothering IDL (Interface Define Language), users can build distributed applications by depending on interfaces in an easy and n [...]
- "link": "/en-us/blog/dubbo-101.html",
- "meta": {
- "title": "Your First Dubbo Demo",
- "keywords": "Dubbo, RPC, RMI",
- "description": "Modern distributed frameworks is similiar to RMI in terms of concepts. They both use Java interface as a service contract, archive service registry and discovery by a registry center, and Shield communication details by a proxy."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-annotation.html b/en-us/blog/dubbo-annotation.html
deleted file mode 100644
index 50b7c78..0000000
--- a/en-us/blog/dubbo-annotation.html
+++ /dev/null
@@ -1,335 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Annotation, Spring" />
- <meta name="description" content="This article will introduce you how to use annotations instead of XML to develop Dubbo applications, such as `@EnableDubbo`, `@Service` and `@Reference`." />
- <!-- 网页标签标题 -->
- <title>Use Annotations In Dubbo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>With the widely promotion and implementation of Microservices Architecture, the Microservices Architecture represented by Spring Boot and Spring Cloud, in Java ecosystem, introduced some brand new programming model, like:</p>
-<ul>
-<li>Annotation-Driven</li>
-<li>External Configuration</li>
-<li>Auto-Configure</li>
-</ul>
-<p>New programming model have some advantages, for example, it does not require <code>XML</code> configuration, it can simplify deployment process, beyond that，it can promote development efficiency. In order to implement the microservice architecture better，Dubbo has provided more perfect support for the above three scenarios since version 2.5.8. This article focuses on introduce annotations rather than discuss the traditional XML configuration approach. There are two kinds of automatic [...]
-<h2>Introduce Annotations</h2>
-<h3>@EnableDubbo</h3>
-<p>The annotations of <code>@EnableDubbo</code> is a combination of both <code>@EnableDubboConfig</code> and <code>@DubboComponentScan</code>.Related to the annotation driver is <code>@DubboComponentScan</code>.</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> org.apache.dubbo.config.spring.context.annotation;
-
-<span class="hljs-meta">@EnableDubboConfig</span>
-<span class="hljs-meta">@DubboComponentScan</span>
-<span class="hljs-keyword">public</span> <span class="hljs-meta">@interface</span> EnableDubbo {
- <span class="hljs-comment">/**
- * Base packages to scan for annotated <span class="hljs-doctag">@Service</span> classes.
- * <p>
- * Use {<span class="hljs-doctag">@link</span> #scanBasePackageClasses()} for a type-safe alternative to String-based
- * package names.
- *
- * <span class="hljs-doctag">@return</span> the base packages to scan
- * <span class="hljs-doctag">@see</span> DubboComponentScan#basePackages()
- */</span>
- <span class="hljs-meta">@AliasFor</span>(annotation = DubboComponentScan.class, attribute = <span class="hljs-string">"basePackages"</span>)
- String[] scanBasePackages() <span class="hljs-keyword">default</span> {};
-
- <span class="hljs-comment">/**
- * Type-safe alternative to {<span class="hljs-doctag">@link</span> #scanBasePackages()} for specifying the packages to
- * scan for annotated <span class="hljs-doctag">@Service</span> classes. The package of each class specified will be
- * scanned.
- *
- * <span class="hljs-doctag">@return</span> classes from the base packages to scan
- * <span class="hljs-doctag">@see</span> DubboComponentScan#basePackageClasses
- */</span>
- <span class="hljs-meta">@AliasFor</span>(annotation = DubboComponentScan.class, attribute = <span class="hljs-string">"basePackageClasses"</span>)
- Class<?>[] scanBasePackageClasses() <span class="hljs-keyword">default</span> {};
-}
-</code></pre>
-<p>The <code>@bableDubbo</code> can be used to scan Dubbo's service provider (marked by <code>@Service</code>) and Dubbo's service consumer (marked by <code>Reference</code>) under the specified package name (via <code>scanBasePackages</code>) or in the specified class (via <code>scanBasePackageClasses</code>). After Dubbo's service providers and consumers have been scanned, they have been assembled corresponding and been initialized, and finally the service is exposed or referenced, if [...]
-<h3>@Service</h3>
-<p><code>@service</code> is used to configure Dubbo's Service provider,for example:</p>
-<pre><code class="language-java"><span class="hljs-meta">@Service</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">AnnotatedGreetingService</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">GreetingService</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hello, "</span> + name;
- }
-}
-</code></pre>
-<p>Via <code>@Service</code>'s properties, you can customize Dubbo's Service provider:</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> org.apache.dubbo.config.annotation;
-
-<span class="hljs-meta">@Documented</span>
-<span class="hljs-meta">@Retention</span>(RetentionPolicy.RUNTIME)
-<span class="hljs-meta">@Target</span>({ElementType.TYPE}) <span class="hljs-comment">// #1</span>
-<span class="hljs-meta">@Inherited</span>
-<span class="hljs-keyword">public</span> <span class="hljs-meta">@interface</span> Service {
- Class<?> interfaceClass() <span class="hljs-keyword">default</span> <span class="hljs-keyword">void</span>.class; <span class="hljs-comment">// #2</span>
- <span class="hljs-function">String <span class="hljs-title">interfaceName</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #3</span>
- <span class="hljs-function">String <span class="hljs-title">version</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #4</span>
- <span class="hljs-function">String <span class="hljs-title">group</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #5</span>
- <span class="hljs-function"><span class="hljs-keyword">boolean</span> <span class="hljs-title">export</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> <span class="hljs-keyword">true</span></span>; <span class="hljs-comment">// #6</span>
- <span class="hljs-function"><span class="hljs-keyword">boolean</span> <span class="hljs-title">register</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> <span class="hljs-keyword">true</span></span>; <span class="hljs-comment">// #7</span>
-
- <span class="hljs-function">String <span class="hljs-title">application</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #8</span>
- <span class="hljs-function">String <span class="hljs-title">module</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #9</span>
- <span class="hljs-function">String <span class="hljs-title">provider</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #10</span>
- String[] protocol() <span class="hljs-keyword">default</span> {}; <span class="hljs-comment">// #11</span>
- <span class="hljs-function">String <span class="hljs-title">monitor</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #12</span>
- String[] registry() <span class="hljs-keyword">default</span> {}; <span class="hljs-comment">// #13</span>
-}
-</code></pre>
-<p>Which is more important:</p>
-<ol>
-<li><strong>@Service</strong>: Can only be defined on a class, represent a service</li>
-<li><strong>interfaceClass</strong>: specified <code>interface</code>'s class implemented by the service provider</li>
-<li><strong>interfaceName</strong>: specified <code>interface</code>'s class name implemented by the service provider</li>
-<li><strong>version</strong>: specified the version number of the service</li>
-<li><strong>group</strong>:specified the group of services</li>
-<li><strong>export</strong>:whether to expose service</li>
-<li><strong>registry</strong>:Whether to register service to the registry</li>
-<li><strong>application</strong>:application configuration</li>
-<li><strong>module</strong>:module configuration</li>
-<li><strong>provider</strong>:service provider configuration</li>
-<li><strong>protocol</strong>:protocol configuration</li>
-<li><strong>monitor</strong>:monitoring center configuration</li>
-<li><strong>registr</strong>:registry configuration</li>
-</ol>
-<p>In addition, it should be noted that, <code>application</code>, <code>module</code>, <code>provider</code>, <code>protocol</code>, <code>monitor</code>, <code>registry</code> (from 8 to 13) need to provide the name of the corresponding <code>spring bean</code>,These bean assembly completed either through traditional XML configuration,or by the modern Java Config. This article will show you how to use <code>Java Config</code>.</p>
-<h3>@Reference</h3>
-<p><code>@Reference</code> is used to configure Dubbo's Service consumer,for example:</p>
-<pre><code class="language-Java"><span class="hljs-meta">@Component</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">GreetingServiceConsumer</span> </span>{
- <span class="hljs-meta">@Reference</span>
- <span class="hljs-keyword">private</span> GreetingService greetingService;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">doSayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> greetingService.sayHello(name);
- }
-}
-</code></pre>
-<p>Via <code>@Reference</code>'s properties, you can customize Dubbo's Service consumer:</p>
-<pre><code class="language-Java"><span class="hljs-keyword">package</span> org.apache.dubbo.config.annotation;
-
-<span class="hljs-meta">@Documented</span>
-<span class="hljs-meta">@Retention</span>(RetentionPolicy.RUNTIME)
-<span class="hljs-meta">@Target</span>({ElementType.FIELD, ElementType.METHOD, ElementType.ANNOTATION_TYPE}) <span class="hljs-comment">// #1</span>
-<span class="hljs-keyword">public</span> <span class="hljs-meta">@interface</span> Reference {
- Class<?> interfaceClass() <span class="hljs-keyword">default</span> <span class="hljs-keyword">void</span>.class; <span class="hljs-comment">// #2</span>
- <span class="hljs-function">String <span class="hljs-title">interfaceName</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #3</span>
- <span class="hljs-function">String <span class="hljs-title">version</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #4</span>
- <span class="hljs-function">String <span class="hljs-title">group</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #5</span>
- <span class="hljs-function">String <span class="hljs-title">url</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #6</span>
-
- <span class="hljs-function">String <span class="hljs-title">application</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #7</span>
- <span class="hljs-function">String <span class="hljs-title">module</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #8</span>
- <span class="hljs-function">String <span class="hljs-title">consumer</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #9</span>
- <span class="hljs-function">String <span class="hljs-title">protocol</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #10</span>
- <span class="hljs-function">String <span class="hljs-title">monitor</span><span class="hljs-params">()</span> <span class="hljs-keyword">default</span> ""</span>; <span class="hljs-comment">// #11</span>
- String[] registry() <span class="hljs-keyword">default</span> {}; <span class="hljs-comment">// #12</span>
-}
-</code></pre>
-<p>Which is more important:</p>
-<ol>
-<li><strong>@Reference</strong>:you can define it on a field in a class, you can define it on a method, you can even modify another annotation, it represent a reference to a service.Normally <code>@Reference</code> is defined in one field</li>
-<li><strong>interfaceClass</strong> : specified <code>interface</code>'s class implemented by the service provider</li>
-<li><strong>interfaceName</strong>: specified <code>interface</code>'s class name implemented by the service provider</li>
-<li><strong>version</strong>: specified the version number of the service</li>
-<li><strong>group</strong>:pecified the group of services</li>
-<li><strong>url</strong>: invoking the registry directly by specifying the URL of the service provider</li>
-<li><strong>application</strong>:application configuration</li>
-<li><strong>module</strong>:module configuration</li>
-<li><strong>consumer</strong>:service consumer configuration</li>
-<li><strong>protocol</strong>:protocol configuration</li>
-<li><strong>monitor</strong>:monitoring center configuration</li>
-<li><strong>registr</strong>:registry configuration</li>
-</ol>
-<p>In addition, it should be noted that, <code>application</code>, <code>module</code>, <code>consumer</code>, <code>protocol</code>, <code>monitor</code>, <code>registry</code> (from 7 to 12) need to provide the name of the corresponding <code>spring bean</code>,These bean assembly completed either through traditional XML configuration,or by the modern Java Config. This article will show you how to use <code>Java Config</code>.</p>
-<h2>Example practice</h2>
-<p>After learn what <code>@EnableDubbo</code>, <code>@Service</code>, <code>@Reference</code> is, there is a practical example showing how to use the annotation to develop a Dubbo application.The following code can be found at <a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-annotation">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-annotation</a></p>
-<h3>1.Interface Definition</h3>
-<p>Define a simple <code>GreetingService</code> interface with only a simple method <code>sayHello</code> to the caller.</p>
-<pre><code class="language-Java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">GreetingService</span> </span>{
- <span class="hljs-function">String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span></span>;
-}
-</code></pre>
-<h3>2.Server:Service Implementation</h3>
-<p>Implement the <code>GreetingService</code> interface, and mark it as a service for Dubbo via @Service.</p>
-<pre><code class="language-Java"><span class="hljs-meta">@Service</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">AnnotatedGreetingService</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">GreetingService</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hello, "</span> + name;
- }
-}
-</code></pre>
-<h3>3.Server:Assembly Service Provider</h3>
-<p>You can discover, assemble, and provide Dubbo's services through the Java config technology (@Configuration) and annotation scan (@EnableDubbo) in Spring.</p>
-<pre><code class="language-Java"><span class="hljs-meta">@Configuration</span>
-<span class="hljs-meta">@EnableDubbo</span>(scanBasePackages = <span class="hljs-string">"com.alibaba.dubbo.samples.impl"</span>)
-<span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ProviderConfiguration</span> </span>{
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #1</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> ProviderConfig <span class="hljs-title">providerConfig</span><span class="hljs-params">()</span> </span>{
- ProviderConfig providerConfig = <span class="hljs-keyword">new</span> ProviderConfig();
- providerConfig.setTimeout(<span class="hljs-number">1000</span>);
- <span class="hljs-keyword">return</span> providerConfig;
- }
-
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #2</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> ApplicationConfig <span class="hljs-title">applicationConfig</span><span class="hljs-params">()</span> </span>{
- ApplicationConfig applicationConfig = <span class="hljs-keyword">new</span> ApplicationConfig();
- applicationConfig.setName(<span class="hljs-string">"dubbo-annotation-provider"</span>);
- <span class="hljs-keyword">return</span> applicationConfig;
- }
-
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #3</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> RegistryConfig <span class="hljs-title">registryConfig</span><span class="hljs-params">()</span> </span>{
- RegistryConfig registryConfig = <span class="hljs-keyword">new</span> RegistryConfig();
- registryConfig.setProtocol(<span class="hljs-string">"zookeeper"</span>);
- registryConfig.setAddress(<span class="hljs-string">"localhost"</span>);
- registryConfig.setPort(<span class="hljs-number">2181</span>);
- <span class="hljs-keyword">return</span> registryConfig;
- }
-
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #4</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> ProtocolConfig <span class="hljs-title">protocolConfig</span><span class="hljs-params">()</span> </span>{
- ProtocolConfig protocolConfig = <span class="hljs-keyword">new</span> ProtocolConfig();
- protocolConfig.setName(<span class="hljs-string">"dubbo"</span>);
- protocolConfig.setPort(<span class="hljs-number">20880</span>);
- <span class="hljs-keyword">return</span> protocolConfig;
- }
-}
-</code></pre>
-<p>Description：</p>
-<ul>
-<li>Scan all classes marked with <code>@Service</code> under <code>com.alibaba.dubbo.samples.impl</code> with <code>@EnableDubbo</code></li>
-<li>Via @Configuration, all @Beans in the ProviderConfiguration are assembled using the way of <code>Java Config</code> and then injected into the Dubbo service, which means the class marked with <code>@Service</code>.Which included:
-i. <strong>ProviderConfig</strong>:Service provider configuration
-ii. <strong>ApplicationConfig</strong>:Application configuration
-iii.<strong>RegistryConfig</strong>:registry configuration
-iv. <strong>ProtocolConfig</strong>:Protocol configuration</li>
-</ul>
-<h3>4.Server:Start Service</h3>
-<p>In the <code>main</code> method to provide external <code>Dubbo</code> service by starting a <code>Spring Context</code>.</p>
-<pre><code class="language-Java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ProviderBootstrap</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> <span class="hljs-keyword">throws</span> Exception </span>{
- <span class="hljs-keyword">new</span> EmbeddedZooKeeper(<span class="hljs-number">2181</span>, <span class="hljs-keyword">false</span>).start(); <span class="hljs-comment">// #1</span>
- AnnotationConfigApplicationContext context = <span class="hljs-keyword">new</span> AnnotationConfigApplicationContext(ProviderConfiguration.class); <span class="hljs-comment">// #2</span>
- context.start(); <span class="hljs-comment">// #3</span>
- System.in.read(); <span class="hljs-comment">// #4</span>
- }
-}
-</code></pre>
-<p>Description：</p>
-<ol>
-<li>Start an embedded <code>zookeeper</code> and provide service registry on port <code>2181</code></li>
-<li>Initialize an example of an AnnotationConfigApplicationContext and pass the <code>ProviderConfiguration</code> into the example to complete the automatic discovery and assembly of the <code>Dubbo</code> service.</li>
-<li>Start the <code>Spring Context</code> and start providing external <code>Dubbo</code> services.</li>
-<li>Because it is a server, you need to prevent the process exit by blocking the main thread.</li>
-</ol>
-<p>Start the <code>main</code> method of the server, you will see the following output, on behalf of the server startup success, and registered the <code>GreetingService</code> service in the <code>ZookeeperRegistry</code>:</p>
-<pre><code class="language-sh">[01/08/18 02:12:51:051 CST] main INFO transport.AbstractServer: [DUBBO] Start NettyServer <span class="hljs-built_in">bind</span> /0.0.0.0:20880, <span class="hljs-built_in">export</span> /192.168.99.1:20880, dubbo version: 2.6.2, current host: 192.168.99.1
-
-[01/08/18 02:12:51:051 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=<span class="hljs-literal">true</span>&application=dubbo-annotation-provider&default.timeout=1000&dubbo=2.6.2&generic=<span class="hljs-literal">false</span>&interface=com.alibaba.dubbo.samples.api
-</code></pre>
-<h3>5.Server:Reference Service</h3>
-<p>Marking the member variable of the <code>GreetingService</code> via <code>@Reference</code> .The <code>greetingService</code> is a reference to the <code>Dubbo</code> service, which means that it can simply provide through the interface to the remote party to initiate service calls, and the client does not implement <code>GreetingService</code> interface.</p>
-<pre><code class="language-Java"><span class="hljs-meta">@Component</span>(<span class="hljs-string">"annotatedConsumer"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">GreetingServiceConsumer</span> </span>{
- <span class="hljs-meta">@Reference</span>
- <span class="hljs-keyword">private</span> GreetingService greetingService;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">doSayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> greetingService.sayHello(name);
- }
-}
-</code></pre>
-<h3>6.Server:Assembly Service consumer</h3>
-<p>Just like <strong>3. Server:Assembly Service Provider</strong> You can discover, assemble, and provide Dubbo's service consumer through the Java config technology (@Configuration) and annotation scan (@EnableDubbo) in Spring.</p>
-<pre><code class="language-Java"><span class="hljs-meta">@Configuration</span>
-<span class="hljs-meta">@EnableDubbo</span>(scanBasePackages = <span class="hljs-string">"com.alibaba.dubbo.samples.action"</span>)
-<span class="hljs-meta">@ComponentScan</span>(value = {<span class="hljs-string">"com.alibaba.dubbo.samples.action"</span>})
-<span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ConsumerConfiguration</span> </span>{
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #1</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> ApplicationConfig <span class="hljs-title">applicationConfig</span><span class="hljs-params">()</span> </span>{
- ApplicationConfig applicationConfig = <span class="hljs-keyword">new</span> ApplicationConfig();
- applicationConfig.setName(<span class="hljs-string">"dubbo-annotation-consumer"</span>);
- <span class="hljs-keyword">return</span> applicationConfig;
- }
-
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #2</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> ConsumerConfig <span class="hljs-title">consumerConfig</span><span class="hljs-params">()</span> </span>{
- ConsumerConfig consumerConfig = <span class="hljs-keyword">new</span> ConsumerConfig();
- consumerConfig.setTimeout(<span class="hljs-number">3000</span>);
- <span class="hljs-keyword">return</span> consumerConfig;
- }
-
- <span class="hljs-meta">@Bean</span> <span class="hljs-comment">// #3</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> RegistryConfig <span class="hljs-title">registryConfig</span><span class="hljs-params">()</span> </span>{
- RegistryConfig registryConfig = <span class="hljs-keyword">new</span> RegistryConfig();
- registryConfig.setProtocol(<span class="hljs-string">"zookeeper"</span>);
- registryConfig.setAddress(<span class="hljs-string">"localhost"</span>);
- registryConfig.setPort(<span class="hljs-number">2181</span>);
- <span class="hljs-keyword">return</span> registryConfig;
- }
-}
-</code></pre>
-<p>Description：</p>
-<ul>
-<li>Scan all classes marked with <code>@Service</code> under <code>com.alibaba.dubbo.samples.impl</code> with <code>@Reference</code></li>
-<li>Via @Configuration, all @Beans in the ProviderConfiguration are assembled using the way of <code>Java Config</code> and then injected into the Dubbo service, which means the class marked with <code>@Reference</code>.Which included:
-i. <code>ApplicationConfig</code>: Application configuration
-ii. <code>ConsumerConfig</code>:Service consumer configuration
-iii.<code>RegistryConfig</code>:Registry configuration.Note:The configuration here needs to be consistent with the configuration information of the EmbeddedZooKeeper when started by the service provider.</li>
-</ul>
-<h3>7.Server: Initiate Remote Calls</h3>
-<p>In the <code>main</code> method, you can start a <code>Spring Context</code> to find the service consumer of the assembled <code>Dubbo</code> from it, and initiate a remote call.</p>
-<pre><code class="language-Java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ConsumerBootstrap</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- AnnotationConfigApplicationContext context = <span class="hljs-keyword">new</span> AnnotationConfigApplicationContext(ConsumerConfiguration.class); <span class="hljs-comment">// #1</span>
- context.start(); <span class="hljs-comment">// #2</span>
- GreetingServiceConsumer greetingServiceConsumer = context.getBean(GreetingServiceConsumer.class); <span class="hljs-comment">// #3</span>
- String hello = greetingServiceConsumer.doSayHello(<span class="hljs-string">"annotation"</span>); <span class="hljs-comment">// #4</span>
- System.out.println(<span class="hljs-string">"result: "</span> + hello); <span class="hljs-comment">// #5</span>
- }
-}
-</code></pre>
-<p>Description：</p>
-<ul>
-<li>Initialize an example of an AnnotationConfigApplicationContext and pass the <code>ProviderConfiguration</code> into the example to complete the automatic discovery and assembly of the <code>Dubbo</code> service consumer.</li>
-<li>start <code>Spring Context</code>.</li>
-<li>Find <code>bean</code> which type is <code>GreetingServiceConsumer</code> from <code>Context</code>.</li>
-<li>Call the <code>doSayHello</code> method and finally initiate a remote call via Dubbo's service reference (marked by @Reference)</li>
-<li>Print call result
-Start the Server's <code>main</code> method, you will see the following output, which returns the <code>result</code>: hello, annotation:</li>
-</ul>
-<pre><code class="language-sh">[01/08/18 02:38:40:040 CST] main INFO config.AbstractConfig: [DUBBO] Refer dubbo service com.alibaba.dubbo.samples.api.GreetingService from url zookeeper://localhost:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=<span class="hljs-literal">true</span>&application=dubbo-annotation-consumer&check=<span class="hljs-literal">false</span>&default.timeout=3000&dubbo=2.6.2&generic=<span class="hljs-literal">false</span>&interface [...]
-[01/08/18 02:38:40:040 CST] main INFO annotation.ReferenceBeanBuilder: <dubbo:reference object=<span class="hljs-string">"com.alibaba.dubbo.common.bytecode.proxy0@673be18f"</span> singleton=<span class="hljs-string">"true"</span> interface=<span class="hljs-string">"com.alibaba.dubbo.samples.api.GreetingService"</span> uniqueServiceName=<span class="hljs-string">"com.alibaba.dubbo.samples.api.GreetingService"</span> generic=<span class="hljs-string">"false"</span> id=<span class="hlj [...]
-result: hello, annotation
-</code></pre>
-<h2>Conclusion</h2>
-<p>By studying this article, the reader can master the basic concepts of <code>Dubbo</code>'s exclusive <code>annotations</code> , <code>@EnableDubbo</code>, <code>@Service</code>, <code>@Reference</code>, and master it's basic usage through a simple <code>Dubbo</code> application.</p>
-<p>In addition to traditional <code>XML</code> configuration, <code>Spring</code> offers more modern configurations such as annotation drivers, externalization, and auto-assembly.This article focuses on the development of <code>Dubbo</code> applications through annotations. You can be seen that annotation mode programming is more concise and simple than XML configuration. In future, we will introduce the use of externalization configuration and automatic assembly in <code>Dubbo</code> f [...]
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-annotation.json b/en-us/blog/dubbo-annotation.json
deleted file mode 100644
index ce139f7..0000000
--- a/en-us/blog/dubbo-annotation.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-annotation.md",
- "__html": "<h1>Use Annotations In Dubbo</h1>\n<p>With the widely promotion and implementation of Microservices Architecture, the Microservices Architecture represented by Spring Boot and Spring Cloud, in Java ecosystem, introduced some brand new programming model, like:</p>\n<ul>\n<li>Annotation-Driven</li>\n<li>External Configuration</li>\n<li>Auto-Configure</li>\n</ul>\n<p>New programming model have some advantages, for example, it does not require <code>XML</code> configuration, it [...]
- "link": "/en-us/blog/dubbo-annotation.html",
- "meta": {
- "title": "Use Annotations In Dubbo",
- "keywords": "Dubbo, Annotation, Spring",
- "description": "This article will introduce you how to use annotations instead of XML to develop Dubbo applications, such as `@EnableDubbo`, `@Service` and `@Reference`."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.html b/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.html
deleted file mode 100644
index 97939b5..0000000
--- a/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.html
+++ /dev/null
@@ -1,405 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Provider, Configuration" />
- <meta name="description" content="This article will introduce you how to config Dubbo, by XML, property files, annotations or Java code." />
- <!-- 网页标签标题 -->
- <title>Dubbo Basic Usage -- Dubbo Provider Configuration</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h1>Dubbo Basic Usage</h1>
-<p>This chapter mainly talking about how to configure dubbo. According to the configuration mode, it can be divided into the following mode: XML Configuration, Properties Configuration, Annotation Configuration, API Invocation Mode Configuration. And according to the function, we can divide them into Dubbo Provider and Dubbo Consumer. In the following sections, we would explain Dubbo Provider and Dubbo Consumer respectively.</p>
-<h2>Dubbo Provider Configuration</h2>
-<h3>Provider Configuration in Detail</h3>
-<p>The configuration mode of Dubbo Provider has 4 different ways: XML Configuration, Properties Configuration, API Invocation Mode Configuration and Annotation Configuration.</p>
-<h4>XML Configuration</h4>
-<h6>The simplest configuration example：</h6>
-<pre><code><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <dubbo:service interface="com.alibaba.dubbo.demo.DemoService" ref="demoServiceLocal" />
- <dubbo:reference id="demoServiceRemote" interface="com.alibaba.dubbo.demo.DemoService" />
-</beans>
-</code></pre>
-<p>In the example above，note the way to write dubbo schema：</p>
-<pre><code><beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
- xmlns="http://www.springframework.org/schema/beans"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
- http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">
-</code></pre>
-<h6>Supported Configuration Tags</h6>
-<table>
-<thead>
-<tr>
-<th>Tags</th>
-<th>Application</th>
-<th style="text-align:left">Describe</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><dubbo:service/></td>
-<td>Service Configuration</td>
-<td style="text-align:left">Expose a service, define the meta information of the service. One service can use multiple protocols to expose and can be registered to multiple registry centers</td>
-</tr>
-<tr>
-<td><dubbo:reference/></td>
-<td>Reference Configuration</td>
-<td style="text-align:left">Create a remote service agent, one reference can point to multiple registry centers</td>
-</tr>
-<tr>
-<td><dubbo:protocol/></td>
-<td>Protocol Configuration</td>
-<td style="text-align:left">Configure protocol information for providing services, protocol is specified by the provider and accepted passively by the consumer</td>
-</tr>
-<tr>
-<td><dubbo:application/></td>
-<td>Application Configuration</td>
-<td style="text-align:left">Configure current application information, regardless of whether the application is provider or consumer</td>
-</tr>
-<tr>
-<td><dubbo:module/></td>
-<td>Module Configuration</td>
-<td style="text-align:left">Configure current module information. Optional</td>
-</tr>
-<tr>
-<td><dubbo:registry/></td>
-<td>Registry Center Configuration</td>
-<td style="text-align:left">Configure information related to connect registry centers</td>
-</tr>
-<tr>
-<td><dubbo:monitor/></td>
-<td>Monitoring Center Configuration</td>
-<td style="text-align:left">Configure information related to connect monitor centers. Optional</td>
-</tr>
-<tr>
-<td><dubbo:provider/></td>
-<td>Provider Configuration</td>
-<td style="text-align:left">When some properties ProtocolConfig or ServiceConfig are not configured, use this default value. Optional</td>
-</tr>
-<tr>
-<td><dubbo:consumer/></td>
-<td>Consumer Configuration</td>
-<td style="text-align:left">When some properties of ReferenceConfig are not configured, use this default value. Optional</td>
-</tr>
-<tr>
-<td><dubbo:method/></td>
-<td>Method Configuration</td>
-<td style="text-align:left">Configure specific method level information of ServiceConfig and ReferenceConfig</td>
-</tr>
-<tr>
-<td><dubbo:argument/></td>
-<td>Parameter Configuration</td>
-<td style="text-align:left">Configure parameters of specific method</td>
-</tr>
-</tbody>
-</table>
-<p><img src="https://cdn.yuque.com/lark/0/2018/png/15841/1527849348155-8423d401-9ea4-4dc6-8720-d9e3d90963b6.png" alt="undefined"></p>
- <center>Configuration Diagram</center>
-<h6>Configuration item in detail</h6>
-<ul>
-<li>
-<p><dubbo:application name="hello-world-app" /><br>
-Apply to specific application name, note that you need to make sure that the application name is unique. The application name can be displayed in the following console admin for easy management.</p>
-</li>
-<li>
-<p><dubbo:registry address="multicast://224.5.6.7:1234" /><br>
-Configure registry center, related to the specific mechanism of service discovery. It can be zookeeper address or eureka address. The address above is the broadcast address, which is very convenient in the test process of the local service invocation.</p>
-</li>
-<li>
-<p><dubbo:protocol name="dubbo" port="20880" /><br>
-Here is the transport protocol and the default port, generally no changes are required.</p>
-</li>
-</ul>
-<blockquote>
-<p>Next, we will focus on the configuration of <dubbo:service/></p>
-</blockquote>
-<ul>
-<li><dubbo:service/>mainly supports the following properties：</li>
-</ul>
-<table>
-<thead>
-<tr>
-<th>Properties Name</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>version</td>
-<td>Version number</td>
-</tr>
-<tr>
-<td>scope</td>
-<td>Service visibility, value can be local or remote，remote by default</td>
-</tr>
-<tr>
-<td>actives</td>
-<td>Maximum number of activated requests</td>
-</tr>
-<tr>
-<td>async</td>
-<td>Whether the method called asynchronously，false by default</td>
-</tr>
-<tr>
-<td>cache</td>
-<td>Service cache，optional value：lru/threadlocal/jcache</td>
-</tr>
-<tr>
-<td>callbacks</td>
-<td>Limitation of callback instance</td>
-</tr>
-<tr>
-<td>generic</td>
-<td>Generalized calls which can be bypassed</td>
-</tr>
-<tr>
-<td>class</td>
-<td>The implementation of the service's class name</td>
-</tr>
-<tr>
-<td>connections</td>
-<td>The number of connections in the service</td>
-</tr>
-<tr>
-<td>delay</td>
-<td>The number of milliseconds delay for publicating the service</td>
-</tr>
-<tr>
-<td>executes</td>
-<td>Upper bound of service execution requests</td>
-</tr>
-<tr>
-<td>retries</td>
-<td>Timeout retry times</td>
-</tr>
-<tr>
-<td>timeout</td>
-<td>Invocation timeout time</td>
-</tr>
-</tbody>
-</table>
-<p>For other configuration properties, please refer to xsd：<a href="http://dubbo.apache.org/schema/dubbo/dubbo.xsd">http://dubbo.apache.org/schema/dubbo/dubbo.xsd</a></p>
-<ul>
-<li><dubbo:method/> as the sub-element of <dubbo:service/> can be configured corresponding to method. Properties that are commonly used are：</li>
-</ul>
-<table>
-<thead>
-<tr>
-<th>Properties Name</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>executes</td>
-<td>Upper bound of service execution requests</td>
-</tr>
-<tr>
-<td>retries</td>
-<td>Timeout retry times</td>
-</tr>
-<tr>
-<td>timeout</td>
-<td>Invocation timeout time</td>
-</tr>
-</tbody>
-</table>
-<p>For other properties，you can refer to xsd above。</p>
-<h6>Configuration Override Relationship</h6>
-<p><img src="https://cdn.yuque.com/lark/0/2018/png/15841/1527849374313-94a5ea24-0e72-4d83-871b-e0e95eab646a.png" alt="undefined"></p>
-<center>Configuration Coverage Relationship Diagram</center>
-<p>The Override relationship here includes the configuration of both provider end and consumer end. If you have any questions about consumer, you can refer to the next chapter, consumer chapter, to understand.</p>
-<h4>dubbo.properties Configuration</h4>
-<blockquote>
-<p>If the public configuration is very simple, no multiple registry centers, no multiple protocols, etc., or if you want multiple Spring containers to share the configuration, you can use dubbo.properties as the default configurations.</p>
-</blockquote>
-<p>Dubbo would load dubbo.properties under the classpath root directory automaticaly，you can change the default configuration location by JVM startup parameter -Ddubbo.properties.file=xxx.properties.</p>
-<h6>dubbo.properties Configuration example</h6>
-<pre><code># application name
-dubbo.application.name=dubbodemo-provider
-# registry center address
-dubbo.registry.address=zookeeper://localhost:2181
-# Example of broadcasting registry center
-#dubbo.registry.address=multicast://224.5.6.7:1234
-# address for calling protocol
-dubbo.protocol.name=dubbo
-dubbo.protocol.port=28080
-</code></pre>
-<h6>Mapping Rule</h6>
-<p>Split the tag name and properties in XML configuration with dots, and multiple properties should be split into multiple lines</p>
-<ul>
-<li>For example: dubbo.application.name=foo equivalents to <dubbo:application name="foo" /></li>
-<li>For example: dubbo.registry.address=10.20.153.10:9090 equivalents to <dubbo:registry address="10.20.153.10:9090" /></li>
-</ul>
-<p>If there are multiple configurations having the same tag name, they can be distinguished by id, and if there is no id, the configurations will be applied to all tags with the same name.</p>
-<ul>
-<li>For example: dubbo.protocol.rmi.port=1234 equivalents to <dubbo:protocol id="rmi" name="rmi" port="1234" /></li>
-<li>For example: dubbo.registry.china.address=10.20.153.10:9090 equivalents to <dubbo:registry id="china" address="10.20.153.10:9090" /></li>
-</ul>
-<h6>Coverage Strategy</h6>
-<p><img src="https://cdn.yuque.com/lark/0/2018/png/15841/1527849393591-2c3de248-1b3d-47d3-bd10-8b415e9fcd39.png" alt="undefined"></p>
-<ul>
-<li>When JVM starts, -D parameter has priority, so that users can rewrite the parameters when deploy and start, for example, the protocol port should be changed when start.</li>
-<li>Then comes to XML, the configurations in dubbo.properties are invalid, if they are configured in XML.</li>
-<li>Properties are the last, which can be considered as default value. Only when there is no configuration in XML, the corresponding configuarations in dubbo.properties will become effective, which usually applies to shared public configuration, like application name.</li>
-</ul>
-<blockquote>
-<p>Note:</p>
-</blockquote>
-<ol>
-<li>If there are multiple dubbo.properties in the classpath root directory, for example, if dubbo.properties exist in multiple JAR files, Dubbo will load anyone arbitrarily and print the Error logs, which may change to throwing exceptions later.↩</li>
-<li>When the protocol's id is not configured, protocol name will be used as id as default.</li>
-</ol>
-<h4>Annotation</h4>
-<h6>Service Annotation Exposure Service</h6>
-<pre><code>import com.alibaba.dubbo.config.annotation.Service;
-
-@Service(timeout = 5000)
-public class AnnotateServiceImpl implements AnnotateService {
- // ...
-}
-</code></pre>
-<h6>Javaconfig Configuration Public Module</h6>
-<pre><code>@Configuration
-public class DubboConfiguration {
-
- @Bean
- public ApplicationConfig applicationConfig() {
- ApplicationConfig applicationConfig = new ApplicationConfig();
- applicationConfig.setName("provider-test");
- return applicationConfig;
- }
-
- @Bean
- public RegistryConfig registryConfig() {
- RegistryConfig registryConfig = new RegistryConfig();
- registryConfig.setAddress("zookeeper://127.0.0.1:2181");
- registryConfig.setClient("curator");
- return registryConfig;
- }
-}
-</code></pre>
-<p>The result of configuration using this method is the same as that of using xml.</p>
-<h6>Specify the Dubbo Scan Path</h6>
-<pre><code>@SpringBootApplication
-@DubboComponentScan(basePackages = "com.alibaba.dubbo.test.service.impl")
-public class ProviderTestApp {
- // ...
-}
-</code></pre>
-<p>or use the spring bean xml configuration:</p>
-<pre><code><dubbo:annotation package="com.chanshuyi.service.impl" />
-</code></pre>
-<h4>API Trigger Directly</h4>
-<pre><code>import com.alibaba.dubbo.rpc.config.ApplicationConfig;
-import com.alibaba.dubbo.rpc.config.RegistryConfig;
-import com.alibaba.dubbo.rpc.config.ProviderConfig;
-import com.alibaba.dubbo.rpc.config.ServiceConfig;
-import com.xxx.XxxService;
-import com.xxx.XxxServiceImpl;
-
-// Service implementation
-XxxService xxxService = new XxxServiceImpl();
-
-// current application configuration
-ApplicationConfig application = new ApplicationConfig();
-application.setName("xxx");
-
-// connect to registry center configuration
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("10.20.130.230:9090");
-registry.setUsername("aaa");
-registry.setPassword("bbb");
-
-// service provider's protocol configuration
-ProtocolConfig protocol = new ProtocolConfig();
-protocol.setName("dubbo");
-protocol.setPort(12345);
-protocol.setThreads(200);
-
-// Note: ServiceConfig is a heavy object, which encapsulated the connection with registry center internally, and open the service port
-
-// Service provider exposes service configuration
-ServiceConfig<XxxService> service = new ServiceConfig<XxxService>(); // This instance is very heavy, which encapsulated the connection with registry center, please cache it by yourself, it might cause memory and connection leakage otherwise.
-service.setApplication(application);
-service.setRegistry(registry); // multiple registry centers can use setRegistries()
-service.setProtocol(protocol); // multiple protocols can use setProtocols()
-service.setInterface(XxxService.class);
-service.setRef(xxxService);
-service.setVersion("1.0.0");
-
-// exposure and register service
-service.export();
-</code></pre>
-<p>Generally, this method is not recommended in spring applications. The reason can be checked by reading the source code on github, which would not be explained here.</p>
-<h3>Provider Interface and Implement</h3>
-<p>The above chapters are described mainly from a configuration perspective, and lets explain the complete use of Dubbo provider by going through a complete example.</p>
-<p>There is only one service UserReadService, and one method getUserById in this example.
-This service need to be exposed to a remote service by Dubbo. Detail steps are shown below:</p>
-<ol>
-<li>Create Project
-Skip this step if there is already a project. Create a Spring Boot project, which can be created through <a href="https://start.spring.io/">https://start.spring.io/</a>.</li>
-<li>Define Interface
-Define interface: UserReadService</li>
-</ol>
-<pre><code>public interface UserReadService{
- public User getUserById(Long userId);
-}
-</code></pre>
-<p>Generally, this interface should be placed in an independent JAR file as a client package.
-Generally, the other services need to refer this client package if they want to consume this service(except for generalized call).
-3. Implement Interface
-Implement UserReadService, and deploy current implementation in the Provider's application.</p>
-<pre><code>public UserReadServiceImpl implements UserReadService{
- public User getUserById(Long userId){
- return xxx;
- }
-}
-</code></pre>
-<ol start="4">
-<li>Dubbo Configuration</li>
-</ol>
-<pre><code><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <bean id="userReadService" class="com.package.UserReadServiceImpl"/>
- <dubbo:service interface="com.package.UserReadService" ref="userReadService" />
-</beans>
-</code></pre>
-<p>For the other modes of Dubbo configuration, please refer to the related configurations in the previous chapter, or use the integrated Dubbo Spring Boot starter method.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.json b/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.json
deleted file mode 100644
index fe75644..0000000
--- a/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-basic-usage-dubbo-provider-configuration.md",
- "__html": "<h2>Dubbo Basic Usage -- Dubbo Provider Configuration</h2>\n<h1>Dubbo Basic Usage</h1>\n<p>This chapter mainly talking about how to configure dubbo. According to the configuration mode, it can be divided into the following mode: XML Configuration, Properties Configuration, Annotation Configuration, API Invocation Mode Configuration. And according to the function, we can divide them into Dubbo Provider and Dubbo Consumer. In the following sections, we would explain Dubbo Prov [...]
- "link": "/en-us/blog/dubbo-basic-usage-dubbo-provider-configuration.html",
- "meta": {
- "title": "Dubbo Basic Usage -- Dubbo Provider Configuration",
- "keywords": "Dubbo, Provider, Configuration",
- "description": "This article will introduce you how to config Dubbo, by XML, property files, annotations or Java code."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-fescar.html b/en-us/blog/dubbo-fescar.html
deleted file mode 100644
index 22e68f0..0000000
--- a/en-us/blog/dubbo-fescar.html
+++ /dev/null
@@ -1,215 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo,Fescar,Consistency" />
- <meta name="description" content="This article will introduce you how to use Fescar to ensure consistency between Dubbo Microservices." />
- <!-- 网页标签标题 -->
- <title>How to use Fescar to ensure consistency between Dubbo Microservices</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Use case</h2>
-<p>A business logic for user purchasing commodities. The whole business logic is powered by 3 microservices:</p>
-<ul>
-<li>Storage service: deduct storage count on given commodity.</li>
-<li>Order service: create order according to purchase request.</li>
-<li>Account service: debit the balance of user's account.</li>
-</ul>
-<h3>Architecture</h3>
-<p><img src="../../img/blog/fescar/fescar-1.png" alt="Architecture"></p>
-<h3>StorageService</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">StorageService</span> </span>{
-
- <span class="hljs-comment">/**
- * deduct storage count
- */</span>
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">deduct</span><span class="hljs-params">(String commodityCode, <span class="hljs-keyword">int</span> count)</span></span>;
-}
-</code></pre>
-<h3>OrderService</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">OrderService</span> </span>{
-
- <span class="hljs-comment">/**
- * create order
- */</span>
- <span class="hljs-function">Order <span class="hljs-title">create</span><span class="hljs-params">(String userId, String commodityCode, <span class="hljs-keyword">int</span> orderCount)</span></span>;
-}
-</code></pre>
-<h3>AccountService</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">AccountService</span> </span>{
-
- <span class="hljs-comment">/**
- * debit balance of user's account
- */</span>
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">debit</span><span class="hljs-params">(String userId, <span class="hljs-keyword">int</span> money)</span></span>;
-}
-</code></pre>
-<h3>Main business logic</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">BusinessServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">BusinessService</span> </span>{
-
- <span class="hljs-keyword">private</span> StorageService storageService;
-
- <span class="hljs-keyword">private</span> OrderService orderService;
-
- <span class="hljs-comment">/**
- * purchase
- */</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">purchase</span><span class="hljs-params">(String userId, String commodityCode, <span class="hljs-keyword">int</span> orderCount)</span> </span>{
-
- storageService.deduct(commodityCode, orderCount);
-
- orderService.create(userId, commodityCode, orderCount);
- }
-}
-</code></pre>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">StorageServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">StorageService</span> </span>{
-
- <span class="hljs-keyword">private</span> StorageDAO storageDAO;
-
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">deduct</span><span class="hljs-params">(String commodityCode, <span class="hljs-keyword">int</span> count)</span> </span>{
- Storage storage = <span class="hljs-keyword">new</span> Storage();
- storage.setCount(count);
- storage.setCommodityCode(commodityCode);
- storageDAO.update(storage);
- }
-}
-</code></pre>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">OrderServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">OrderService</span> </span>{
-
- <span class="hljs-keyword">private</span> OrderDAO orderDAO;
-
- <span class="hljs-keyword">private</span> AccountService accountService;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> Order <span class="hljs-title">create</span><span class="hljs-params">(String userId, String commodityCode, <span class="hljs-keyword">int</span> orderCount)</span> </span>{
-
- <span class="hljs-keyword">int</span> orderMoney = calculate(commodityCode, orderCount);
-
- accountService.debit(userId, orderMoney);
-
- Order order = <span class="hljs-keyword">new</span> Order();
- order.userId = userId;
- order.commodityCode = commodityCode;
- order.count = orderCount;
- order.money = orderMoney;
-
- <span class="hljs-keyword">return</span> orderDAO.insert(order);
- }
-}
-</code></pre>
-<h2>Distributed Transaction Solution with Fescar</h2>
-<p><img src="../../img/blog/fescar/fescar-2.png" alt="undefined"></p>
-<p>We just need an annotation <code>@GlobalTransactional</code> on business method:</p>
-<pre><code class="language-java">
- <span class="hljs-meta">@GlobalTransactional</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">purchase</span><span class="hljs-params">(String userId, String commodityCode, <span class="hljs-keyword">int</span> orderCount)</span> </span>{
- ......
- }
-</code></pre>
-<h2>Example powered by Dubbo + Fescar</h2>
-<h3>Step 1: Setup database</h3>
-<ul>
-<li>Requirement: MySQL with InnoDB engine.</li>
-</ul>
-<p><strong>Note:</strong> In fact, there should be 3 database for the 3 services in the example use case. However, we can just create one database and configure 3 data sources for simple.</p>
-<p>Modify Spring XML with the database URL/username/password you just created.</p>
-<p>dubbo-account-service.xml
-dubbo-order-service.xml
-dubbo-storage-service.xml</p>
-<pre><code class="language-xml"> <span class="hljs-tag"><<span class="hljs-name">property</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"url"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"jdbc:mysql://x.x.x.x:3306/xxx"</span> /></span>
- <span class="hljs-tag"><<span class="hljs-name">property</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"username"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"xxx"</span> /></span>
- <span class="hljs-tag"><<span class="hljs-name">property</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"password"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"xxx"</span> /></span>
-</code></pre>
-<h3>Step 2: Create undo_log table for Fescar</h3>
-<p><code>UNDO_LOG</code> table is required by Fescar AT mode.</p>
-<pre><code class="language-sql"><span class="hljs-comment">-- Note that when Fescar version is upgraded to 0.3.0+, it is changed from the previous normal index to the unique index.</span>
-<span class="hljs-keyword">CREATE</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-string">`undo_log`</span> (
- <span class="hljs-string">`id`</span> <span class="hljs-built_in">bigint</span>(<span class="hljs-number">20</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span> AUTO_INCREMENT,
- <span class="hljs-string">`branch_id`</span> <span class="hljs-built_in">bigint</span>(<span class="hljs-number">20</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`xid`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">100</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`rollback_info`</span> longblob <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`log_status`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`log_created`</span> datetime <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`log_modified`</span> datetime <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`ext`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">100</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-literal">NULL</span>,
- PRIMARY <span class="hljs-keyword">KEY</span> (<span class="hljs-string">`id`</span>),
- <span class="hljs-keyword">UNIQUE</span> <span class="hljs-keyword">KEY</span> <span class="hljs-string">`ux_undo_log`</span> (<span class="hljs-string">`xid`</span>,<span class="hljs-string">`branch_id`</span>)
-) <span class="hljs-keyword">ENGINE</span>=<span class="hljs-keyword">InnoDB</span> AUTO_INCREMENT=<span class="hljs-number">1</span> <span class="hljs-keyword">DEFAULT</span> <span class="hljs-keyword">CHARSET</span>=utf8;
-</code></pre>
-<h3>Step 3: Create tables for example business</h3>
-<pre><code class="language-sql">
-<span class="hljs-keyword">DROP</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-keyword">IF</span> <span class="hljs-keyword">EXISTS</span> <span class="hljs-string">`storage_tbl`</span>;
-<span class="hljs-keyword">CREATE</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-string">`storage_tbl`</span> (
- <span class="hljs-string">`id`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span> AUTO_INCREMENT,
- <span class="hljs-string">`commodity_code`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">255</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`count`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-number">0</span>,
- PRIMARY <span class="hljs-keyword">KEY</span> (<span class="hljs-string">`id`</span>),
- <span class="hljs-keyword">UNIQUE</span> <span class="hljs-keyword">KEY</span> (<span class="hljs-string">`commodity_code`</span>)
-) <span class="hljs-keyword">ENGINE</span>=<span class="hljs-keyword">InnoDB</span> <span class="hljs-keyword">DEFAULT</span> <span class="hljs-keyword">CHARSET</span>=utf8;
-
-
-<span class="hljs-keyword">DROP</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-keyword">IF</span> <span class="hljs-keyword">EXISTS</span> <span class="hljs-string">`order_tbl`</span>;
-<span class="hljs-keyword">CREATE</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-string">`order_tbl`</span> (
- <span class="hljs-string">`id`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span> AUTO_INCREMENT,
- <span class="hljs-string">`user_id`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">255</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`commodity_code`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">255</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`count`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-number">0</span>,
- <span class="hljs-string">`money`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-number">0</span>,
- PRIMARY <span class="hljs-keyword">KEY</span> (<span class="hljs-string">`id`</span>)
-) <span class="hljs-keyword">ENGINE</span>=<span class="hljs-keyword">InnoDB</span> <span class="hljs-keyword">DEFAULT</span> <span class="hljs-keyword">CHARSET</span>=utf8;
-
-
-<span class="hljs-keyword">DROP</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-keyword">IF</span> <span class="hljs-keyword">EXISTS</span> <span class="hljs-string">`account_tbl`</span>;
-<span class="hljs-keyword">CREATE</span> <span class="hljs-keyword">TABLE</span> <span class="hljs-string">`account_tbl`</span> (
- <span class="hljs-string">`id`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">NOT</span> <span class="hljs-literal">NULL</span> AUTO_INCREMENT,
- <span class="hljs-string">`user_id`</span> <span class="hljs-built_in">varchar</span>(<span class="hljs-number">255</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-literal">NULL</span>,
- <span class="hljs-string">`money`</span> <span class="hljs-built_in">int</span>(<span class="hljs-number">11</span>) <span class="hljs-keyword">DEFAULT</span> <span class="hljs-number">0</span>,
- PRIMARY <span class="hljs-keyword">KEY</span> (<span class="hljs-string">`id`</span>)
-) <span class="hljs-keyword">ENGINE</span>=<span class="hljs-keyword">InnoDB</span> <span class="hljs-keyword">DEFAULT</span> <span class="hljs-keyword">CHARSET</span>=utf8;
-</code></pre>
-<h3>Step 4: Start Fescar-Server</h3>
-<ul>
-<li>Download server <a href="https://github.com/alibaba/fescar/releases">package</a>, unzip it.</li>
-<li>Start Fescar-Server</li>
-</ul>
-<pre><code class="language-shell">sh fescar-server.sh $LISTEN_PORT $PATH_FOR_PERSISTENT_DATA
-
-e.g.
-
-sh fescar-server.sh 8091 /home/admin/fescar/data/
-</code></pre>
-<h3>Step 5: Run example</h3>
-<ul>
-<li>Start AccountService (<a href="https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboAccountServiceStarter.java">DubboAccountServiceStarter</a>).</li>
-<li>Start StorageService (<a href="https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboStorageServiceStarter.java">DubboStorageServiceStarter</a>).</li>
-<li>Start OrderService (<a href="https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboOrderServiceStarter.java">DubboOrderServiceStarter</a>).</li>
-<li>Run BusinessService for test (<a href="https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboBusinessTester.java">DubboBusinessTester</a>).</li>
-</ul>
-<h3>Related projects</h3>
-<ul>
-<li>fescar: <a href="https://github.com/alibaba/fescar/">https://github.com/alibaba/fescar/</a></li>
-<li>fescar-samples : <a href="https://github.com/fescar-group/fescar-samples">https://github.com/fescar-group/fescar-samples</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-fescar.json b/en-us/blog/dubbo-fescar.json
deleted file mode 100644
index cc8023a..0000000
--- a/en-us/blog/dubbo-fescar.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-fescar.md",
- "__html": "<h1>How to use Fescar to ensure consistency between Dubbo Microservices</h1>\n<h2>Use case</h2>\n<p>A business logic for user purchasing commodities. The whole business logic is powered by 3 microservices:</p>\n<ul>\n<li>Storage service: deduct storage count on given commodity.</li>\n<li>Order service: create order according to purchase request.</li>\n<li>Account service: debit the balance of user's account.</li>\n</ul>\n<h3>Architecture</h3>\n<p><img src=\"../../img/blog/fe [...]
- "link": "/en-us/blog/dubbo-fescar.html",
- "meta": {
- "title": "How to use Fescar to ensure consistency between Dubbo Microservices",
- "keywords": "Dubbo,Fescar,Consistency",
- "description": "This article will introduce you how to use Fescar to ensure consistency between Dubbo Microservices."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-generic-invoke.html b/en-us/blog/dubbo-generic-invoke.html
deleted file mode 100644
index b04490a..0000000
--- a/en-us/blog/dubbo-generic-invoke.html
+++ /dev/null
@@ -1,175 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Generic invoke" />
- <meta name="description" content="This article introduces you when and how to use generic invoke of Dubbo." />
- <!-- 网页标签标题 -->
- <title>Generic invoke of Dubbo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The generic invoke could be considered to be used in the following cases:</p>
-<ul>
-<li>Service test platform</li>
-<li>API service gateway</li>
-</ul>
-<p>The generic invoke is mainly used when the consumer does not have an API interface;
-instead of depending the interface jar package, the service call is initiated directly through the GenericService interface, and all POJOs in the parameters and return values are represented by a <code>Map</code>.
-Generic invoke does not require attention on the server and can be exposed as normal services.</p>
-<p>Next, let's take a look at how the consumer uses generic invoke for service call.</p>
-<h2>Generic invoke through Spring XML configuration</h2>
-<p>Declare <code>generic="true"</code> in Spring configuration, such as</p>
-<pre><code class="language-xml">"userService" interface="com.alibaba.dubbo.samples.generic.api.IUserService" generic="true"/>
-</code></pre>
-<p>Where you need to use it, you can call it by forcing a type cast to GenericService.</p>
-<pre><code class="language-java">GenericService userService = (GenericService) context.getBean(<span class="hljs-string">"userService"</span>);
-<span class="hljs-comment">// primary param and return value</span>
-String name = (String) userService.$invoke(<span class="hljs-string">"delete"</span>, <span class="hljs-keyword">new</span> String[]{<span class="hljs-keyword">int</span>.class.getName()}, <span class="hljs-keyword">new</span> Object[]{<span class="hljs-number">1</span>});
-System.out.println(name);
-</code></pre>
-<p>Among them,</p>
-<ol>
-<li>
-<p>The interface GenericService has only one method, named $invoke, which takes three arguments, a method name, an array of method parameter types, and an array of parameter values.</p>
-</li>
-<li>
-<p>For arrays of method parameter types</p>
-<p>i. If it is a basic type, such as int or long, use <code>int.class.getName()</code> to get its type;</p>
-<p>ii. If it is a basic type array, such as int[], use <code>int[].class.getName()</code>;</p>
-<p>iii. If it is a POJO, use the full class name directly, such as <code>com.alibaba.dubbo.samples.generic.api.Params</code>.</p>
-</li>
-</ol>
-<h2>Generic invoke through API programming</h2>
-<pre><code class="language-java">ApplicationConfig application = <span class="hljs-keyword">new</span> ApplicationConfig()ApplicationConfig application = <span class="hljs-keyword">new</span> ApplicationConfig();
-application.setName(<span class="hljs-string">"api-generic-consumer"</span>);
-
-RegistryConfig registry = <span class="hljs-keyword">new</span> RegistryConfig();
-registry.setAddress(<span class="hljs-string">"zookeeper://127.0.0.1:2181"</span>);
-
-application.setRegistry(registry);
-
-ReferenceConfig<GenericService> reference = <span class="hljs-keyword">new</span> ReferenceConfig<GenericService>();
-<span class="hljs-comment">// weak type interface name</span>
-reference.setInterface(<span class="hljs-string">"com.alibaba.dubbo.samples.generic.api.IUserService"</span>);
-<span class="hljs-comment">// declared as a generalized interface</span>
-reference.setGeneric(<span class="hljs-keyword">true</span>);
-
-reference.setApplication(application);
-
-<span class="hljs-comment">// replace all interface references with com.alibaba.dubbo.rpc.service.GenericService</span>
-GenericService genericService = reference.get();
-
-String name = (String) genericService.$invoke(<span class="hljs-string">"delete"</span>, <span class="hljs-keyword">new</span> String[]{<span class="hljs-keyword">int</span>.class.getName()}, <span class="hljs-keyword">new</span> Object[]{<span class="hljs-number">1</span>});
-System.out.println(name);
-</code></pre>
-<p>Through the API, you don't need to configure the service in advance like XML. You can dynamically construct ReferenceConfig; the API is more common than XML.</p>
-<h2>The case where parameters or return values are POJOs</h2>
-<p>For example, the method signature is <code>User get(Params params)</code>, where <code>User</code> has two attributes, id and name, and <code>Params</code> has one attribute, query.</p>
-<p>The following is the code of the consumer:</p>
-<pre><code class="language-java">String[] parameterTypes = <span class="hljs-keyword">new</span> String[]{<span class="hljs-string">"com.alibaba.dubbo.samples.generic.api.Params"</span>};
-Map<String, Object> params = <span class="hljs-keyword">new</span> HashMap<String, Object>();
-param.put(<span class="hljs-string">"class"</span>, <span class="hljs-string">"com.alibaba.dubbo.samples.generic.api.Params"</span>);
-param.put(<span class="hljs-string">"query"</span>, <span class="hljs-string">"a=b"</span>);
-Object user = userService.$invoke(<span class="hljs-string">"get"</span>, parameterTypes, <span class="hljs-keyword">new</span> Object[]{param});
-System.out.println(<span class="hljs-string">"sample one result: "</span> + user);
-</code></pre>
-<p>The output of the above code is:</p>
-<pre><code>sample one result: {name=charles, id=1, class=com.alibaba.dubbo.samples.generic.api.User}
-</code></pre>
-<p>Here, the Dubbo framework will automatically convert the return value from POJO to Map.
-It can be seen that the return value <code>user</code> is a HashMap, which stores three k/vs, name, id, and class.</p>
-<h2>Generic interface implementation</h2>
-<p>The implementation of the generic interface is mainly used when the server does not have an API interface. All POJOs in the parameters and return values are represented by Map, which is usually used for framework integration. For example, to implement a generic remote service Mock framework, all service requests can be handled by implementing the interface GenericService.</p>
-<h3>Implementation GenericService on the server</h3>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">GenericServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">GenericService</span> </span>{
- <span class="hljs-meta">@Override</span>
- <span class="hljs-keyword">public</span> Object $invoke(String method, String[] parameterTypes, Object[] args) <span class="hljs-keyword">throws</span> GenericException {
- <span class="hljs-keyword">if</span> (method.equals(<span class="hljs-string">"hi"</span>)) {
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hi, "</span> + args[<span class="hljs-number">0</span>];
- } <span class="hljs-keyword">else</span> <span class="hljs-keyword">if</span> (method.equals(<span class="hljs-string">"hello"</span>)) {
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hello, "</span> + args[<span class="hljs-number">0</span>];
- }
-
- <span class="hljs-keyword">return</span> <span class="hljs-string">"welcome"</span>;
- }
-}
-</code></pre>
-<h3>Server exposed service</h3>
-<pre><code class="language-java">ApplicationConfig application = <span class="hljs-keyword">new</span> ApplicationConfig();
-application.setName(<span class="hljs-string">"api-generic-provider"</span>);
-
-RegistryConfig registry = <span class="hljs-keyword">new</span> RegistryConfig();
-registry.setAddress(<span class="hljs-string">"zookeeper://127.0.0.1:2181"</span>);
-
-application.setRegistry(registry);
-
-GenericService genericService = <span class="hljs-keyword">new</span> GenericServiceImpl();
-
-ServiceConfig<GenericService> service = <span class="hljs-keyword">new</span> ServiceConfig<GenericService>();
-service.setApplication(application);
-service.setInterface(<span class="hljs-string">"com.alibaba.dubbo.samples.generic.api.HelloService"</span>);
-service.setRef(genericService);
-service.export();
-
-ServiceConfig<GenericService> service2 = <span class="hljs-keyword">new</span> ServiceConfig<GenericService>();
-service2.setApplication(application);
-service2.setInterface(<span class="hljs-string">"com.alibaba.dubbo.samples.generic.api.HiService"</span>);
-service2.setRef(genericService);
-service2.export();
-</code></pre>
-<p>Similarly, you can expose the service using XML configuration; in this case, the server does not depend on the two interfaces HiService and HelloService.</p>
-<h3>Service invoke on the consumer</h3>
-<pre><code class="language-java">ApplicationConfig application = <span class="hljs-keyword">new</span> ApplicationConfig();
-application.setName(<span class="hljs-string">"api-generic-consumer"</span>);
-
-RegistryConfig registry = <span class="hljs-keyword">new</span> RegistryConfig();
-registry.setAddress(<span class="hljs-string">"zookeeper://127.0.0.1:2181"</span>);
-
-application.setRegistry(registry);
-
-ReferenceConfig<GenericService> reference = <span class="hljs-keyword">new</span> ReferenceConfig<GenericService>();
-<span class="hljs-comment">// weak type interface name</span>
-reference.setInterface(HiService.class);
-reference.setApplication(application);
-
-HiService hiService = (HiService) reference.get();
-System.out.println(hiService.hi(<span class="hljs-string">"dubbo"</span>));
-
-ReferenceConfig<GenericService> reference2 = <span class="hljs-keyword">new</span> ReferenceConfig<GenericService>();
-<span class="hljs-comment">// weak type interface name</span>
-reference2.setInterface(HelloService.class);
-reference2.setApplication(application);
-
-HelloService helloService = (HelloService) reference2.get();
-System.out.println(helloService.hello(<span class="hljs-string">"community"</span>));
-</code></pre>
-<p>Similarly, the consumer can also reference the service using an XML configuration and then make the call. Here you can see that the calling method is a normal service call, not a generic call. Of course, it is also possible to use generic calls.</p>
-<p>So far, a simple service Mock platform has been successfully launched!</p>
-<h2>Others</h2>
-<ul>
-<li>The generic invoke and generic interface implementations introduced in this article are all based on the native Dubbo protocol. Prior to version 2.6.2, other protocols such as http/hessian don't support generic invoke. Version 2.6.3 will support the generic invoke of these two protocols.</li>
-<li>The relevant sample codes mentioned in this article can be found in dubbo-samples: <a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-generic">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-generic</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-generic-invoke.json b/en-us/blog/dubbo-generic-invoke.json
deleted file mode 100644
index 7b7dfd0..0000000
--- a/en-us/blog/dubbo-generic-invoke.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-generic-invoke.md",
- "__html": "<h1>Generic invoke of Dubbo</h1>\n<p>The generic invoke could be considered to be used in the following cases:</p>\n<ul>\n<li>Service test platform</li>\n<li>API service gateway</li>\n</ul>\n<p>The generic invoke is mainly used when the consumer does not have an API interface;\ninstead of depending the interface jar package, the service call is initiated directly through the GenericService interface, and all POJOs in the parameters and return values are represented by a <cod [...]
- "link": "/en-us/blog/dubbo-generic-invoke.html",
- "meta": {
- "title": "Generic invoke of Dubbo",
- "keywords": "Dubbo, Generic invoke",
- "description": "This article introduces you when and how to use generic invoke of Dubbo."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-invoke.html b/en-us/blog/dubbo-invoke.html
deleted file mode 100644
index 0c6df0d..0000000
--- a/en-us/blog/dubbo-invoke.html
+++ /dev/null
@@ -1,193 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Invoke, Async" />
- <meta name="description" content="This article introduces you how to use Dubbo synchronously or asynchronously." />
- <!-- 网页标签标题 -->
- <title>Dubbo: Several ways about synchronous/asynchronous invoke</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>As we all know，Dubbo adopts a single large join protocol by default and takes the NIO asynchronous communication mechanism of Netty as the low-level implementation. Based on this mechanism, Dubbo implements several invocation modes as follows:</p>
-<ul>
-<li>synchronous invoke</li>
-<li>asynchronous invoke</li>
-<li>parameters callback</li>
-<li>event notification</li>
-</ul>
-<h3>Synchronous invoke</h3>
-<p>Synchronous invoke is a kind of blocking invocation mode, that is the Consumer keeps blocking and waiting, until the Provider returns.</p>
-<p>Generally, a typical synchronous invocation process is as follows:</p>
-<ol>
-<li>Consumer service thread invokes the remote API and sends requests to the Provider. Meanwhile, the current service thread stays in blocking state;</li>
-<li>Provider process relative request after receiving it from Consumer. Then returns the results to Consumer;</li>
-<li>After Consumer receiving results, the current thread continues to execute.</li>
-</ol>
-<p>Here are two problems:</p>
-<ol>
-<li>How does Consumer service thread turn into <code>blocking</code> state?</li>
-<li>How does the service thread be awaked to execute after Consumer receiving results?</li>
-</ol>
-<p>In fact, the low-level I/O operations of Dubbo are all asynchronous. The Consumer gets a Future object after invoking the Provider. For synchronous invoke, the service thread takes advantage of <code>Future#get(timeout)</code> to block and wait for Provider returning results, with the 'timeout' indicating the timeout defined by Consumer. When the result returns, the Future will be set and the blocked service thread will be awaked. The service thread will return an exception if there i [...]
-<h3>Asynchronous invoke</h3>
-<p>For scenarios that Provider has a long response time, it's necessary to implement asynchronous invoke based on Dubbo's underlying asynchronous NIO. It could utilize the resource of Consumer effectively, and costs less than using multi-thread for Consumer.</p>
-<p>Asynchronous invoke does not need specific configuration for Provider. In the example，the API of Provider is defined as follow：</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">AsyncService</span> </span>{
- <span class="hljs-function">String <span class="hljs-title">goodbye</span><span class="hljs-params">(String name)</span></span>;
-}
-</code></pre>
-<h5>Consumer configuration</h5>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:reference</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"asyncService"</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"com.alibaba.dubbo.samples.async.api.AsyncService"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:method</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"goodbye"</span> <span class="hljs-attr">async</span>=<span class="hljs-string">"true"</span>/></span>
-<span class="hljs-tag"></<span class="hljs-name">dubbo:reference</span>></span>
-</code></pre>
-<p>Notice that if we need an asynchronous revoke method, we must use <code><dubbo:method/></code> label to describe it.</p>
-<h5>Consumer triggers invocation</h5>
-<pre><code class="language-java">AsyncService service = ...;
-String result = service.goodbye(<span class="hljs-string">"samples"</span>);<span class="hljs-comment">// returns NULL and DO NOT use!</span>
-Future<String> future = RpcContext.getContext().getFuture();
-... <span class="hljs-comment">// other service thread logic</span>
-result = future.get(); <span class="hljs-comment">// could use get(timeout, unit) to configure timeout, when it needs to get the asynchronous result</span>
-</code></pre>
-<p>After Dubbo Consumer triggers invocation, it uses <code>RpcContext.getContext().getFuture()</code> to get the relative <code>Future</code> object, and then it could start executing other tasks. Anytime when we need results, <code>future.get(timeout)</code> is supposed to be called.</p>
-<p>Under several special conditions, it could be set whether to wait for sending the request, to accelerate the return of invocation:</p>
-<ul>
-<li><code>sent="true"</code> Waiting for sending the request, and return an exception if it fails;</li>
-<li><code>sent="false"</code> Do not wait for the request, and returns immediately after putting the request to the I/O queue.</li>
-</ul>
-<p>We set it to <code>false</code> by default. And detailed configuration is as follows：</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:method</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"goodbye"</span> <span class="hljs-attr">async</span>=<span class="hljs-string">"true"</span> <span class="hljs-attr">sent</span>=<span class="hljs-string">"true"</span> /></span>
-</code></pre>
-<p>If you only want to be asynchronous, then omit the result thoroughly, <code>return="false"</code> could be set to reduce the creation and management cost of Future:</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:method</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"goodbye"</span> <span class="hljs-attr">async</span>=<span class="hljs-string">"true"</span> <span class="hljs-attr">return</span>=<span class="hljs-string">"false"</span>/></span>
-</code></pre>
-<p>At this time，<code>RpcContext.getContext().getFuture()</code> will return <code>null</code>。</p>
-<p>The complete sequence diagram of asynchronous invoke is as follow:</p>
-<p><img src="../../img/blog/dubbo-async.svg" alt="Asynchronous invoke"></p>
-<p>The sample locates at：<a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-async">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-async</a></p>
-<h3>Parameters callback</h3>
-<p>The parameter Callback is somewhat similar to the local Callback mechanism, but Callback is not an inner class or interface of Dubbo. Instead, it is defined by the Provider. Dubbo will generate a reverse proxy based on the long connection, so as to implement the logic of calling the Consumer from the Provider.</p>
-<h5>Service and Callback definition of Provider</h5>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">CallbackService</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">addListener</span><span class="hljs-params">(String key, CallbackListener listener)</span></span>;
-}
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">CallbackListener</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">changed</span><span class="hljs-params">(String msg)</span></span>;
-}
-</code></pre>
-<h5>Service implementation of Provider</h5>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">CallbackServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">CallbackService</span> </span>{
-
- <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> Map<String, CallbackListener> listeners = <span class="hljs-keyword">new</span> ConcurrentHashMap<String, CallbackListener>();
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">CallbackServiceImpl</span><span class="hljs-params">()</span> </span>{
- Thread t = <span class="hljs-keyword">new</span> Thread(<span class="hljs-keyword">new</span> Runnable() {
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">while</span> (<span class="hljs-keyword">true</span>) {
- <span class="hljs-keyword">try</span> {
- <span class="hljs-keyword">for</span> (Map.Entry<String, CallbackListener> entry : listeners.entrySet()) {
- <span class="hljs-keyword">try</span> {
- entry.getValue().changed(getChanged(entry.getKey()));
- } <span class="hljs-keyword">catch</span> (Throwable t) {
- listeners.remove(entry.getKey());
- }
- }
- Thread.sleep(<span class="hljs-number">5000</span>); <span class="hljs-comment">// timely trigger change event</span>
- } <span class="hljs-keyword">catch</span> (Throwable t) {
- t.printStackTrace();
- }
- }
- }
- });
- t.setDaemon(<span class="hljs-keyword">true</span>);
- t.start();
- }
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">addListener</span><span class="hljs-params">(String key, CallbackListener listener)</span> </span>{
- listeners.put(key, listener);
- listener.changed(getChanged(key)); <span class="hljs-comment">// send notification for change</span>
- }
-
- <span class="hljs-function"><span class="hljs-keyword">private</span> String <span class="hljs-title">getChanged</span><span class="hljs-params">(String key)</span> </span>{
- <span class="hljs-keyword">return</span> <span class="hljs-string">"Changed: "</span> + <span class="hljs-keyword">new</span> SimpleDateFormat(<span class="hljs-string">"yyyy-MM-dd HH:mm:ss"</span>).format(<span class="hljs-keyword">new</span> Date());
- }
-}
-</code></pre>
-<h5>Service exposure of Provider</h5>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">bean</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"callbackService"</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"com.alibaba.dubbo.samples.callback.impl.CallbackServiceImpl"</span>/></span>
-
-<span class="hljs-tag"><<span class="hljs-name">dubbo:service</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"com.alibaba.dubbo.samples.callback.api.CallbackService"</span> <span class="hljs-attr">ref</span>=<span class="hljs-string">"callbackService"</span> <span class="hljs-attr">connections</span>=<span class="hljs-string">"1"</span> <span class="hljs-attr">callbacks</span>=<span class="hljs-string">"1000"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:method</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"addListener"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:argument</span> <span class="hljs-attr">index</span>=<span class="hljs-string">"1"</span> <span class="hljs-attr">callback</span>=<span class="hljs-string">"true"</span>/></span>
- <span class="hljs-comment"><!--<dubbo:argument type="com.demo.CallbackListener" callback="true" />--></span>
- <span class="hljs-tag"></<span class="hljs-name">dubbo:method</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">dubbo:service</span>></span>
-</code></pre>
-<p>Here，Provider needs to declare which parameter is the Callback parameter in the method.</p>
-<h5>Callback interface implementation of Consumer</h5>
-<pre><code class="language-java">CallbackService callbackService = ...;
-callbackService.addListener(<span class="hljs-string">"foo.bar"</span>, <span class="hljs-keyword">new</span> CallbackListener() {
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">changed</span><span class="hljs-params">(String msg)</span> </span>{
- System.out.println(<span class="hljs-string">"callback1:"</span> + msg);
- }
-});
-</code></pre>
-<p>The implementation class of the Callback interface is on the Consumer, which automatically exports a Callback service when the method is called. Thus during Provider processing the call, if the parameter is determined as Callback, it will generate a proxy. Therefore, when the service implementation class calling the Callback method, it will be passed to the Consumer to execute the code.</p>
-<p>The sample code above is located at：<a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-callback">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-callback</a></p>
-<p>This invocation mode is somewhat like message publishing and subscribing, but there is a little difference. For example, when the Consumer completes the export of Callback service, if it restarts later, then the Provider will fail to adjust. Meanwhile it is also a problem for the Provider to clean up the proxy.</p>
-<h3>Event notification</h3>
-<p>Event notification allows the Consumer triggering three events，particularly <code>oninvoke</code>, <code>onreturn</code>, <code>onthrow</code> before calling, after calling or occurring exceptions.</p>
-<p>You can specify which events need to be notified during configuring Consumer, such as:</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">bean</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"demoCallback"</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"com.alibaba.dubbo.samples.notify.impl.NotifyImpl"</span> /></span>
-
-<span class="hljs-tag"><<span class="hljs-name">dubbo:reference</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"demoService"</span> <span class="hljs-attr">check</span>=<span class="hljs-string">"false"</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"com.alibaba.dubbo.samples.notify.api.DemoService"</span> <span class="hljs-attr">version</span>=<span class="hljs-string">"1.0.0"</span> <span class="hljs-attr">group</span>=<span class="hljs [...]
- <span class="hljs-tag"><<span class="hljs-name">dubbo:method</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"sayHello"</span> <span class="hljs-attr">onreturn</span>=<span class="hljs-string">"demoCallback.onreturn"</span> <span class="hljs-attr">onthrow</span>=<span class="hljs-string">"demoCallback.onthrow"</span>/></span>
-<span class="hljs-tag"></<span class="hljs-name">dubbo:reference</span>></span>
-</code></pre>
-<p>Among them，the code of NotifyImpl is as follow：</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">NotifyImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Notify</span></span>{
-
- <span class="hljs-keyword">public</span> Map<Integer, String> ret = <span class="hljs-keyword">new</span> HashMap<Integer, String>();
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onreturn</span><span class="hljs-params">(String name, <span class="hljs-keyword">int</span> id)</span> </span>{
- ret.put(id, name);
- System.out.println(<span class="hljs-string">"onreturn: "</span> + name);
- }
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onthrow</span><span class="hljs-params">(Throwable ex, String name, <span class="hljs-keyword">int</span> id)</span> </span>{
- System.out.println(<span class="hljs-string">"onthrow: "</span> + name);
- }
-}
-</code></pre>
-<p>Here we address that the parameter rules of three methods in the custom Notify interface are as follows:</p>
-<ul>
-<li><code>oninvoke</code> method's parameters are the same as the calling method parameters;</li>
-<li><code>onreturn</code> method's first parameter is the returned value of calling method，and the others are the same as the calling method;</li>
-<li><code>onthrow</code> method's first parameter is an invoked exception，and the others are the same as the calling method.</li>
-</ul>
-<p>In the above configuration, <code>sayHello</code> method is an asynchronous invocation, so the execution of event notification method is also synchronous. You can configure the <code>async = true</code> to make method invocation asynchronous, at this moment, event notification method is executed asynchronously. Especially emphasize that <code>oninvoke</code> method is executed synchronously, whether is an asynchronous call or not.</p>
-<p>Please refer to the sample code for event notification：<a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify</a></p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-invoke.json b/en-us/blog/dubbo-invoke.json
deleted file mode 100644
index e05a847..0000000
--- a/en-us/blog/dubbo-invoke.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-invoke.md",
- "__html": "<h1>Dubbo: Several ways about synchronous/asynchronous invoke</h1>\n<p>As we all know，Dubbo adopts a single large join protocol by default and takes the NIO asynchronous communication mechanism of Netty as the low-level implementation. Based on this mechanism, Dubbo implements several invocation modes as follows:</p>\n<ul>\n<li>synchronous invoke</li>\n<li>asynchronous invoke</li>\n<li>parameters callback</li>\n<li>event notification</li>\n</ul>\n<h3>Synchronous invoke</h3>\ [...]
- "link": "/en-us/blog/dubbo-invoke.html",
- "meta": {
- "title": "Dubbo: Several ways about synchronous/asynchronous invoke",
- "keywords": "Dubbo, Invoke, Async",
- "description": "This article introduces you how to use Dubbo synchronously or asynchronously."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-k8s.html b/en-us/blog/dubbo-k8s.html
deleted file mode 100644
index 156af22..0000000
--- a/en-us/blog/dubbo-k8s.html
+++ /dev/null
@@ -1,190 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Kubernetes, K8S" />
- <meta name="description" content="This article will try to register Dubbo service to Kubernetes and integrate with Kubernetes's multi-tenancy security system." />
- <!-- 网页标签标题 -->
- <title>Integrate Dubbo with Kubernetes</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>Dubbo's provider don't care about service registration.Open its Dubbo service port,the declaration and publishment of the service will be executed by Kubernetes.
-Dubbo's consumer directly discovers the corresponding service endpoints of Kubernetes during service discovery procedure, thereby reusing Dubbo's existing microservice channel capabilities.The benefit is that there is no need to rely on any third-party soft-loaded registry and it can be seamlessly integrated into the multi-tenant security system of Kubernetes. Reference demo : <a href="https://github.com/dubbo/dubbo-Kubernetes">https://github.com/dubbo/dubbo-ubernetes</a></p>
-<h1>Introduction</h1>
-<p>Kubernates is a hierarchical system with rich secondary development function based on the expansibility.</p>
-<ul>
-<li>First of all, Kubernates's core function is to manage the container cluster. Kubernates manages the storage and calculation of containerized cluster, based on the container runtime (CRI), network interface (CNI) and storage service interface (CSI/FV).</li>
-<li>Secondly，Kubernates has application-oriented deployment and routing capabilities，including statefulness/statelessness，batch processing and service-oriented applications，especially the application management based on microservices architecture which includes service discovery，service definition and unified configuration on the basis of configmap.</li>
-<li>Finally, on top of the abstract model of the basic resource (mainly the resources of abstract infrastructure, IaaS) and the application layer is the governance layer, which includes elastic expansion, namespaces/tenants and so on. Naturally, it is a matter of course to set up service about unified log center and omnidirectional monitoring on the Kubernetes based upon the foundational capabilities of atomic inner core.</li>
-</ul>
-<p>We will explain the above description with a diagram of Kubernetes Architecture. In 2018, Kubernetes took a qualitative step toward the standard PaaS basement.Someone hold opinions that the reason is the ability for secondary development on the basis of the expansion and someone think the key is declarative programming and strong community operations relying on Google and Redhat. However,I think the essential reason is Layered architecture and the abstract domain modeling in the probl [...]
-<p><img src="../../img/blog/k8s/1.png" alt="img"></p>
-<p>From a micro-service architecture perspective, Kubernetes is a micro-service framework (more appropriate than a micro-service platform or toolkit set at this time) in a sense, supporting the basic capabilities of microservices for service discovery/registration. Use the following table to make a brief description.</p>
-<table>
-<thead>
-<tr>
-<th style="text-align:left">The design of microservice</th>
-<th style="text-align:left">The function of Kubernetes</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td style="text-align:left">Point 1：API gateway</td>
-<td style="text-align:left">Ingress</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 2：Statelessness, distinguish between stateful and stateless applications</td>
-<td style="text-align:left">Stateless corresponds to Deployment，and stateful corresponds to StatefulSet</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 3：Horizontal expansion of the database</td>
-<td style="text-align:left">Headless service points to PaaS service or StatefulSet deployment</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 4：Cache</td>
-<td style="text-align:left">Headless service points to PaaS service or StatefulSet deployment</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 5：Service splitting and service discovery</td>
-<td style="text-align:left">Service</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 6：Service orchestration and flexibility</td>
-<td style="text-align:left">Replicas of deployment</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 7：Unified configuration center</td>
-<td style="text-align:left">ConfigMap</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 8：Unified log center</td>
-<td style="text-align:left">DaemonSet deploys log agent</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 9：Circut break, current limiting and downgrade</td>
-<td style="text-align:left">Service Mesh</td>
-</tr>
-<tr>
-<td style="text-align:left">Point 10：Comprehensive monitoring</td>
-<td style="text-align:left">Cadsivor, DaemonSet deploys and monitors Agent</td>
-</tr>
-</tbody>
-</table>
-<p>By the way, the microservices field involves many issues, which can be explained as follows. When building microservices, we will delve into Distributed System, a discipline has a 40-year research background and is rooted in the adaptive system theory. It's a bit complicated, but the concepts it covers are more or less heard for us, and it solves problems that we're familiar with:</p>
-<ul>
-<li>Deployment</li>
-<li>Delivery</li>
-<li>APIs</li>
-<li>Versioning</li>
-<li>Contracts</li>
-<li>Scaling / Autoscaling</li>
-<li>Service Discovery</li>
-<li>Load Balancing</li>
-<li>Routing / Adaptive Routing</li>
-<li>Health Checking</li>
-<li>Configuration</li>
-<li>Circuit Breaking</li>
-<li>Bulk-heads</li>
-<li>TTL / Deadlining</li>
-<li>Latency Tracing</li>
-<li>Service Causal Tracing</li>
-<li>Distributed logging</li>
-<li>Metrics Exposure, Collection</li>
-</ul>
-<p>For Kubernetes, only a few of problems are solved. Problems such as Dynamic Routing, Stability Control (Circuit Breaking, Bulk-heads, etc.) , Distributed Service Tracking, etc. are all the blank. These problems are exactly what Service Mesh needs to solve, and these also plays an important role in CNCF's Tail Map. Of course, as Dubbo is a basically complete microservices infrastructure (Dubbo is based on the Sidecar which is a common solution for solving cross-language claims in Servi [...]
-<blockquote>
-<p><span data-type="color" style="color:rgb(119, 119, 119)"><span data-type="background" style="background-color:rgb(255, 255, 255)">A service mesh is a dedicated infrastructure layer for handling service-to-service communication. It's responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application.</span></span></p>
-</blockquote>
-<p>We will know the existing solution, Dubbo integrates the Clould Native Equipment - Kubernetes's basic abilities to solve the microservices's core problems, can be regarded as a Service Mesh solution in a narrow sense, but it can only be used in the Java field. You can understand the above words as a joke, haha.</p>
-<h1>T<span data-type="color" style="color:rgb(51, 51, 51)"><span data-type="background" style="background-color:rgb(255, 255, 255)">hought</span></span>/Plan</h1>
-<p>Kubernetes is a natural address registration center for microservices, similar to zookeeper, VIPserver and Configserver used internally by Alibaba. Specifically, the Pod in Kubernetes is a running instance of the application. The scheduled deployment/start/stop of the Pod will call the API-Server service to maintain its state to ETCD. The service in Kubernetes is coresponded to the concept of the microservices defined as follows.</p>
-<blockquote>
-<p>A Kubernetes Service is an abstraction layer which defines a logical set of Pods and enables external traffic exposure, load balancing and service discovery for those Pods.</p>
-</blockquote>
-<p>In conclusion, the Kubernetes service has the following characteristics:</p>
-<ul>
-<li>Each Service has a unique name and corresponding IP. IP is automatically assigned by Kubernetes and the name is defined by the developer.</li>
-<li>Service IP has several manifestations: ClusterIP, NodePort, LoadBalance and Ingress. ClusterIP is mainly used for intra-cluster communication; NodePort, Ingress and LoadBalance, which are used to expose services to access portals outside the cluster.</li>
-</ul>
-<p>At first sight, the service of Kubernetes has its own IP, while under the original fixed mindset: Dubbo/HSF service is aggregated by the IP of the entire service cluster, that means, Kubernetes and Dubbo/HSF look like something different in natural, but when carefully thinking, the difference becomes insignificant. Because the only IP under Kubernetes is just a Virtural IP--VIP, behind the vip are multiple endpoints, which is the factual processing node.</p>
-<p>Here we only discuss the situation that the Dubbo service in the cluster is accessed in the same Kubernetes cluster, As for the provider outside Kubernetes to access the provider in Kubernetes, since it involves the problem of network address space, and it usually requires GateWay/loadbalance for mapping conversion, which there not detail discussion for this case. Besides, there are two options available for Kubernetes:</p>
-<ol>
-<li>
-<p>DNS: The default Kubernetes service is based on the DNS plugin (The latest version of the recommendation is coreDNS), one proposal on Dubbo is about this. since HSF/Dubbo has always highlighted its soft-load address discovery capability, it ignores Static's strategy insteadily, my understanding is that as a service discovery mechanism, the static resolution mechanism is one of the simplest and most needed to support mechanism, you can also refer to Envoy's point of views. While at th [...]
-<p><img src="https://img.alicdn.com/tfs/TB1Kj1ktpkoBKNjSZFEXXbrEVXa-985-213.png" alt="img"></p>
-</li>
-<li>
-<p>API：DNS relies on the DNS plugin, which will generate additional operation, so consider directly obtaining the endpoint through the client of Kubernetes. In fact, by accessing the API server interface of Kubernetes, you can directly obtain the list of endpoints behind a certain servie, and can also monitor the changes in its address list. Thereby implementing the soft load discovery strategy recommended by Dubbo/HSF. Refer to the code for details:</p>
-</li>
-</ol>
-<p>The above two thoughts need to consider the following two points:</p>
-<ol>
-<li>Kubernetes and Dubbo are consistent with the mapping name of service. Dubbo's service is determined by serviename, group, version to determine its uniqueness, and servicename generally has a longer package name for its service interface. Need to map the servie name of Kubernetes and the service name of dubbo. Either add a property like SOFA to define it. This is a big change, but it is most reasonable. Or it is a fixed rule to reference the deployed environment variables, which can b [...]
-<li>Port problem:The default Pod and Pod network interoperability is solved, need to be validated.</li>
-</ol>
-<h2>Demo Verification</h2>
-<p>The following is a demo deployment through Kubernetes service in Alibaba Cloud's Container Registry and EDAS. Visit Alibaba Cloud -》Container Registry.</p>
-<ol>
-<li>Create repo and bind the github codebase. As shown below.</li>
-</ol>
-<p><img src="https://img.alicdn.com/tfs/TB1m.tEtrorBKNjSZFjXXc_SpXa-1892-870.png" alt="img"></p>
-<ol start="2">
-<li>
-<p>Click Manage enter the repository details page. Click Build in images service panel, construct the demo into image and publish it to the specified repository. As shown below.</p>
-<p><img src="https://img.alicdn.com/tfs/TB1oYqvtcIrBKNjSZK9XXagoVXa-1872-888.png" alt="img"></p>
-</li>
-<li>
-<p>Switch to Enterprise Distributed Application Services (EDAS) products panel, visit Resource Management -> Clusters. Create Kubernetes cluster and bind ECS. As shown below.</p>
-<p><img src="https://img.alicdn.com/tfs/TB1b1p2trZnBKNjSZFKXXcGOVXa-1858-833.png" alt="img"></p>
-</li>
-<li>
-<p>Application Management -> Create application, type Kubernetes application and specify the image in the container registry . As shown below.</p>
-<p><img src="https://img.alicdn.com/tfs/TB1_YywtDCWBKNjSZFtXXaC3FXa-1737-588.png" alt="img"></p>
-<p><img src="https://img.alicdn.com/tfs/TB18uzTtdcnBKNjSZR0XXcFqFXa-1820-861.png" alt=""></p>
-</li>
-<li>
-<p>After creation , then deploy applications. As shown below.</p>
-</li>
-</ol>
-<p><img src="https://img.alicdn.com/tfs/TB1fEpEtrorBKNjSZFjXXc_SpXa-1846-783.png" alt=""></p>
-<ul>
-<li>
-<p>The supplementary application name cannot have uppercase letters, all lowercase, otherwise there is a problem of deployment failure.</p>
-</li>
-<li>
-<p>When creating an app, after selecting the image, the next button cannot be clicked and you need to click Choose to continue.</p>
-</li>
-<li>
-<p>EDAS has two independent Kubernetes services, one based on Alibaba Cloud's container service, and one set by Lark. I experience the latter.</p>
-</li>
-<li>
-<p>The development joint of Docker and IDE integration, you need to consider the relevant plug-ins for integrating IDEA.</p>
-</li>
-<li>
-<p>There is always an error in deployment, maybe there is a problem with the Kubernetes service. Need further investigation.</p>
-</li>
-</ul>
-<p>{"kind":"Pod","namespace":"lzumwsrddf831iwarhehd14zh2-default","name":"dubbo-k8s-demo-610694273-jq238","uid":"12892e67-8bc8-11e8-b96a-00163e02c37b","apiVersion":"v1","resourceVersion":"850282769"},"reason":"FailedSync","message":"Error syncing pod","</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-k8s.json b/en-us/blog/dubbo-k8s.json
deleted file mode 100644
index e53fd8a..0000000
--- a/en-us/blog/dubbo-k8s.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-k8s.md",
- "__html": "<h1>General goal</h1>\n<p>Dubbo's provider don't care about service registration.Open its Dubbo service port,the declaration and publishment of the service will be executed by Kubernetes.\nDubbo's consumer directly discovers the corresponding service endpoints of Kubernetes during service discovery procedure, thereby reusing Dubbo's existing microservice channel capabilities.The benefit is that there is no need to rely on any third-party soft-loaded registry and it can be se [...]
- "link": "/en-us/blog/dubbo-k8s.html",
- "meta": {
- "title": "Integrate Dubbo with Kubernetes",
- "keywords": "Dubbo, Kubernetes, K8S",
- "description": "This article will try to register Dubbo service to Kubernetes and integrate with Kubernetes's multi-tenancy security system."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-loadbalance.html b/en-us/blog/dubbo-loadbalance.html
deleted file mode 100644
index 0a9d7d6..0000000
--- a/en-us/blog/dubbo-loadbalance.html
+++ /dev/null
@@ -1,258 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, LoadBalance" />
- <meta name="description" content="This article introduces you what is load balance and how load balance strategy is implemented in Dubbo." />
- <!-- 网页标签标题 -->
- <title>Dubbo's Load Balance</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Background</h2>
-<p>Dubbo is a distributed service framework that avoids single point of failure and horizontal expansion of support services. A service typically deploys multiple instances. How to select a call from a cluster of multiple service providers involves a load balancing strategy.</p>
-<h2>Concepts</h2>
-<p>Before discussing load balancing, I will explain these three concepts first.</p>
-<ol>
-<li>Load Balancing</li>
-<li>Fault-tolerant Cluster</li>
-<li>Service Route</li>
-</ol>
-<p>These three concepts are confusing. They all describe how to choose from multiple Providers to make calls. So what is the difference between them? Let me give a simple example and explain these concepts clearly.</p>
-<p>There is a Dubbo user service, 10 deployed in Beijing and 20 deployed in Shanghai. A service consumer in Hangzhou initiated a call and then the following steps executed:</p>
-<ol>
-<li>According to the configured routing rule, if the call is initiated by Hangzhou, it will be routed to the nearest 20 Providers in Shanghai.</li>
-<li>According to the configured random load balancing strategy, one of the 20 Providers is randomly selected to be called, assuming that the 7th Provider is randomly selected.</li>
-<li>As a result, calling the 7th Provider failed.</li>
-<li>Retried other servers according to the configured Fault-tolerant Cluster mode.</li>
-<li>The call to the 13th Provider was successful.</li>
-</ol>
-<p>Steps 1, 2, and 4 above correspond to routing, load balancing, and fault-tolerant cluster. In Dubbo, a subset is selected by routing from multiple Providers according to routing rules, then a Provider selected from the subset according to load balancing to make this call. If the call fails, Dubbo retry or schedule retransmission or fail-fast according to the Fault-tolerant Cluster policy. You can see the routes in Dubbo, load balancing and Fault-tolerant Cluster exectute at different [...]
-<h2>Dubbo's Internal Load Balancing Strategy</h2>
-<p>Dubbo has four Internal Load Balancing Strategies:</p>
-<ol>
-<li>RandomLoadBalance: Random load balancing. Choose a Provider randomly. It is Dubbo's default load balancing strategy.</li>
-<li>Round Robin Load Balancing: Polling load balancing, then chooses one Provider.</li>
-<li>LeastActiveLoadBalance: The minimum number of active calls, the random number of the same active number. The active number refers to the difference before and after the call. Make slow providers receive fewer requests, because the slower Provider before and after the difference of calls will be larger.</li>
-<li>ConsistentHashLoadBalance: Consistent hash load balancing. Requests with the same parameters always fall on the same machine.</li>
-</ol>
-<h3>1. Random Load Balancing</h3>
-<p>As the name implies, the random load balancing strategy is to select one from multiple Providers randomly. However, random load balancing in Dubbo has a weighting concept that sets the random probability according to the weight. For example, there are 10 Providers, it's not to say that the probability of each Provider is the same, but to assign the probability by combining the weights of these 10 providers.</p>
-<p>In Dubbo, you can set weights on the Provider. For example, if the performance of the machine is better, you can set a larger weight. If the performance is poorer, you can set a smaller weight. Weights have an impact on load balancing. The weight of provider can be set in Dubbo Admin.</p>
-<h4>Weight-based Load Balancing Algorithm</h4>
-<p>The stochastic strategy will determine whether the weights of all the invokers are the same at first. If they are all the same, then the processing is relatively simple. Using <code>random.nexInt(length)</code>, you can randomly generate an invoker serial number, and select the corresponding invoker according to the serial number. If the service provider not set weight in Dubbo Admin, then all the invokers have the same weight, the default is 100. If the weights are different, then yo [...]
-<table>
-<thead>
-<tr>
-<th>Invoker</th>
-<th>Weight</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>A</td>
-<td>10</td>
-</tr>
-<tr>
-<td>B</td>
-<td>20</td>
-</tr>
-<tr>
-<td>C</td>
-<td>20</td>
-</tr>
-<tr>
-<td>D</td>
-<td>30</td>
-</tr>
-</tbody>
-</table>
-<p>The total weight of A, B, C and D is 10 + 20 + 20 + 30 = 80. Spread 80 numbers in the following diagram:</p>
-<pre><code>+-----------------------------------------------------------------------------------+
-| | | | |
-+-----------------------------------------------------------------------------------+
-1 10 30 50 80
-
-|-----A----|---------B----------|----------C---------|---------------D--------------|
-
-
----------------------15
-
--------------------------------------------37
-
------------------------------------------------------------54
-</code></pre>
-<p>There are four areas in the above picture, and the lengths are the weights of A, B, C and D, respectively. Use <code>random.nextInt(10 + 20 + 20 + 30)</code> to randomly select one of the 80 numbers. Then determine which area the number is distributed in. For example, if random to 37, 37 is distributed in the C region, then select inboker C. 15 is in the B area, 54 is in the D area.</p>
-<h4>Random load balancing Source code</h4>
-<p>Below is the source code for random load balancing. For ease of reading and understanding, I removed the extraneous parts.</p>
-<pre><code>public class RandomLoadBalance extends AbstractLoadBalance {
-
- private final Random random = new Random();
-
- protected <T> Invoker<T> doSelect(List<Invoker<T>> invokers, URL url, Invocation invocation) {
- int length = invokers.size(); // total invoker
- int totalWeight = 0; // Sum of invokers' weights
-
- // Determine if all the invokers have the same weight
- // If the weights are the same, it is simple to generate an index directly from Random.
- boolean sameWeight = true;
- for (int i = 0; i < length; i++) {
- int weight = getWeight(invokers.get(i), invocation);
- totalWeight += weight; // Sum
- if (sameWeight && i > 0 && weight != getWeight(invokers.get(i - 1), invocation)) {
- sameWeight = false;
- }
- }
-
- if (totalWeight > 0 && !sameWeight) {
- // If not all of the invoker weights are the same, load balancer will randomly choose invoker based on its weight. The greater the weight, the greater the probability of being selected
- int offset = random.nextInt(totalWeight);
- for (int i = 0; i < length; i++) {
- offset -= getWeight(invokers.get(i), invocation);
- if (offset < 0) {
- return invokers.get(i);
- }
- }
- }
- // If all invokers have the same weight
- return invokers.get(random.nextInt(length));
- }
-}
-</code></pre>
-<h3>2. Round Robin Load Balancing</h3>
-<p>Round Robin Load Balancing, is to call all Providers in turn. As with random load balancing strategies, Round Robin Load Balancing policies also has a weighting concept. The Round Robin Load Balancing algorithm allows RPC calls to be allocated exactly as we set. Whether it is a small or large number of calls. However, there are also some shortcomings in the Round Robin Load Balancing algorithm. There is a problem that the slow provider accumulates the request. For example, the second [...]
-<h3>3. Minimum Active Call Load Balancing</h3>
-<p>Official explanation:</p>
-<blockquote>
-<p>The active number refers to the difference between the counts before and after the call. Select the machine with the minimum number of active calls or choose a random one among machines with the same active number, so that the slower machine can receives less requests.</p>
-</blockquote>
-<p>This explanation seems to be ambigious. We know the purpose is to ensure the slower machine receive less requests, but it is not clear how to achieve it. An example is here: each service maintains an active number counter. When A machine starts processing the request, the counter is incremented by 1. At this time, A is still processing. If the processing is completed, the counter is decremented by 1. B machine processes very quickly after receiving the request. Then the active numbers [...]
-<p>When processing a new request, Consumer will check the active number of all Providers. If there is only one Invoker with the minimum active number, the Invoker is returned directly.</p>
-<pre><code>if (leastCount == 1) {
- // if there is only one minimum value then return directly
- return invokers.get(leastIndexs[0]);
-}
-</code></pre>
-<p>If there are multiple Invokers with the minimum active number, plus the weights are not equal and the total weight is greater than 0, then generate a random weight ranging from 0 to totalWeight. Finally, the Invoker is selected based on the randomly generated weights.</p>
-<pre><code>if (! sameWeight && totalWeight > 0) {
- // if the weights are not equal and the toatl weight is greater than 0 then choose randomly according to total weight
-
- int offsetWeight = random.nextInt(totalWeight);
-
- // and determine which segment the random value falls on.
-
- for (int i = 0; i < leastCount; i++) {
- int leastIndex = leastIndexs[i];
- offsetWeight -= getWeight(invokers.get(leastIndex), invocation);
- if (offsetWeight <= 0)
- return invokers.get(leastIndex);
- }
-}
-</code></pre>
-<h3>4. Consistent Hash Algorithm</h3>
-<p>Use consistent hash algorithm to ensure that requests with same parameters are always sent to the same Provider. When a Provider crashes, requests originally sent to the Provider is spread evenly to other Providers based on the virtual node without causing drastic changes. The algorithm can be seen at: <a href="http://en.wikipedia.org/wiki/Consistent_hashing">http://en.wikipedia.org/wiki/Consistent_hashing</a></p>
-<p>By default, only the first parameter is hashed. Configure if you would like to modify it:</p>
-<pre><code><dubbo:parameter key="hash.arguments" value="0,1" />
-</code></pre>
-<p>By default, 160 virtual nodes are used. Configure if you would like to modify it:</p>
-<pre><code><dubbo:parameter key="hash.nodes" value="320" />
-</code></pre>
-<p>Consistent hash algorithms can be used in conjunction with caching mechanisms. For example, there is a service getUserInfo(String userId). After the hash algorithm is set, the same userId call is sent to the same Provider. This Provider can cache user data in memory, reducing the number of accesses to the database or distributed cache. If this part of the data is allowed to be inconsistent for some time, this approach can be considered. The number of dependencies and accesses to middl [...]
-<h2>Load Balancing Configuration</h2>
-<p>If load balancing is not specified, random load balancing is used by default. Load balancing can also be explicitly specified based on our needs. Load balancing can be configured in multiple local classes, such as Provider Side, Consumer Side, Service Level, and Method Level.</p>
-<h3>Server Side Service Level</h3>
-<pre><code><dubbo:service interface="..." loadbalance="roundrobin" />
-</code></pre>
-<p>All methods of the service use roundrobin load balancing.</p>
-<h3>Client Side Service Level</h3>
-<pre><code><dubbo:reference interface="..." loadbalance="roundrobin" />
-</code></pre>
-<p>All methods of the service use roundrobin load balancing.</p>
-<h3>Server Side Method Level</h3>
-<pre><code><dubbo:service interface="...">
- <dubbo:method name="hello" loadbalance="roundrobin"/>
-</dubbo:service>
-</code></pre>
-<p>Only the hello method of the service uses roundrobin load balancing.</p>
-<h3>Client Side Method Level</h3>
-<pre><code><dubbo:reference interface="...">
- <dubbo:method name="hello" loadbalance="roundrobin"/>
-</dubbo:reference>
-</code></pre>
-<p>Only the hello method of the service uses roundrobin load balancing.</p>
-<p>Similar to other Dubbo configurations, multiple configurations are covered:</p>
-<ol>
-<li>The method level takes precedence, the interface level is next, and the global configuration comes last.</li>
-<li>If the level is the same, the Consumer is given priority and the Provider is next</li>
-</ol>
-<p>Therefore, the priority of the above four configurations is:</p>
-<ol>
-<li>Client side method level configuration.</li>
-<li>Client side interface level configuration.</li>
-<li>Server side method level configuration.</li>
-<li>Server side interface level configuration.</li>
-</ol>
-<h2>Extended Load Balancing</h2>
-<p>Four load balancing implementations of Dubbo meet the requirements in most cases. Sometimes, we may need to implement our own load balancing strategy because of the needs of the business. This chapter only explains how to configure the load balancing algorithm. For more on the Dubbo extension mechanism, go to the Dubbo extension mechanism practice.</p>
-<ol>
-<li>Implementing the LoadBalance interface</li>
-</ol>
-<p>The following is Dubbo's LoadBalance interface:</p>
-<pre><code>@SPI(RandomLoadBalance.NAME)
-public interface LoadBalance {
- @Adaptive("loadbalance")
- <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException;
-}
-</code></pre>
-<p>This is the interface of the SPI. The parameters of the select method are as follows:</p>
-<ul>
-<li>invokers: A list of all service Providers.</li>
-<li>url: Some configuration information, such as interface name, check or not, serialization.</li>
-<li>invocation: Information called by the RPC, including the method name, method parameter type, and method parameters. Here is a LoadBalance implemented by us. The implementation is very simple - Choose the first Invoker:</li>
-</ul>
-<pre><code>package com.demo.dubbo;
-public class DemoLoadBalance implements LoadBalance {
- @Override
- public <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException {
- System.out.println("[DemoLoadBalance]Select the first invoker...");
- return invokers.get(0);
- }
-}
-</code></pre>
-<ol start="2">
-<li>Add a resource file</li>
-</ol>
-<p>Add a file:
-<code>src/main/resource/META-INF/dubbo/com.alibaba.dubbo.rpc.cluster.LoadBalance</code>
-This is a simple text file. The file contents are as follows:</p>
-<pre><code>demo=my=com.demo.dubbo.DemoLoadBalance
-</code></pre>
-<ol start="3">
-<li>Configure to use custom LoadBalance</li>
-</ol>
-<pre><code><dubbo:reference id="helloService" interface="com.demo.dubbo.api.IHelloService" loadbalance="demo" />
-</code></pre>
-<p>Configure <code><loadbalance="demo"></code> in <code>dubbo:reference</code> at the Consumer side.</p>
-<p>After 3 steps above, we wrote a custom LoadBalance and told Dubbo to use it. Start Dubbo and we can see that Dubbo has used a custom DemoLoadBalance.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-loadbalance.json b/en-us/blog/dubbo-loadbalance.json
deleted file mode 100644
index 2df2a9e..0000000
--- a/en-us/blog/dubbo-loadbalance.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-loadbalance.md",
- "__html": "<h1>Dubbo's Load Balance</h1>\n<h2>Background</h2>\n<p>Dubbo is a distributed service framework that avoids single point of failure and horizontal expansion of support services. A service typically deploys multiple instances. How to select a call from a cluster of multiple service providers involves a load balancing strategy.</p>\n<h2>Concepts</h2>\n<p>Before discussing load balancing, I will explain these three concepts first.</p>\n<ol>\n<li>Load Balancing</li>\n<li>Fault-t [...]
- "link": "/en-us/blog/dubbo-loadbalance.html",
- "meta": {
- "title": "Dubbo's Load Balance",
- "keywords": "Dubbo, LoadBalance",
- "description": "This article introduces you what is load balance and how load balance strategy is implemented in Dubbo."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-beijing-may-12th-2018.html b/en-us/blog/dubbo-meetup-beijing-may-12th-2018.html
deleted file mode 100644
index ed22e2d..0000000
--- a/en-us/blog/dubbo-meetup-beijing-may-12th-2018.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Beijing, meetup" />
- <meta name="description" content="The first Dubbo meetup has been held in Beijing." />
- <!-- 网页标签标题 -->
- <title>The first Dubbo meetup has been held in Beijing</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The first Dubbo meetup has successfully been held in Beijing, over 400+ people were present. What a great event!</p>
-<p>Please enjoy the slides of the topics:</p>
-<ul>
-<li>Ian Luo: Dubbo's present and future (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf">slides</a></li>
-<li>Jun Liu: Introduction to the 4th Aliware Performance Challenge (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/introduction-to-4th-aliware-performance-challenge.pdf">slides</a></li>
-<li>Zhixuan Chen: Quickly building Microservice with Dubbo and Spring-boot (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/quickly-building-microservice-with-dubbo-and-springboot.pdf">slides</a></li>
-<li>Xin Wang: Dubbo and Weidian's Practice on Microservice Architecture (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-and-weidian's-practice-on-microservice-architecture.pdf">slides</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-beijing-may-12th-2018.json b/en-us/blog/dubbo-meetup-beijing-may-12th-2018.json
deleted file mode 100644
index 97b1878..0000000
--- a/en-us/blog/dubbo-meetup-beijing-may-12th-2018.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-meetup-beijing-may-12th-2018.md",
- "__html": "<h2>The first Dubbo meetup has been held in Beijing</h2>\n<p>The first Dubbo meetup has successfully been held in Beijing, over 400+ people were present. What a great event!</p>\n<p>Please enjoy the slides of the topics:</p>\n<ul>\n<li>Ian Luo: Dubbo's present and future (Chinese) <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf\">slides</a></li>\n<li>Jun Liu: Introduction to the 4th Aliware Performance C [...]
- "link": "/en-us/blog/dubbo-meetup-beijing-may-12th-2018.html",
- "meta": {
- "title": "The first Dubbo meetup has been held in Beijing",
- "keywords": "Dubbo, Beijing, meetup",
- "description": "The first Dubbo meetup has been held in Beijing."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-chengdu.html b/en-us/blog/dubbo-meetup-chengdu.html
deleted file mode 100644
index df891cb..0000000
--- a/en-us/blog/dubbo-meetup-chengdu.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Chengdu, meetup" />
- <meta name="description" content="The fourth Dubbo meetup has been held in Chengdu." />
- <!-- 网页标签标题 -->
- <title>The fourth Dubbo meetup has been held in Chengdu</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p><img src="../../img/blog/meetup-chengdu/all-hands.webp" alt="img"></p>
-<h2>The depth of the user communication</h2>
-<p>On August 26, 10:00 am - 12:00am, invited the arrival of the car to help, cloud gold, former BBD, flying fish star four companies open source enthusiasts and heavy users participate in face-to-face communication;According to the participants' feedback, answer to Dubbo many doubt, especially how to participate in the contribution to the community, as well as code contribution value point.Hope later can be more deeply involved in Dubbo communities and activities.</p>
-<h2>Meetup activity information</h2>
-<p>The event is still full, total enrollment of 976, 350 + site users, live PV 13207.</p>
-<h2>The registration information</h2>
-<p>Aliware Open Source, headquarters - Apache Dubbo developers salon on August 26 (Sunday) in chengdu high-tech zone tianfu hemicyenine rong international plaza, 200 five street on the 8th floor held the second floor conference room, technical thinking is GG feast, dry goods and welfare will not one less.</br>
-Sign up link：<a href="http://www.huodongxing.com/event/7453091088400">http://www.huodongxing.com/event/7453091088400</a></p>
-<img src="../../img/blog/dubbo-chengdu-meetup-img.jpg"/>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-chengdu.json b/en-us/blog/dubbo-meetup-chengdu.json
deleted file mode 100644
index 0870914..0000000
--- a/en-us/blog/dubbo-meetup-chengdu.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-meetup-chengdu.md",
- "__html": "<h1>The fourth Dubbo meetup has been held in Chengdu</h1>\n<p><img src=\"../../img/blog/meetup-chengdu/all-hands.webp\" alt=\"img\"></p>\n<h2>The depth of the user communication</h2>\n<p>On August 26, 10:00 am - 12:00am, invited the arrival of the car to help, cloud gold, former BBD, flying fish star four companies open source enthusiasts and heavy users participate in face-to-face communication;According to the participants' feedback, answer to Dubbo many doubt, especially [...]
- "link": "/en-us/blog/dubbo-meetup-chengdu.html",
- "meta": {
- "title": "The fourth Dubbo meetup has been held in Chengdu",
- "keywords": "Dubbo, Chengdu, meetup",
- "description": "The fourth Dubbo meetup has been held in Chengdu."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-hangzhou.html b/en-us/blog/dubbo-meetup-hangzhou.html
deleted file mode 100644
index 6325ad9..0000000
--- a/en-us/blog/dubbo-meetup-hangzhou.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Hangzhou, meetup" />
- <meta name="description" content="The fifth Dubbo meetup has been held in Hangzhou" />
- <!-- 网页标签标题 -->
- <title>The fifth Dubbo meetup has been held in Hangzhou</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The fifth Dubbo meetup has been held in Hangzhou,</p>
-<p>Please enjoy the slides of the topics:</p>
-<ul>
-<li>Ding Li: How to involve in dubbo community <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/how-to-involve-in-dubbo-community.pdf">slides</a></li>
-<li>Shenli Cao: Dubbo 2.7 introduction <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/dubbo-2.7-introduction.pdf">slides</a></li>
-<li>Tao Yang: Dubbo practice in netease koala <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/dubbo-practice-in-netease-koala.pdf">slides</a></li>
-<li>Mercy Ma: Nacos support in Dubbo <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/nacos-support-in-dubbo.pdf">slides</a></li>
-<li>Yihao Zhao: Sentinel: Sentinel support for Dubbo <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/sentinel-support-for-dubbo.pdf">slides</a></li>
-<li>Zhixuan Chen: Troubleshooting Dubbo with Arthas <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/troubleshooting-dubbo-with-arthas.pdf">slides</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-hangzhou.json b/en-us/blog/dubbo-meetup-hangzhou.json
deleted file mode 100644
index a565cdf..0000000
--- a/en-us/blog/dubbo-meetup-hangzhou.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-meetup-hangzhou.md",
- "__html": "<h1>The fifth Dubbo meetup has been held in Hangzhou</h1>\n<p>The fifth Dubbo meetup has been held in Hangzhou,</p>\n<p>Please enjoy the slides of the topics:</p>\n<ul>\n<li>Ding Li: How to involve in dubbo community <a href=\"https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/how-to-involve-in-dubbo-community.pdf\">slides</a></li>\n<li>Shenli Cao: Dubbo 2.7 introduction <a href=\"https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetu [...]
- "link": "/en-us/blog/dubbo-meetup-hangzhou.html",
- "meta": {
- "title": "The fifth Dubbo meetup has been held in Hangzhou",
- "keywords": "Dubbo, Hangzhou, meetup",
- "description": "The fifth Dubbo meetup has been held in Hangzhou"
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.html b/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.html
deleted file mode 100644
index d78cd3a..0000000
--- a/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Shanghai, meetup" />
- <meta name="description" content="The second Dubbo Shanghai meetup has been held successfully." />
- <!-- 网页标签标题 -->
- <title>The second Dubbo Shanghai meetup has been held successfully</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The sencond Dubbo meetup has successfully been held in Shanghai, over 700 people submitted registration, and over 300 were present, more than 10,000 watched the live online.</p>
-<p>Please enjoy the slides of the topics:</p>
-<ul>
-<li>Jerrick Zhu: Dubbo Status and Roadmap (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-status-and-roadmap.pdf">slides</a></li>
-<li>Mercy Ma: Dubbo Cloud Native Practices and Thoughts (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-cloud-native-practices-and-thoughts.pdf">slides</a></li>
-<li>Ping Guo: Nacos Open Source Initiative (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/nacos-open-source-initiative.pdf">slides</a></li>
-<li>Zhiwei Pan: Dubbo Practices on Internet Finance Industries (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-practices-on-internet-finance-industries.pdf">slides</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.json b/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.json
deleted file mode 100644
index 589c0d8..0000000
--- a/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-meetup-shanghai-jun-23rd-2018.md",
- "__html": "<h2>The second Dubbo Shanghai meetup has been held successfully</h2>\n<p>The sencond Dubbo meetup has successfully been held in Shanghai, over 700 people submitted registration, and over 300 were present, more than 10,000 watched the live online.</p>\n<p>Please enjoy the slides of the topics:</p>\n<ul>\n<li>Jerrick Zhu: Dubbo Status and Roadmap (Chinese) <a href=\"https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-status-and-roadmap.pdf\ [...]
- "link": "/en-us/blog/dubbo-meetup-shanghai-jun-23rd-2018.html",
- "meta": {
- "title": "The second Dubbo Shanghai meetup has been held successfully",
- "keywords": "Dubbo, Shanghai, meetup",
- "description": "The second Dubbo Shanghai meetup has been held successfully."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-shenzhen.html b/en-us/blog/dubbo-meetup-shenzhen.html
deleted file mode 100644
index 1bac9bb..0000000
--- a/en-us/blog/dubbo-meetup-shenzhen.html
+++ /dev/null
@@ -1,40 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Shenzhen, meetup" />
- <meta name="description" content="The third Dubbo meetup has been held in Shenzhen" />
- <!-- 网页标签标题 -->
- <title>The third Dubbo meetup has been held in Shenzhen</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The third Dubbo meetup has successfully been held in Shenzhen, over 2000 people submitted registration, and over 700 were present, more than 17,000 watched the live online.</p>
-<p>Please enjoy the slides of the topics:</p>
-<ul>
-<li>Zhixuan Chen: Dubbo-present-and-2.7-update (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/dubbo-present-and-2.7-update.pdf">slides</a></li>
-<li>Bin Kang: Microservice-in-lexinfintech (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/microservice-in-lexinfintech.pdf">slides</a></li>
-<li>Jialiang lin: sentinel (Chinese) <a href="https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/sentinel.pdf">slides</a></li>
-</ul>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-meetup-shenzhen.json b/en-us/blog/dubbo-meetup-shenzhen.json
deleted file mode 100644
index 976bc67..0000000
--- a/en-us/blog/dubbo-meetup-shenzhen.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-meetup-shenzhen.md",
- "__html": "<h2>The third Dubbo meetup has been held in Shenzhen</h2>\n<p>The third Dubbo meetup has successfully been held in Shenzhen, over 2000 people submitted registration, and over 700 were present, more than 17,000 watched the live online.</p>\n<p>Please enjoy the slides of the topics:</p>\n<ul>\n<li>Zhixuan Chen: Dubbo-present-and-2.7-update (Chinese) <a href=\"https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/dubbo-present-and-2.7-update.pdf\">s [...]
- "link": "/en-us/blog/dubbo-meetup-shenzhen.html",
- "meta": {
- "title": "The third Dubbo meetup has been held in Shenzhen",
- "keywords": "Dubbo, Shenzhen, meetup",
- "description": "The third Dubbo meetup has been held in Shenzhen"
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-new-async.html b/en-us/blog/dubbo-new-async.html
deleted file mode 100644
index bab522c..0000000
--- a/en-us/blog/dubbo-new-async.html
+++ /dev/null
@@ -1,416 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, asynchronous, async chain" />
- <meta name="description" content="This article recalls how asynchronous call is implemented in Dubbo 2.6.x, and introduces the new way based on CompletableFuture in 2.7.0." />
- <!-- 网页标签标题 -->
- <title>How to implement a fully asynchronous calls chain based on Dubbo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>Implementing the full asynchronous programming based on Dubbo, which is a new feature introduced in version 2.7.0 after the enhancement of the existing asynchronous mode.This article first reviews the supported functions and existing problems of asynchronization in 2.6.x and earlier versions, and introduces the targeted enhancements based on CompletableFuture in version 2.7.0. Then, the use of enhanced asynchronous programming is elaborated through several examples. Finally, it summar [...]
-<h2>Asynchronous mode before version 2.6.x</h2>
-<p>Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including <a href="http://dubbo.apache.org/zh-cn/docs/user/demos/async-call.html">Asynchronous Call</a>, <a href="http://dubbo.apache.org/zh-cn/docs/user/demos/callback-parameter.html">Parameter Callback</a> and <a href="http://dubbo.apache.org/zh-cn/docs/user/demos/events-notify.html">Event Notification</a> on Consumer side. There are some brief introductions to the usage and Demo in the above do [...]
-<p>But the current asynchronous method has the following problems:</p>
-<ul>
-<li>Methods to access Future object are not direct enough.</li>
-<li>Future interface cannot implement automatic callback. Customized ResponseFuture class could implement callback, however it only supports limited asynchronous scenes. For example, it does not support mutual coordination or combination between Future objects.</li>
-<li>Asynchronization on Provider side is not supported.</li>
-</ul>
-<p>Take the asynchronous method of Consumer side as an example:</p>
-<ol>
-<li>Define a original synchronous interface and add the declaration to support asynchronous calls.</li>
-</ol>
-<pre><code>public interface FooService {
- String findFoo(String name);
-}
-</code></pre>
-<pre><code><dubbo:reference id="fooService" interface="com.alibaba.foo.FooService">
- <dubbo:method name="findFoo" async="true" />
-</dubbo:reference>
-</code></pre>
-<ol start="2">
-<li>Obtain Future object through RpcContext.</li>
-</ol>
-<pre><code>// this call will return null immediately
-fooService.findFoo(fooId);
-// Obtain the Future instance. When the result is returned, Future instance will be notified and the result will be set to Future instance.
-Future<Foo> fooFuture = RpcContext.getContext().getFuture();
-fooFuture.get();
-</code></pre>
-<p>or</p>
-<pre><code>// this call will return null immediately
-fooService.findFoo(fooId);
-// get Dubbo's built-in ResponseFuture, and set the callback
-ResponseFuture future = ((FutureAdapter)RpcContext.getContext().getFuture()).getFuture();
-future.setCallback(new ResponseCallback() {
- @Override
- public void done(Object response) {
- System.out.print(response);
- }
-
- @Override
- public void caught(Throwable exception) {
- exception.printStackTrace();
- }
-});
-</code></pre>
-<p>From this simple example, we can see there are some inconveniences in use:</p>
-<ol>
-<li>The synchronization interface of findFoo cannot directly return a Future object representing the asynchronous result, which is further obtained through RpcContext.</li>
-<li>Future object can only be obtained from get method that will block until getting the result.</li>
-<li>Callback can be set by getting the built-in ResponseFuture interface. However, the API to obtain ResponseFuture is not convenient enough to support other asynchronous scenes except callback. For example, it does not support the scene where multiple Future objects work together.</li>
-</ol>
-<h2>Enhancement based on CompletableFuture in version 2.7.0</h2>
-<p>People who understand the evolution history of Future in Java should know that the Future used in Dubbo 2.6.x and earlier versions is introduced in Java 5, so there are some problems in function design.The CompletableFuture introduced in Java 8 further enriches the Future interface and solves these problems well.</p>
-<p>Support for Java 8 has been upgraded in Dubbo 2.7.0, and Dubbo has enhanced the current asynchronous functionality based on CompletableFuture.</p>
-<ol>
-<li>
-<p>Now it supports direct definition of service interfaces that return CompletableFuture. Through these interfaces, we can implement asynchronous programming on both Consumer side and Provider side more naturally.</p>
-<pre><code>public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
-}
-</code></pre>
-</li>
-<li>
-<p>If you don't want to define the return value of the interface as a Future object, or if there is a defined synchronization interface, you can additionally define an asynchronous interface and provide a method to return a Future object.</p>
-<pre><code>public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
-}
-</code></pre>
-<pre><code>@AsyncFor(AsyncService.class)
-public interface GrettingServiceAsync extends GreetingsService {
- CompletableFuture<String> sayHiAsync(String name);
-}
-</code></pre>
-<p>In this way, Provider can only implement the sayHi method. The Consumer can get a Future instance by directly calling sayHiAsync, and Dubbo framework will convert it to a call to the sayHi method on the Provider side automatically.</p>
-<p>Providing an asynchronous method definition for each synchronization method can be inconvenient. Further, using <a href="https://github.com/dubbo/dubbo-async-processor">Annotation Processor implementation</a> in the Dubbo ecosystem can automatically generate asynchronous method definitions for us.</p>
-</li>
-<li>
-<p>Similarly, if your original interface definition doesn't return a Future object, the Provider side also provides a programming interface similar to the Async Servlet in Servlet 3.0 to support asynchronization : <code>RpcContext.startAsync()</code>.</p>
-<pre><code>public interface AsyncService {
- String sayHello(String name);
-}
-</code></pre>
-<pre><code>public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
-}
-</code></pre>
-<p>At the beginning of the method body, it starts asynchronization by running <code>RpcContext.startAsync()</code> , and it starts a new thread to execute the business logic asynchronously. After the time-consuming operation is completed, the result is written back by <code>asyncContext.write</code>.</p>
-</li>
-<li>
-<p>RpcContext returns CompletableFuture directly.</p>
-<pre><code>CompletableFuture<String> f = RpcContext.getContext().getCompletableFuture();
-</code></pre>
-</li>
-</ol>
-<p>All of the above enhancements are based on the compatibility with existing asynchronous programming, so asynchronous programs written based on 2.6.x versions can be successfully compiled without any modification.</p>
-<p>Next, let's illustrate how to implement a fully asynchronous Dubbo service call chain through a few examples.</p>
-<h2>example 1：CompletableFuture interface</h2>
-<p>CompletableFuture interface can be used both for a synchronous call and for an asynchronous call on Consumer or Provider side. This example implements asynchronous calls between Consumer and Provider sides. Code link <a href="https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-original-future">dubbo-samples-async-original-future</a>.</p>
-<ol>
-<li>
-<p>Interface definition</p>
-<pre><code>public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
-}
-</code></pre>
-<p>Note that the return type of this interface is <code>CompletableFuture<String></code>.</p>
-</li>
-<li>
-<p>Provider Side</p>
-<ul>
-<li>
-<p>Implementation</p>
-<pre><code>public class AsyncServiceImpl implements AsyncService {
- public CompletableFuture<String> sayHello(String name) {
- return CompletableFuture.supplyAsync(() -> {
- try {
- Thread.sleep(5000);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- return "async response from provider.";
- });
- }
-}
-</code></pre>
-<p>We can see that the business code is switched to be executed in the new thread by supplyAsync, so the Provider side is asynchronous.</p>
-</li>
-<li>
-<p>Config</p>
-<pre><code><bean id="asyncService" class="com.alibaba.dubbo.samples.async.impl.AsyncServiceImpl"/>
-<dubbo:service interface="com.alibaba.dubbo.samples.async.api.AsyncService" ref="asyncService"/>
-</code></pre>
-<p>The Config is the same as the original interface.</p>
-</li>
-</ul>
-</li>
-<li>
-<p>Consumer Side</p>
-<ul>
-<li>Config</li>
-</ul>
-<pre><code><dubbo:reference id="asyncService" timeout="10000" interface="com.alibaba.dubbo.samples.async.api.AsyncService"/>
-</code></pre>
-<p> The Config is the same as the original interface.</p>
-<ul>
-<li>Call remote service</li>
-</ul>
-<pre><code>public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
- final AsyncService asyncService = (AsyncService) context.getBean("asyncService");
-
- CompletableFuture<String> future = asyncService.sayHello("async call request");
- future.whenComplete((v, t) -> {
- if (t != null) {
- t.printStackTrace();
- } else {
- System.out.println("Response: " + v);
- }
- });
- System.out.println("Executed before response return.");
- System.in.read();
- }
-</code></pre>
-<p><code>CompletableFuture<String> future = asyncService.sayHello("async call request");</code>It is convenient to return the Future instance, which implements the asynchronous service call on the Consumer side.</p>
-</li>
-</ol>
-<h2>Example 2：Synchronous interface uses Annotation Processor</h2>
-<p>This example demonstrates how to implement the Consumer-side asynchronous service call using the Annotation Processor based on the original synchronous interface. Code link <a href="https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-generated-future">dubbo-samples-async-generated-future</a>.</p>
-<ol>
-<li>
-<p>Interface definition</p>
-<pre><code>@DubboAsync
-public interface GreetingsService {
- String sayHi(String name);
-}
-</code></pre>
-<p>This is a generic definition of the Dubbo service interface. Note that add the @DubboAsync annotation when using Annotation Processor.</p>
-<pre><code><dependency>
- <groupId>com.alibaba</groupId>
- <artifactId>dubbo-async-processer</artifactId>
- <version>1.0.0-SNAPSHOT</version>
-</dependency>
-<plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-compiler-plugin</artifactId>
- <version>3.7.0</version>
- <configuration>
- <source>1.8</source>
- <target>1.8</target>
- <annotationProcessorPaths>
- <path>
- <groupId>com.alibaba</groupId>
- <artifactId>dubbo-async-processer</artifactId>
- <version>1.0.0-SNAPSHOT</version>
- </path>
- </annotationProcessorPaths>
- </configuration>
-</plugin>
-</code></pre>
-<p>The above config is the Maven dependency that imports dubbo-async-processer processor. Developers who define interfaces (providing APIs) usually add the above dependencies to the project, so that when doing API packaging, the following interface definitions will be automatically generated in APIs:</p>
-<pre><code>/**
-* Generated by dubbo-async-processer
-*/
-package com.alibaba.dubbo.samples.api;
-import java.util.concurrent.CompletableFuture;
-@javax.annotation.Generated("com.alibaba.dubbo.async.processor.AsyncAnnotationProcessor")
-@org.apache.dubbo.common.config.AsyncFor(com.alibaba.dubbo.samples.api.GreetingsService.class)
-public interface GreetingsServiceAsync extends GreetingsService {
-CompletableFuture<java.lang.String> sayHiAsync(java.lang.String name);
-}
-</code></pre>
-</li>
-<li>
-<p>Provider side</p>
-<ul>
-<li>Config</li>
-</ul>
-<pre><code><bean id="greetingsService" class="com.alibaba.dubbo.samples.async.impl.GreetingsServiceImpl"/>
-<dubbo:service interface="com.alibaba.dubbo.samples.api.GreetingsService" ref="greetingsService"/>
-</code></pre>
-<ul>
-<li>Service implementation</li>
-</ul>
-<pre><code>public class GreetingsServiceImpl implements GreetingsService {
- @Override
- public String sayHi(String name) {
- return "hi, " + name;
- }
-}
-</code></pre>
-</li>
-<li>
-<p>Consumer side</p>
-<ul>
-<li>Config</li>
-</ul>
-<pre><code> <dubbo:reference id="greetingsService" interface="com.alibaba.dubbo.samples.api.GreetingsServiceAsync"/>
-</code></pre>
-<p>Note that the service interface uses <strong>GreetingsServiceAsync</strong></p>
-<ul>
-<li>Service call</li>
-</ul>
-<pre><code> public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
-
- GreetingsServiceAsync greetingsService = (GreetingsServiceAsync) context.getBean("greetingsService");
- CompletableFuture<String> future = greetingsService.sayHiAsync("async call reqeust");
- System.out.println("async call ret :" + future.get());
-
- System.in.read();
- }
-</code></pre>
-<p>In this way, we can use <code>CompletableFuture<String> future = greetingsService.sayHiAsync("async call reqeust");</code> directly，and return CompletableFuture.</p>
-</li>
-</ol>
-<h2>Example 3：Use AsyncContext</h2>
-<p>This example demonstrates how to implement the Provider-side asynchronous execution through AsyncContext based on the original synchronous interface. Code link <a href="https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-provider">dubbo-samples-async-provider</a>.</p>
-<ol>
-<li>
-<p>Interface definition</p>
-<pre><code>public interface AsyncService {
- String sayHello(String name);
-}
-</code></pre>
-</li>
-<li>
-<p>Provider side</p>
-<ul>
-<li>Config</li>
-</ul>
-<pre><code><bean id="asyncService" class="com.alibaba.dubbo.samples.async.impl.AsyncServiceImpl"/>
-<dubbo:service async="true" interface="com.alibaba.dubbo.samples.async.api.AsyncService" ref="asyncService"/>
-</code></pre>
-<p>Note that adding <code>async="true"</code> indicates that this is a service that starts the Provider-side execution asynchronously.</p>
-<ul>
-<li>Asynchronous execution implementation</li>
-</ul>
-<pre><code>public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.signalContextSwitch();
- try {
- Thread.sleep(500);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
-}
-</code></pre>
-</li>
-<li>
-<p>Consumer side</p>
-<ul>
-<li>Config</li>
-</ul>
-<pre><code><dubbo:reference id="asyncService" interface="com.alibaba.dubbo.samples.async.api.AsyncService"/>
-</code></pre>
-<ul>
-<li>Service call</li>
-</ul>
-<pre><code> public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
-
- AsyncService asyncService = (AsyncService) context.getBean("asyncService");
- System.out.println(asyncService.sayHello("async call request"));
-
- System.in.read();
- }
-</code></pre>
-</li>
-</ol>
-<h2>New problems resulted from asynchronization</h2>
-<h3>Filter Chain</h3>
-<p>The following is a complete Filter chain for a normal Dubbo call.</p>
-<p>After using the asynchronous call, since the asynchronous result is executed separately in the asynchronous thread, the Result passed through the second half of the Filter chain is null, and the real result cannot be processed by the Filter chain when it is returned.</p>
-<p>In order to solve this problem, PostProcessFilter and AbstractPostProcessFilter were introduced in Dubbo 2.7.0. The PostProcessFilter interface extends from the Filter interface, and AbstractPostProcessFilter is an abstract implementation of PostProcessFilter.</p>
-<p>The following is an example of extending the Filter and supporting the asynchronous Filter chain.</p>
-<pre><code>@Activate(group = {Constants.PROVIDER, Constants.CONSUMER})
-public class AsyncPostprocessFilter extends AbstractPostProcessFilter {
-
- @Override
- public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
- return postProcessResult(invoker.invoke(invocation), invoker, invocation);
- }
-
- @Override
- protected Result doPostProcess(Result result, Invoker<?> invoker, Invocation invocation) {
- System.out.println("Filter get the return value: " + result.getValue());
- return result;
- }
-}
-</code></pre>
-<h3>Context passing</h3>
-<p>Currently, the context we are considering mainly refers to the data stored in the RpcContext. In most scenarios, the user needs to complete the passing of the Context before switching the service thread.</p>
-<pre><code>public class AsyncServiceImpl implements AsyncService {
- // Save the context of the current thread
- RpcContext context = RpcContext.getContext();
- public CompletableFuture<String> sayHello(String name) {
- return CompletableFuture.supplyAsync(() -> {
- // Set context into new thread
- RpcContext.setContext(context);
- try {
- Thread.sleep(5000);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- return "async response from provider.";
- });
- }
-}
-</code></pre>
-<p>However, AsyncContext also provides the signalContextSwitch() method for a convenient Context switch.</p>
-<pre><code>public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.signalContextSwitch();
- try {
- Thread.sleep(500);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
-}
-</code></pre>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-new-async.json b/en-us/blog/dubbo-new-async.json
deleted file mode 100644
index a860f7a..0000000
--- a/en-us/blog/dubbo-new-async.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-new-async.md",
- "__html": "<h1>How to implement a fully asynchronous calls chain based on Dubbo</h1>\n<p>Implementing the full asynchronous programming based on Dubbo, which is a new feature introduced in version 2.7.0 after the enhancement of the existing asynchronous mode.This article first reviews the supported functions and existing problems of asynchronization in 2.6.x and earlier versions, and introduces the targeted enhancements based on CompletableFuture in version 2.7.0. Then, the use of enha [...]
- "link": "/en-us/blog/dubbo-new-async.html",
- "meta": {
- "title": "How to implement a fully asynchronous calls chain based on Dubbo",
- "keywords": "Dubbo, asynchronous, async chain",
- "description": "This article recalls how asynchronous call is implemented in Dubbo 2.6.x, and introduces the new way based on CompletableFuture in 2.7.0."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo-zk.html b/en-us/blog/dubbo-zk.html
deleted file mode 100644
index 33eb2dd..0000000
--- a/en-us/blog/dubbo-zk.html
+++ /dev/null
@@ -1,278 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, registry center, Zookeeper, ZK" />
- <meta name="description" content="This article introduces basic concepts of Zookeeper, and how to use Zookeeper as a registry center." />
- <!-- 网页标签标题 -->
- <title>Using Zookeeper in Dubbo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Introduction of Zookeeper</h2>
-<h3>The basic concept</h3>
-<p>In the mordern distrbuted applications, there are multiple coordination problems between nodes and nodes, including: leader election, group service, locking, configuration management, naming and synchronization. Apache Zookeeper, as its name implied, is a distributed, open-source coordination service framwork to address these demand.</p>
-<p>In order to ensure the high performance, highly available and strictly ordered access, the performance aspects of ZooKeeper means it can be used in large, distributed systems and can also be deployed in cluster mode, which called 'ZooKeeper ensemble'. In ZooKeeper ensemble, all write requests from clients are forwarded to a single server, called the leader, through the ZAB(Zookeeper Atomic Broadcast Protocol) to make sure the message in each nodes are same. Clients can access any one [...]
-<p><img src="../../img/blog/zk-emsemble.png" alt="Diagram shows client-server architecture of ZooKeeper">
-<em>Image Credit : ebook -Zookeeper-Distributed Process Coordination from O'Reilly</em></p>
-<p>The method to store the data in Zookeeper is similar as the standard UNIX file system, as a data model styled after the familiar directory tree structure of file systems. When we talking about ZooKeeper data nodes, we call it Znodes to clarify it.</p>
-<p><img src="../../img/blog/zk-tree.png" alt="zk-tree">
-<em>Image Credit : ebook -Zookeeper-Distributed Process Coordination from O'Reilly</em></p>
-<h3>Basic Implementation</h3>
-<p>You could donwload and install Zookeeper directly<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup>.
-Or you could use Homebrew <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup> <code>brew install zookeeper</code> to install Zookeeper in Mac OS.
-Considering the versatility, we run the Zookeeper by using docker in this blog. If you have not installed the docker yet, please prepare the docker environment first. <sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup></p>
-<h4>1. Running the Zookeeper</h4>
-<p>Execute the command to run zookeeper in a docker container</p>
-<pre><code class="language-shell">docker run --rm --name zookeeper -p 2181:2181 zookeeper
-</code></pre>
-<h4>2. Entering the zookeeper container</h4>
-<pre><code class="language-shell">docker exec -it zookeeper bash
-</code></pre>
-<p>In the <code>bin</code> directory, there is a command to start zookeeper <code>zkServer</code> and the Management Console <code>zkCli</code></p>
-<pre><code class="language-shell">bash-4.4# ls -l bin
-total 36
--rwxr-xr-x 1 zookeepe zookeepe 232 Mar 27 04:32 README.txt
--rwxr-xr-x 1 zookeepe zookeepe 1937 Mar 27 04:32 zkCleanup.sh
--rwxr-xr-x 1 zookeepe zookeepe 1056 Mar 27 04:32 zkCli.cmd
--rwxr-xr-x 1 zookeepe zookeepe 1534 Mar 27 04:32 zkCli.sh
--rwxr-xr-x 1 zookeepe zookeepe 1759 Mar 27 04:32 zkEnv.cmd
--rwxr-xr-x 1 zookeepe zookeepe 2696 Mar 27 04:32 zkEnv.sh
--rwxr-xr-x 1 zookeepe zookeepe 1089 Mar 27 04:32 zkServer.cmd
--rwxr-xr-x 1 zookeepe zookeepe 6773 Mar 27 04:32 zkServer.sh
-</code></pre>
-<h4>3. Entering the zookeeper management interface via zkCli</h4>
-<p>Since it was started through docker, the process of Zookeeper has been started and will provide the services to the public via port 2181.</p>
-<pre><code class="language-shell">bash-4.4# ps
-PID USER TIME COMMAND
- 1 zookeepe 0:02 /usr/lib/jvm/java-1.8-openjdk/jre/bin/java -Dzookeeper.log.dir=. -Dzookeeper.root
- 32 root 0:00 bash
- 42 root 0:00 ps
-</code></pre>
-<p>So, it allows you to access Zookeeper's console directly through <code>zkCli</code> for management.</p>
-<pre><code class="language-shell">bash-4.4# bin/zkCli.sh -server 127.0.0.1:2181
-Connecting to 127.0.0.1:2181
-...
-WATCHER::
-
-WatchedEvent state:SyncConnected type:None path:null
-
-[zk: 127.0.0.1:2181(CONNECTED) 0] help
-ZooKeeper -server host:port cmd args
- stat path [watch]
- set path data [version]
- ls path [watch]
- delquota [-n|-b] path
- ls2 path [watch]
- setAcl path acl
- setquota -n|-b val path
- history
- redo cmdno
- printwatches on|off
- delete path [version]
- sync path
- listquota path
- rmr path
- get path [watch]
- create [-s] [-e] path data acl
- addauth scheme auth
- quit
- getAcl path
- close
- connect host:port
-</code></pre>
-<h4>4. Basic Examples on zkCli</h4>
-<p>Create <code>/hello-zone</code> node:</p>
-<pre><code class="language-shell">[zk: 127.0.0.1:2181(CONNECTED) 19] create /hello-zone 'world'
-Created /hello-zone
-</code></pre>
-<p>List the child nodes under <code>/</code> and confirm that <code>hello-zone</code> is created:</p>
-<pre><code class="language-shell">[zk: 127.0.0.1:2181(CONNECTED) 20] ls /
-[zookeeper, hello-zone]
-</code></pre>
-<p>List the child nodes for <code>/hello-zone</code> and verify that it is empty:</p>
-<pre><code class="language-shell">[zk: 127.0.0.1:2181(CONNECTED) 21] ls /hello-zone
-[]
-</code></pre>
-<p>Get the data stored on the <code>/hello-zone</code> node:</p>
-<pre><code class="language-shell">[zk: 127.0.0.1:2181(CONNECTED) 22] get /hello-zone
-world
-</code></pre>
-<h2>Using Zookeeper in Dubbo</h2>
-<p>Zookeeper is used for service registration discovery and configuration management in Dubbo, and the structure of data in Zookeeper is shown in the following figure:</p>
-<p><img src="../../img/blog/dubbo-in-zk.jpg" alt="dubbo-in-zk"></p>
-<p>First, all data related to Dubbo is organized under the root node of <code>/duboo</code>.</p>
-<p>The secondary directory is the service name like <code>com.foo.BarService</code>.</p>
-<p>The three-level directory has two child nodes, <code>providers</code> and <code>consumers</code>, representing the supplier and customers of the service.</p>
-<p>The URL information for each application instance associated with the service will be recorded by the Level 4 directory. The <code>providers</code> and <code>consumer</code> will stored the providers information and the consumers information of the services seperately.<br>
-For example, the service provider of <code>com.foo.BarService</code> will register its URL Information to <code>/dubbo/com.foo.BarService/providers</code>; Similarly, service consumers will register their information under the corresponding <code>consumer</code> node. At the same time, consumers will subscribe to the corresponding <code>providers</code> node to be able to detect the changes of the service provider address list.</p>
-<h3>Prepare the sample code</h3>
-<p>The code in this document can be found in <a href="https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-zookeeper">https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-zookeeper</a>.</p>
-<h4>1. Interface definition</h4>
-<p>Define a simple <code>greetingservice</code> interface with only one simple method named <code>sayHello</code> to greet to the caller.</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">GreetingService</span> </span>{
- <span class="hljs-function">String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span></span>;
-}
-</code></pre>
-<h4>2. Server: Implementation</h4>
-<p>Implement the <code>GreetingService</code> interface and mark it as a service for Dubbo via <code>@Service</code>.</p>
-<pre><code class="language-java"><span class="hljs-meta">@Service</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">AnnotatedGreetingService</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">GreetingService</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> <span class="hljs-string">"hello, "</span> + name;
- }
-}
-</code></pre>
-<h4>3. Server: Assembly</h4>
-<p>Define ProviderConfiguration to assemble Dubbo services.</p>
-<pre><code class="language-java"><span class="hljs-meta">@Configuration</span>
-<span class="hljs-meta">@EnableDubbo</span>(scanBasePackages = <span class="hljs-string">"com.alibaba.dubbo.samples.impl"</span>)
-<span class="hljs-meta">@PropertySource</span>(<span class="hljs-string">"classpath:/spring/dubbo-provider.properties"</span>)
-<span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ProviderConfiguration</span> </span>{}
-</code></pre>
-<p>Dubbo-provider.properties is an external configuration in a spring application, as follows:</p>
-<pre><code class="language-properties"><span class="hljs-meta">dubbo.application.name</span>=<span class="hljs-string">demo-provider</span>
-<span class="hljs-meta">dubbo.registry.address</span>=<span class="hljs-string">zookeeper://$DOCKER_HOST:2181</span>
-<span class="hljs-meta">dubbo.protocol.name</span>=<span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.port</span>=<span class="hljs-string">20880</span>
-</code></pre>
-<p>Since zookeeper runs in a docker container, please be noted that:</p>
-<ul>
-<li>We assumes that Dubbo applications is running on the host machine (outside the docker container) in this document, and needs to replace the PATH of Zookeeper with the IP address of the Environment Variable <em>${DOCKER_HOST}</em>. Please find more detail in the official Docker documentation.</li>
-<li>When the Dubbo application is a docker application, the container's name is equivalent to Zookeeper's. The container's name is ** zookeeper ** in this document.</li>
-<li>Of course, if you don't want to run the Zookeeper in a container mode, just simply replace <em>$DOCKER_HOST</em> with <strong>localhost</strong>.</li>
-</ul>
-<h4>4. Server: Starting Service</h4>
-<p>In the <code>main</code> method, you could provide the Dubbo service by running a Spring Context.</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ProviderBootstrap</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> <span class="hljs-keyword">throws</span> Exception </span>{
- AnnotationConfigApplicationContext context = <span class="hljs-keyword">new</span> AnnotationConfigApplicationContext(ProviderConfiguration.class);
- context.start();
- System.in.read();
- }
-}
-</code></pre>
-<p>Start the <code>main</code> method of server, you will get the following output, which represents the success of the server's startup, and the <code>GreetingService</code> service is registered on the ZookeeperRegistry:</p>
-<pre><code class="language-sh">[03/08/18 10:50:33:033 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=<span class="hljs-literal">true</span>&application=demo-provider&dubbo=2.6.2&generic=<span class="hljs-literal">false</span>&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=12938&side=provider&timestamp=1533264631849, dubbo version: [...]
-</code></pre>
-<p>You could find the registration information of the service provider through the Zookeeper management terminal:</p>
-<pre><code class="language-sh">$ docker <span class="hljs-built_in">exec</span> -it zookeeper bash
-bash-4.4<span class="hljs-comment"># bin/zkCli.sh -server localhost:218</span>
-Connecting to localhost:2181
-...
-Welcome to ZooKeeper!
-JLine support is enabled
-...
-[zk: localhost:2181(CONNECTED) 0] ls /dubbo/com.alibaba.dubbo.samples.api.GreetingService/providers
-[dubbo%3A%2F%2F192.168.99.1%3A20880%2Fcom.alibaba.dubbo.samples.api.GreetingService%3Fanyhost%3Dtrue%26application%3Ddemo-provider%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dcom.alibaba.dubbo.samples.api.GreetingService%26methods%3DsayHello%26pid%3D12938%26side%3Dprovider%26timestamp%3D1533264631849]
-</code></pre>
-<p>You could find that the Dubbo services just registered its URL address at the <code>providers</code> node as follows:
-<em>dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=true&application=demo-provider&dubbo=2.6.2&generic=false&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=12938&side=provider&timestamp=1533264631849</em></p>
-<h4>5. Client: Reference Service</h4>
-<p>You could declare the reference service by @Reference, while it will generate a full call. The target address of the service could be queried by the Zookeeper's <code>provider</code> node.</p>
-<pre><code class="language-java"><span class="hljs-meta">@Component</span>(<span class="hljs-string">"annotatedConsumer"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">GreetingServiceConsumer</span> </span>{
- <span class="hljs-meta">@Reference</span>
- <span class="hljs-keyword">private</span> GreetingService greetingService;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">doSayHello</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-keyword">return</span> greetingService.sayHello(name);
- }
-}
-</code></pre>
-<h4>6. Client: Assembling</h4>
-<p>Define the ConsumerConfiguration to assemble Dubbo service.</p>
-<pre><code class="language-java"><span class="hljs-meta">@Configuration</span>
-<span class="hljs-meta">@EnableDubbo</span>(scanBasePackages = <span class="hljs-string">"com.alibaba.dubbo.samples.action"</span>)
-<span class="hljs-meta">@PropertySource</span>(<span class="hljs-string">"classpath:/spring/dubbo-consumer.properties"</span>)
-<span class="hljs-meta">@ComponentScan</span>(value = {<span class="hljs-string">"com.alibaba.dubbo.samples.action"</span>})
-<span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ConsumerConfiguration</span> </span>{}
-</code></pre>
-<p>"dubbo-consumer.properties" is a method of external configuration in a Spring application, as follows:</p>
-<pre><code class="language-properties"><span class="hljs-meta">dubbo.application.name</span>=<span class="hljs-string">demo-consumer</span>
-<span class="hljs-meta">dubbo.registry.address</span>=<span class="hljs-string">zookeeper://$DOCKER_HOST:2181</span>
-<span class="hljs-meta">dubbo.consumer.timeout</span>=<span class="hljs-string">3000</span>
-</code></pre>
-<p>Same as <strong>3. Server: Assembling</strong>, You need to modify <em>$DOCKER_HOST</em> defined in <em>dubbo.registry.address</em> according to your own environment. You could find more instructions in step 3.</p>
-<h4>7. Client: Initiating A Remote Call</h4>
-<p>Run <code>main</code> to initiate a remote call from a existed service provider. Dubbo first subscribes to the zookeeper service address and then selects one from the list of returned addresses to invoke the client:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ConsumerBootstrap</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ConsumerBootstrap</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> <span class="hljs-keyword">throws</span> IOException </span>{
- AnnotationConfigApplicationContext context = <span class="hljs-keyword">new</span> AnnotationConfigApplicationContext(ConsumerConfiguration.class);
- context.start();
- GreetingServiceConsumer greetingServiceConsumer = context.getBean(GreetingServiceConsumer.class);
- String hello = greetingServiceConsumer.doSayHello(<span class="hljs-string">"zookeeper"</span>);
- System.out.println(<span class="hljs-string">"result: "</span> + hello);
- System.in.read();
- }
-}
-</code></pre>
-<p>The output are as follows:</p>
-<pre><code class="language-shell">[03/08/18 01:42:31:031 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=consumers&check=false&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer&timestamp=1533274951195, dubbo version: 2.6.2, current host: 192.168.99.1 #1
-[03/08/18 01:42:31:031 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Subscribe: consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=providers,configurators,routers&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer&timestamp=1533274951195, dubbo version: 2.6.2, current host: 192.168.99.1 #2
-...
-result: hello, zookeeper
-</code></pre>
-<p>Description:</p>
-<ol>
-<li><strong>Register</strong>: consumer://192.168.99.1/...&<strong>category=consumers</strong>&： In Zookeeper, consumers could register their information and store it at the <code>consumers</code> node</li>
-<li><strong>Subscribe</strong>: consumer://192.168.99.1/...&<strong>category=providers,configurators,routers</strong>&：Consumers subscribe <code>providers</code>, <code>configurators</code>, <code>routers</code> from Zookeepers. The <code>configurations</code> is related to the Dubbo configuration, and <code>routers</code> is related to routing rules. The providers node subscription should be noted. When a new service provider to join, due to the relationship between the subscrip [...]
-</ol>
-<p>You could find the registration information of the service provider through the Zookeeper management terminal:</p>
-<pre><code class="language-sh">$ docker <span class="hljs-built_in">exec</span> -it zookeeper bash
-bash-4.4<span class="hljs-comment"># bin/zkCli.sh -server localhost:218</span>
-Connecting to localhost:2181
-...
-Welcome to ZooKeeper!
-JLine support is enabled
-...
-[zk: localhost:2181(CONNECTED) 4] ls /dubbo/com.alibaba.dubbo.samples.api.GreetingService/consumers
-[consumer%3A%2F%2F192.168.99.1%2Fcom.alibaba.dubbo.samples.api.GreetingService%3Fapplication%3Ddemo-consumer%26category%3Dconsumers%26check%3Dfalse%26default.timeout%3D3000%26dubbo%3D2.6.2%26interface%3Dcom.alibaba.dubbo.samples.api.GreetingService%26methods%3DsayHello%26pid%3D82406%26side%3Dconsumer%26timestamp%3D1533274951195]
-</code></pre>
-<p>You could see that consumers of Dubbo's servicehas registered its URL address at the <code>consumers</code> node:</p>
-<p><em>consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=providers,configurators,routers&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer&timestamp=1533274951195</em></p>
-<h2>Summary</h2>
-<p>This document focuses on how to use ZooKeeper as a registry in Dubbo. This document also mentioned that the Zookeeper could be a configuration center and a service management in Dubbo. Zookeeper is a single-node, standalone mode. However, developers always bulid a Zookeeper server cluster called * Zookeeper ensemble * in the real world.</p>
-<p>Through this document, readers can learn:</p>
-<ul>
-<li>Basic concepts and applications of ZooKeeper</li>
-<li>The function of Zookeeper in Dubbo application</li>
-<li>Learn about Zookeeper's interaction through practical sample codes</li>
-<li>The storage of service registration and consumption information of Dubbo with ZooKeeper</li>
-</ul>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p><a href="https://www.apache.org/dyn/closer.cgi/zookeeper/">https://www.apache.org/dyn/closer.cgi/zookeeper/</a> <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn2" class="footnote-item"><p><a href="https://brew.sh">https://brew.sh</a> <a href="#fnref2" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn3" class="footnote-item"><p><a href="https://www.docker.com/community-edition">https://www.docker.com/community-edition</a> <a href="#fnref3" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo-zk.json b/en-us/blog/dubbo-zk.json
deleted file mode 100644
index bbbd96c..0000000
--- a/en-us/blog/dubbo-zk.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo-zk.md",
- "__html": "<h1>Using Zookeeper in Dubbo</h1>\n<h2>Introduction of Zookeeper</h2>\n<h3>The basic concept</h3>\n<p>In the mordern distrbuted applications, there are multiple coordination problems between nodes and nodes, including: leader election, group service, locking, configuration management, naming and synchronization. Apache Zookeeper, as its name implied, is a distributed, open-source coordination service framwork to address these demand.</p>\n<p>In order to ensure the high perfo [...]
- "link": "/en-us/blog/dubbo-zk.html",
- "meta": {
- "title": "Using Zookeeper in Dubbo",
- "keywords": "Dubbo, registry center, Zookeeper, ZK",
- "description": "This article introduces basic concepts of Zookeeper, and how to use Zookeeper as a registry center."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/dubbo2-js.html b/en-us/blog/dubbo2-js.html
deleted file mode 100644
index d341ef8..0000000
--- a/en-us/blog/dubbo2-js.html
+++ /dev/null
@@ -1,233 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Cross-language, Node, NodeJS, js" />
- <meta name="description" content="This article introduces how to use Dubbo.js to implement cross-language calls." />
- <!-- 网页标签标题 -->
- <title>Implementation of cross-language calls by Dubbo2.js</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<blockquote>
-<p><a href="https://github.com/dubbo/dubbo2.js">dubbo2.js</a> is a Dubbo client for node.js developped by <a href="https://www.qianmi.com/">Qianmiwang</a>. It supports Dubbo's native protocol, which makes the RPC calls between javascript and java efficient and agile. This tool has been contributed to Dubbo's community.</p>
-</blockquote>
-<h2>Cross-language calls for micro service</h2>
-<p>Nowadays, Internet architecture tends to be micro-service way. The discussions about micro-service architecture becomes the most mentioned topic in different technical conferences. In China, most of the companies, such as Qianmiwang, choose Dubbo as their micro-servie architecture solution. As most of the internet companies, Qianmiwang uses various of programming languages. Java is for most of the backend services. Each business based on these backend can choose its own programming la [...]
-<ul>
-<li>Spring cloud. Spring cloud provides a set of components for micro-service development. It is based on HTTP protocol and is designed in the restful way, which makes it support cross-language calls. Other languages can call the services simply by implementing an HTTP interface.</li>
-<li>Service mesh. People call service mesh the next generation of micro-service framework. The core of this solution is SideCar. Even though the concept of SideCar changes a lot during the revolution of Service mesh, its main job never changed: providing reliable communication between different services.</li>
-<li>Motan. <a href="https://github.com/weibocom/motan">Motan</a> is an open source cross-language service framework developped by Sina Weibo. Its early version only supports motan-java. However, as the new versions come out, more languages are supported in order to handle the cross-language problem. Its newest version(1.1.0) provides motan-go, motan-php, motan-openresty, etc. Similar to SideCar in Service mesh, Motan forwards messages by mortan-go, which can be considered as an agent. Me [...]
-</ul>
-<p>According to the solutions below, there are two ways to solve the cross-language calls problem:</p>
-<ul>
-<li>communicating by a common protocol.</li>
-<li>implementing an agent as a protocol adapter.</li>
-</ul>
-<p>When a new team is choosing technical solutions, what I mentioned below could be our candidates. Meanwhile, the old system's compatibility and migration costs should also be considered. The first trial we did is to work on RPC protocol.</p>
-<h2>Cross-language calls by a common protocol</h2>
-<h3>SpringMVC</h3>
-<p><img src="../../img/blog/springmvc.png" alt="springmvc"></p>
-<p>Before achieving the real cross-language calls, the most common solution is to use the http protocol. We can call Dubbo provider indirectly by controller/restController provided by springmvc. This is easy to carry out, but there are lots of inconveniences. firstly, a call will go through too many nodes. Secondly, an extra communication layer (for http protocol) will be involved, but it could have been handled simply by the TCP protocol. Thirdly, we need to implement the RPC interface [...]
-<h3>We support some common protocols</h3>
-<p>Most of the service management frameworks support multiple protocols, dubbo as well. Besides its own protocol, the common protocols such as Dangdangwang's <a href="https://dangdangdotcom.github.io/dubbox/rest.html">Rest</a> protocol and Qianmiwang's <a href="https://github.com/apache/dubbo-rpc-jsonrpc">json-rpc</a> protocol are also supported.</p>
-<p>The developers getting used to traditional RPC interfaces might feel uncomfortable while working on restful RPC interfaces. On the one hand, this is not good for rebuilding new interfaces. On the other hand, restful style might make these interfaces incompatible with the other protocols used by old interfaces. Of course, if there is no old system problems, using Rest protocol is the easiest implementation of cross-language calls, since most of the languages support it.</p>
-<p>Even if Dubbo has tried on restful interface, the difference between rest architecture and RPC architecture should not be ignored. Rest architecture defines each resources, and it needs basic operations of http protocols such as GET, POST, DELETE, PUT. In my opinion, a Rest protocol is more for calls between different systems on the internet, while RPC is suitable for inner system calls. Similar to Rest protocol, json-rpc is also implemented by text sequence and http protocol. Using j [...]
-<p>Json-rpc is Qianmiwang's early solution for cross-language protocol. They open-sourced their <a href="https://github.com/dubbo/dubbo-client-py">dubbo-client-py</a> and <a href="https://github.com/QianmiOpen/dubbo-node-client">dubbo-node-client</a>, two clients based on json-rpc protocol. With these tools, we can easily call the rpc services provided by dubbo-provider-java with while using python or node.js. The inner system calls for java services are still mainly implemented by Dubbo [...]
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:protocol</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"dubbo"</span> <span class="hljs-attr">port</span>=<span class="hljs-string">"20880"</span> /></span>
-<span class="hljs-tag"><<span class="hljs-name">dubbo:protocol</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"jsonrpc"</span> <span class="hljs-attr">port</span>=<span class="hljs-string">"8080"</span> /></span>
-</code></pre>
-<h3>Customized Protocols for Cross-language Support</h3>
-<p>The so-called protocol of the microservice framework can be simply interpreted as: message format and serialization scheme. Generally, the service governance framework would provide numbers of protocol configuration items for users to choose from. In addition to the above two common protocols,there exists some other customized protocols like the dubbo protocol, the default protocol for the dubbo framework, and Motan2, a cross-language protocol provided by the motan framework.</p>
-<h4>Motan2 for cross-language support</h4>
-<p><img src="../../img/blog/motan-protocol-en.png" alt="motan2"></p>
-<p>In the original Motan protocol, the protocol message consisted only of the Header and the Body, making deserialization indispensable for acquiring data stored in the Body, like path, param and group, which is terribly unfriendly for cross-language support. Therefore, the content of the protocol was modifiedin Motan2, Weibo released the open-source projects, <a href="https://github.com/weibocom/motan-go/">motan-go</a>, <a href="https://github.com/weibocom/motan-php">motan-php</a> and < [...]
-<p><img src="../../img/blog/motan-agent.png" alt="agent"></p>
-<p>After observation we find out that there is no big difference between the configuration of Motan2 and the dual protocol. It’s just that the agent here is implicit, and it co-exists with the main service. The most obvious difference is that different languages do not interact directly in agent scheme.</p>
-<h4>Dubbo for cross-language support</h4>
-<p>Instead of cross-language support, the dubbo protocol was originally designed only for common rpc requests. However, it’s not always the case that we can only choose to support it or not. We can always choose to offer different levels of support. It may be hard to offer cross-language support based on the dubbo protocol, but not impossible. Actually, Qianmiwang succeeded. It conquered the front-end cross-language business field built by nodejs with dubbo2.js. It builds the bridge betw [...]
-<h5>Dubbo protocol message format:</h5>
-<p><img src="../../img/blog/dubbo-protocol.png" alt="dubbo协议"></p>
-<p>Details in dubbo protocol header message:</p>
-<ul>
-<li>Magic: similar to magic number in Java bytes code files, which is used to determine whether it is a data pack of dubbo protocol. The magic number is the constant, 0xdabb.</li>
-<li>Flag: contains 8 bits. The lower four bits are used to indicate the type of serialization tool used for message body data (default hessian). Among the upper four bits, the 1 at first bit indicates request, the 1 at second bit indicates dual transfer, 1 at third bits indicates the heartbeat.</li>
-<li>Status: used toset response status. Dubbo defines some types for response. Details can be found in <span data-type="color" style="color:rgb(36, 41, 46)"><span data-type="background" style="background-color:rgba(27, 31, 35, 0.05)">com.alibaba.dubbo.remoting.exchange.Response</span></span></li>
-<li>Invoke id: Message id,Type long, Unique indentifier for each request (Due to asynchronous communication, it is used to match the request to the corresponding returned response)</li>
-<li>Body length: message body length, type int,record bytes of body content.</li>
-<li>Body content: request param, where serializedresponse parameters are stored.</li>
-</ul>
-<p>Protocol messages will eventually become bytes and be transmitted using TCP. Any language that supports network modules and has a socket will be able to be communicatedwith. Then, why cross-language support is difficult? There are two main obstaclesin calling service in Java using other languages:</p>
-<ol>
-<li><span data-type="color" style="color:#24292E">How </span><span data-type="color" style="color:#212121">can different languages represent data types in java, especially dynamiclanguages with possible non-strict data types</span>?</li>
-<li><span data-type="color" style="color:#24292E">How to serialize string across language?</span></li>
-</ol>
-<h2>How does dubbo2.js solve problems?</h2>
-<p>We have analyzed two obstacles above. The key to dubbo2.js in solving these two problems depends on two class libraries: <a href="https://github.com/node-modules/js-to-java">js-to-java</a>，<a href="https://github.com/node-modules/hessian.js">hessian.js</a>. js-to-java, which makes nodejs have the ability to express Java objects. Hessian.js provides serialization capabilities. With the help of nodejs socket, and a duplicate set of dubbo protocol message format, we can finally achieve [...]
-<h2>Quick Start</h2>
-<p>To give an intuitive feeling to readers interested in dubbo2.js, this section presents a quick start example that shows how easy it is to call dubbo service using dubbo2.js.</p>
-<h3>1. Initiate dubbo-java-provider</h3>
-<p>Java provides the backend dubbo service. Firstly, let’s define the service interface:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">DemoProvider</span> </span>{
- <span class="hljs-function">String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span></span>;
- <span class="hljs-function">String <span class="hljs-title">echo</span><span class="hljs-params">()</span> </span>;
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">test</span><span class="hljs-params">()</span></span>;
- <span class="hljs-function">UserResponse <span class="hljs-title">getUserInfo</span><span class="hljs-params">(UserRequest request)</span></span>;
-}
-</code></pre>
-<p>Then we implement the interface:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoProviderImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">DemoProvider</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- System.out.println(<span class="hljs-string">"["</span> + <span class="hljs-keyword">new</span> SimpleDateFormat(<span class="hljs-string">"HH:mm:ss"</span>).format(<span class="hljs-keyword">new</span> Date()) + <span class="hljs-string">"] Hello "</span> + name + <span class="hljs-string">", request from consumer: "</span> + RpcContext.getContext().getRemoteAddress());
- <span class="hljs-keyword">return</span> <span class="hljs-string">"Hello "</span> + name + <span class="hljs-string">", response form provider: "</span> + RpcContext.getContext().getLocalAddress();
- }
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">echo</span><span class="hljs-params">()</span> </span>{
- System.out.println(<span class="hljs-string">"receive...."</span>);
- <span class="hljs-keyword">return</span> <span class="hljs-string">"pang"</span>;
- }
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">test</span><span class="hljs-params">()</span> </span>{
- System.out.println(<span class="hljs-string">"test"</span>);
- }
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> UserResponse <span class="hljs-title">getUserInfo</span><span class="hljs-params">(UserRequest request)</span> </span>{
- System.out.println(request);
- UserResponse response = <span class="hljs-keyword">new</span> UserResponse();
- response.setStatus(<span class="hljs-string">"ok"</span>);
- Map<String, String> map = <span class="hljs-keyword">new</span> HashMap<String, String>();
- map.put(<span class="hljs-string">"id"</span>, <span class="hljs-string">"1"</span>);
- map.put(<span class="hljs-string">"name"</span>, <span class="hljs-string">"test"</span>);
- response.setInfo(map);
- <span class="hljs-keyword">return</span> response;
- }
-}
-</code></pre>
-<p>After that,<span data-type="color" style="color:#24292E"> we expose the dubbo service with xml files:</span></p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">beans</span> <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xmlns:dubbo</span>=<span class="hljs-string">"http://code.alibabatech.com/schema/dubbo"</span>
- <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://www.springframework.org/schema/beans"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
- http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd"</span>></span>
-
- <span class="hljs-comment"><!-- dubbo provider info, used to compute dependency --></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:application</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"demo-provider"</span>/></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dubbo:registry</span> <span class="hljs-attr">protocol</span>=<span class="hljs-string">"zookeeper"</span> <span class="hljs-attr">address</span>=<span class="hljs-string">"localhost:2181"</span>/></span>
-
- <span class="hljs-comment"><!-- dubbo protocol, used to expose service at port 20880 --></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:protocol</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"dubbo"</span> <span class="hljs-attr">port</span>=<span class="hljs-string">"20880"</span>/></span>
-
- <span class="hljs-comment"><!-- realize a service as a local bean --></span>
- <span class="hljs-tag"><<span class="hljs-name">bean</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"demoProvider"</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"com.alibaba.dubbo.demo.provider.DemoProviderImpl"</span>/></span>
-
- <span class="hljs-comment"><!-- claim for service interfaces to expose --></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:service</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"com.alibaba.dubbo.demo.DemoProvider"</span> <span class="hljs-attr">ref</span>=<span class="hljs-string">"demoProvider"</span> <span class="hljs-attr">version</span>=<span class="hljs-string">"1.0.0"</span>/></span>
-
-<span class="hljs-tag"></<span class="hljs-name">beans</span>></span>
-</code></pre>
-<p>After we implemented all the configurations on server side, initiate an object initiater to register a dubbo service locally:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Provider</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> <span class="hljs-keyword">throws</span> Exception </span>{
- ClassPathXmlApplicationContext context = <span class="hljs-keyword">new</span> ClassPathXmlApplicationContext(<span class="hljs-keyword">new</span> String[]{<span class="hljs-string">"META-INF/spring/dubbo-demo-provider.xml"</span>});
- context.start();
- System.in.read();
- }
-}
-</code></pre>
-<h3>2. Implement dubbo client-side for nodejs</h3>
-<p>Install dubbo2.js using npm:</p>
-<pre><code class="language-sh">npm install dubbo2.js --save
-</code></pre>
-<p>Configure dubboConfig.ts:</p>
-<pre><code class="language-typescript"><span class="hljs-keyword">import</span> { Dubbo, java, TDubboCallResult } <span class="hljs-keyword">from</span> <span class="hljs-string">'dubbo2.js'</span>
-
-<span class="hljs-keyword">const</span> dubbo = <span class="hljs-keyword">new</span> Dubbo({
- application: {name: <span class="hljs-string">'demo-provider'</span>},
- register: <span class="hljs-string">'localhost:2181'</span>,
- dubboVersion: <span class="hljs-string">'2.0.0'</span>,
- interfaces: [
- <span class="hljs-string">'com.alibaba.dubbo.demo.DemoProvider'</span>,
- ],
-});
-
-<span class="hljs-keyword">interface</span> IDemoService {
- sayHello(name: <span class="hljs-built_in">string</span>): TDubboCallResult<<span class="hljs-built_in">string</span>>;
-}
-
-<span class="hljs-keyword">export</span> <span class="hljs-keyword">const</span> demoService = dubbo.proxyService<IDemoService>({
- dubboInterface: <span class="hljs-string">'com.alibaba.dubbo.demo.DemoProvider'</span>,
- version: <span class="hljs-string">'1.0.0'</span>,
- methods: {
- sayHello(name: <span class="hljs-built_in">string</span>) {
- <span class="hljs-keyword">return</span> [java.String(name)];
- },
-
- echo() {},
-
- test() {},
-
- getUserInfo() {
- <span class="hljs-keyword">return</span> [
- java.combine(<span class="hljs-string">'com.alibaba.dubbo.demo.UserRequest'</span>, {
- id: <span class="hljs-number">1</span>,
- name: <span class="hljs-string">'nodejs'</span>,
- email: <span class="hljs-string">'node@qianmi.com'</span>,
- }),
- ];
- },
- },
-});
-</code></pre>
-<blockquote>
-<p>Using typescript brings better coding experience.</p>
-</blockquote>
-<p>Implement caller class main.ts：</p>
-<pre><code class="language-typescript"><span class="hljs-keyword">import</span> {demoService} <span class="hljs-keyword">from</span> <span class="hljs-string">'./dubboConfig'</span>
-
-demoService.sayHello(<span class="hljs-string">'kirito'</span>).then(<span class="hljs-function">(<span class="hljs-params">{res,err}</span>)=></span>{
- <span class="hljs-built_in">console</span>.log(res)
-});
-</code></pre>
-<h3>3. Call main.ts:</h3>
-<p>Run nodejs client in Debug mode:</p>
-<pre><code class="language-sh">DEBUG=dubbo* ts-node main.ts
-</code></pre>
-<p>Checkout running results:</p>
-<pre><code class="language-sh">Hello kirito, response form provider: 172.19.6.151:20880
-</code></pre>
-<p>Congratulations！</p>
-<h2>Features</h2>
-<ul>
-<li>Support zookeeper as register center</li>
-<li>Support TCP Dubbo Native protocol</li>
-<li>Support directly Dubbo connection</li>
-<li>Support link tracing</li>
-<li>Generate dubbo interface Automatically</li>
-</ul>
-<h2>More details</h2>
-<p>The sample code in this article is available here, <a href="https://github.com/dubbo/dubbo2.js">https://github.com/dubbo/dubbo2.js</a>.
-If you don't know much about the dubbo protocol and want to understand how it works, the project provides a sub-moudle: java-socket-consumer, which is implemented in a process-oriented approach, realizing a process of sending dubbo protocal message with native socket and making function calls, and then get response.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/dubbo2-js.json b/en-us/blog/dubbo2-js.json
deleted file mode 100644
index fc52859..0000000
--- a/en-us/blog/dubbo2-js.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "dubbo2-js.md",
- "__html": "<h1>Implementation of cross-language calls by Dubbo2.js</h1>\n<blockquote>\n<p><a href=\"https://github.com/dubbo/dubbo2.js\">dubbo2.js</a> is a Dubbo client for node.js developped by <a href=\"https://www.qianmi.com/\">Qianmiwang</a>. It supports Dubbo's native protocol, which makes the RPC calls between javascript and java efficient and agile. This tool has been contributed to Dubbo's community.</p>\n</blockquote>\n<h2>Cross-language calls for micro service</h2>\n<p>Nowada [...]
- "link": "/en-us/blog/dubbo2-js.html",
- "meta": {
- "title": "Implementation of cross-language calls by Dubbo2.js",
- "keywords": "Dubbo, Cross-language, Node, NodeJS, js",
- "description": "This article introduces how to use Dubbo.js to implement cross-language calls."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/gsoc-2018.html b/en-us/blog/gsoc-2018.html
deleted file mode 100644
index 57f7f7f..0000000
--- a/en-us/blog/gsoc-2018.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, GSoC" />
- <meta name="description" content="The GSoC(Google Summer of Code) 2018 projects has been announced" />
- <!-- 网页标签标题 -->
- <title>GSoC 2018</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>The GSoC(Google Summer of Code) 2018 projects has been announced, Raghu Reddy's project "Extending Serialization protocols support for Apache Dubbo" has been <a href="https://summerofcode.withgoogle.com/projects/#4747840161579008">accepted</a>! Congratulations!</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/gsoc-2018.json b/en-us/blog/gsoc-2018.json
deleted file mode 100644
index dfc7dcb..0000000
--- a/en-us/blog/gsoc-2018.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "gsoc-2018.md",
- "__html": "<h2>The GSoC(Google Summer of Code) 2018 projects has been announced</h2>\n<p>The GSoC(Google Summer of Code) 2018 projects has been announced, Raghu Reddy's project "Extending Serialization protocols support for Apache Dubbo" has been <a href=\"https://summerofcode.withgoogle.com/projects/#4747840161579008\">accepted</a>! Congratulations!</p>\n",
- "link": "/en-us/blog/gsoc-2018.html",
- "meta": {
- "title": "GSoC 2018",
- "keywords": "Dubbo, GSoC",
- "description": "The GSoC(Google Summer of Code) 2018 projects has been announced"
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/index.html b/en-us/blog/index.html
deleted file mode 100644
index f3aaf2c..0000000
--- a/en-us/blog/index.html
+++ /dev/null
@@ -1,32 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="blog" />
- <meta name="description" content="blog" />
- <!-- 网页标签标题 -->
- <title>blog</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blog.css" />
-</head>
-<body>
- <div id="root"><div class="blog-list-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a href [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blog.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-qos.html b/en-us/blog/introduction-to-dubbo-qos.html
deleted file mode 100644
index db571b4..0000000
--- a/en-us/blog/introduction-to-dubbo-qos.html
+++ /dev/null
@@ -1,245 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, qos" />
- <meta name="description" content="This article introduces how to use Dubbo's QoS to achieve dynamic configuration." />
- <!-- 网页标签标题 -->
- <title>Manipulating Services Dynamically via QoS</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>QoS (short form of <strong>Quality of Service</strong>), is a common terminology talking about network devices. For example, by adjusting and manipulating the weights of ports of a router dynamically via QoS, engineers could give priority to services running on these ports and make sure these services' quality and reliability.</p>
-<p>In Dubbo, QoS is used to query and manipulate services dynamically, like getting a list of active provider and consumer services, and launching or withdrawing services (i.e registering to or unregistering services from registration center).</p>
-<h2>Mechanism of QoS</h2>
-<p>From 2.5.8, QoS is introduced into Dubbo and is activated by default. All QoS's features are abstracted to commands, which could be executed to get responses from QoS.</p>
-<blockquote>
-<p>QoS is based on Netty4. In versions earlier than 2.6.x, Dubbo relies on Netty3, so you have to add Netty4 as a dependency explicitly to ensure that Netty4 works. If you generate a Dubbo application on <a href="http://start.dubbo.io">http://start.dubbo.io</a>, there's no need to add configurations because Netty4 is listed as a dependency by default.</p>
-</blockquote>
-<p><img src="../../img/blog/qos-architecture.png" alt="undefined"></p>
-<p>The picture above shows how QoS works:</p>
-<ol>
-<li>Start and listen to a port (22222 by default).</li>
-<li>Choose a corresponding request handler by detecting the protocol (telnet or http) a request comply with.</li>
-<li>Decode and parse the request to generate corresponding command according to the protocol.</li>
-<li>Execute commands and return with responses.</li>
-</ol>
-<h3>QoS Commands:</h3>
-<p>Commands that QoS supports at the current moment include:</p>
-<ul>
-<li><code>help</code>, list available commands</li>
-<li><code>ls</code>: list all active provider services and consumer services</li>
-<li><code>online</code>: dynamically register a service or all services to registration center</li>
-<li><code>offline</code>: dynamically remove (unregister) a services or all services from registration center</li>
-<li><code>quit</code>: quit the current telnet session</li>
-</ul>
-<p>Now we are going to demonstrate how to manipulate services dynamically via QoS.</p>
-<h4>Access QoS via Telnet</h4>
-<p>Assuming that our Dubbo server has started, connect to it via telnet:</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> telnet localhost 22222</span>
-Trying 127.0.0.1...
-Connected to localhost.
-Escape character is '^]'.
- ????????? ??? ?? ??????????? ??????????? ????????
- ??? ???? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ??? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ??? ??? ??? ?????????? ?????????? ??? ???
- ??? ??? ??? ??? ??????????? ??????????? ??? ???
- ??? ??? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ???? ??? ??? ??? ??? ??? ??? ??? ???
- ????????? ????????? ??????????? ??????????? ????????
-<span class="hljs-meta">
-
-dubbo></span><span class="bash"></span>
-</code></pre>
-<p>A <code>dubbo></code> prompt would show up once you connect to server. Now input <code>help</code>:</p>
-<pre><code class="language-sh">dubbo><span class="hljs-built_in">help</span>
-+---------+----------------------------------------------------------------------------------+
-| <span class="hljs-built_in">help</span> | <span class="hljs-built_in">help</span> <span class="hljs-built_in">command</span> |
-+---------+----------------------------------------------------------------------------------+
-| ls | ls service |
-+---------+----------------------------------------------------------------------------------+
-| offline | offline dubbo |
-+---------+----------------------------------------------------------------------------------+
-| online | online dubbo |
-+---------+----------------------------------------------------------------------------------+
-| quit | quit telnet console |
-+---------+----------------------------------------------------------------------------------+
-
-dubbo>
-</code></pre>
-<p>This command lists all available commands with explanations.</p>
-<p>You can also use <code>help</code> to a specific command to read examples of that command.</p>
-<pre><code class="language-sh">dubbo><span class="hljs-built_in">help</span> online
-+--------------+----------------------------------------------------------------------------------+
-| COMMAND NAME | online |
-+--------------+----------------------------------------------------------------------------------+
-| EXAMPLE | online dubbo |
-| | online xx.xx.xxx.service |
-+--------------+----------------------------------------------------------------------------------+
-</code></pre>
-<p>Use <code>ls</code> to check services' status:</p>
-<pre><code class="language-sh">dubbo>ls
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| Y |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-</code></pre>
-<p>There is a service named <code>org.apache.dubbo.demo.provider.DemoService</code> in the provider side. <code>PUB=Y</code> in the second columns means that the service has been published to the registration center, waiting to be called by the consumer side.</p>
-<p>Assuming that we need to withdraw a service dynamically, we can use <code>offline</code> command:</p>
-<pre><code>dubbo>offline org.apache.dubbo.demo.provider.DemoService
-OK
-</code></pre>
-<p>You can see that the command responds with <code>OK</code>. Check the services' status using <code>ls</code>:</p>
-<pre><code class="language-sh">dubbo>ls
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| N |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-</code></pre>
-<p>You can see that <code>PUB</code> of <code>org.apache.dubbo.demo.provider.DemoService</code> has been set to <code>N</code>.</p>
-<p>Quit the current telnet session using <code>quit</code>:</p>
-<pre><code class="language-sh">dubbo>quit
-BYE!
-Connection closed by foreign host.
-</code></pre>
-<h4>Access QoS via HTTP</h4>
-<p>In the example above we performed an offline action to <code>org.apache.dubbo.demo.provider.DemoService</code>. Now we are going to demonstrate how to register the service above via HTTP.</p>
-<pre><code class="language-sh">$ curl -i http://localhost:22222/online?service=org.apache.dubbo.demo.provider.DemoService
-HTTP/1.1 200 OK
-Content-Type: text/plain
-Content-Length: 2
-
-OK%
-</code></pre>
-<blockquote>
-<p>Beware of the parameters of online action. They need to be provided in the form of <code>key=value</code>. However, <code>key</code> would be ignored actually.</p>
-</blockquote>
-<p>The action responds with <code>OK</code>. Now use <code>ls</code> to check providers' status at the current moment.</p>
-<pre><code>$ curl -i http://localhost:22222/ls
-HTTP/1.1 200 OK
-Content-Type: text/plain
-Content-Length: 365
-
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| Y |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-</code></pre>
-<p>You can see that the service's <code>PUB</code> status has been changed to <code>Y</code>.</p>
-<h3>QoS' Parameters</h3>
-<p>You can use parameters that QoS provides to config its startup. These parameters include:</p>
-<table>
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Explanation</th>
-<th>Default</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>qosEnable</td>
-<td>Activate QoS or not</td>
-<td>true</td>
-</tr>
-<tr>
-<td>qosPort</td>
-<td>The port QoS would bind to</td>
-<td>22222</td>
-</tr>
-<tr>
-<td>qosAcceptForeignIp</td>
-<td>Enable remote access or not</td>
-<td>false</td>
-</tr>
-</tbody>
-</table>
-<blockquote>
-<p>Attention. From 2.6.4/2.7.0, <code>qosAcceptForeignIp</code> is set to <code>false</code> by default, because it's risky if this property is set to <code>true</code>. Think twice before you turn it on.</p>
-</blockquote>
-<p>You can configure these parameters in the following ways:</p>
-<ul>
-<li>System property</li>
-<li><code>dubbo.properties</code></li>
-<li>XML</li>
-<li>Spring-boot auto configuration</li>
-</ul>
-<p>They have priority in the following order: system property > <code>dubbo.properties</code> > XML > spring-boot.</p>
-<h4>System Property</h4>
-<pre><code>-Ddubbo.application.qos.enable=true
--Ddubbo.application.qos.port=33333
--Ddubbo.application.qos.accept.foreign.ip=false
-</code></pre>
-<h4><code>Dubbo.properties</code></h4>
-<p>Create a <code>dubbo.properties</code> file in this directory <code>src/main/resources</code> in your project, and copy the following codes into it:</p>
-<pre><code>dubbo.application.qos.enable=true
-dubbo.application.qos.port=33333
-dubbo.application.qos.accept.foreign.ip=false
-</code></pre>
-<h4>XML</h4>
-<p>If you are going to config using XML, you can try this:</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">beans</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://www.springframework.org/schema/beans"</span>
- <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xmlns:dubbo</span>=<span class="hljs-string">"http://dubbo.apache.org/schema/dubbo"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://www.springframework.org/schema/beans
- http://www.springframework.org/schema/beans/spring-beans.xsd
- http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:application</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"demo-provider"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:parameter</span> <span class="hljs-attr">key</span>=<span class="hljs-string">"qos.enable"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"true"</span>/></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:parameter</span> <span class="hljs-attr">key</span>=<span class="hljs-string">"qos.accept.foreign.ip"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"false"</span>/></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:parameter</span> <span class="hljs-attr">key</span>=<span class="hljs-string">"qos.port"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"33333"</span>/></span>
- <span class="hljs-tag"></<span class="hljs-name">dubbo:application</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:registry</span> <span class="hljs-attr">address</span>=<span class="hljs-string">"multicast://224.5.6.7:1234"</span>/></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:protocol</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"dubbo"</span> <span class="hljs-attr">port</span>=<span class="hljs-string">"20880"</span>/></span>
- <span class="hljs-tag"><<span class="hljs-name">dubbo:service</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"org.apache.dubbo.demo.provider.DemoService"</span> <span class="hljs-attr">ref</span>=<span class="hljs-string">"demoService"</span>/></span>
- <span class="hljs-tag"><<span class="hljs-name">bean</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"demoService"</span> <span class="hljs-attr">class</span>=<span class="hljs-string">"org.apache.dubbo.demo.provider.DemoServiceImpl"</span>/></span>
-<span class="hljs-tag"></<span class="hljs-name">beans</span>></span>
-</code></pre>
-<h4><code>spring-boot</code> auto configuration</h4>
-<p>If you are developing a spring-boot application, you can configure in <code>application.properties</code> or <code>application.yml</code>:</p>
-<pre><code>dubbo.application.qosEnable=true
-dubbo.application.qosPort=33333
-dubbo.application.qosAcceptForeignIp=false
-</code></pre>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-qos.json b/en-us/blog/introduction-to-dubbo-qos.json
deleted file mode 100644
index 9bf7922..0000000
--- a/en-us/blog/introduction-to-dubbo-qos.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "introduction-to-dubbo-qos.md",
- "__html": "<h1>Manipulating Services Dynamically via QoS</h1>\n<p>QoS (short form of <strong>Quality of Service</strong>), is a common terminology talking about network devices. For example, by adjusting and manipulating the weights of ports of a router dynamically via QoS, engineers could give priority to services running on these ports and make sure these services' quality and reliability.</p>\n<p>In Dubbo, QoS is used to query and manipulate services dynamically, like getting a list [...]
- "link": "/en-us/blog/introduction-to-dubbo-qos.html",
- "meta": {
- "title": "Manipulating Services Dynamically via QoS",
- "keywords": "Dubbo, qos",
- "description": "This article introduces how to use Dubbo's QoS to achieve dynamic configuration."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-spi-2.html b/en-us/blog/introduction-to-dubbo-spi-2.html
deleted file mode 100644
index 859ea3b..0000000
--- a/en-us/blog/introduction-to-dubbo-spi-2.html
+++ /dev/null
@@ -1,389 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, SPI, source code analysis" />
- <meta name="description" content="This article introduces the principles and details of Dubbo's SPI." />
- <!-- 网页标签标题 -->
- <title>Dubbo extensible mechanism source code analysis</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>In the <a href="./introduction-to-dubbo-spi.md">actual implementation of the Dubbo extensibility mechanism</a>, we learned some concepts of the Dubbo extension mechanism, explored the implementation of LoadBalance in Dubbo, and implemented a LoadBalance on our own. Do you think Dubbo's extension mechanism is great? Next, we will go deep into the source code of Dubbo and see what it is.</p>
-<h2>ExtensionLoader</h2>
-<p><code>ExtensionLoader</code> is the core class, which is responsible for the loading and lifecycle management of extension points. Let's start with this class. There are many methods of Extension, and the common methods include:</p>
-<ul>
-<li><code>public static <T> ExtensionLoader<T> getExtensionLoader(Class<T> type)</code></li>
-<li><code>public T getExtension(String name)</code></li>
-<li><code>public T getAdaptiveExtension()</code></li>
-</ul>
-<p>The common usages are:</p>
-<ul>
-<li><code>LoadBalance lb = ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(loadbalanceName)</code></li>
-<li><code>RouterFactory routerFactory = ExtensionLoader.getExtensionLoader(RouterFactory.class).getAdaptiveExtension()</code></li>
-</ul>
-<p>Notice: In the source code shown below, I'll remove extraneous code (such as logging, exception catching, and so on) to make it easy to read and understand.</p>
-<ol>
-<li>getExtensionLoader
-This is a static factory method that enters an extensible interface and returns an ExtensionLoader entity class for this interface. With this entity class, you can get not only a specific extension based on name, but also an adaptive extension.</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <T> <span class="hljs-function">ExtensionLoader<T> <span class="hljs-title">getExtensionLoader</span><span class="hljs-params">(Class<T> type)</span> </span>{
- <span class="hljs-comment">// An extension point must be an interface</span>
- <span class="hljs-keyword">if</span> (!type.isInterface()) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"Extension type("</span> + type + <span class="hljs-string">") is not interface!"</span>);
- }
- <span class="hljs-comment">// @SPI annotations must be provided</span>
- <span class="hljs-keyword">if</span> (!withExtensionAnnotation(type)) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"Extension type without @SPI Annotation!"</span>);
- }
- <span class="hljs-comment">// Get the corresponding ExtensionLoader from the cache according to the interface</span>
- <span class="hljs-comment">// Each extension will only be loaded once</span>
- ExtensionLoader<T> loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
- <span class="hljs-keyword">if</span> (loader == <span class="hljs-keyword">null</span>) {
- <span class="hljs-comment">// Initialize extension</span>
- EXTENSION_LOADERS.putIfAbsent(type, <span class="hljs-keyword">new</span> ExtensionLoader<T>(type));
- loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
- }
- <span class="hljs-keyword">return</span> loader;
-}
-
-<span class="hljs-function"><span class="hljs-keyword">private</span> <span class="hljs-title">ExtensionLoader</span><span class="hljs-params">(Class<?> type)</span> </span>{
- <span class="hljs-keyword">this</span>.type = type;
- objectFactory = (type == ExtensionFactory.class ? <span class="hljs-keyword">null</span> : ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension());
-}
-</code></pre>
-<ol start="2">
-<li>getExtension</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">public</span> T <span class="hljs-title">getExtension</span><span class="hljs-params">(String name)</span> </span>{
- Holder<Object> holder = cachedInstances.get(name);
- <span class="hljs-keyword">if</span> (holder == <span class="hljs-keyword">null</span>) {
- cachedInstances.putIfAbsent(name, <span class="hljs-keyword">new</span> Holder<Object>());
- holder = cachedInstances.get(name);
- }
- Object instance = holder.get();
- <span class="hljs-comment">// Get it from the cache. If it does not exist, create</span>
- <span class="hljs-keyword">if</span> (instance == <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">synchronized</span> (holder) {
- instance = holder.get();
- <span class="hljs-keyword">if</span> (instance == <span class="hljs-keyword">null</span>) {
- instance = createExtension(name);
- holder.set(instance);
- }
- }
- }
- <span class="hljs-keyword">return</span> (T) instance;
-}
-</code></pre>
-<p>Some judgments and caching have been made in the getExtension method, and the main logic is in the createExtension method. Let's move on to the createExtension method.</p>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">private</span> T <span class="hljs-title">createExtension</span><span class="hljs-params">(String name)</span> </span>{
- <span class="hljs-comment">// Get the extension class according to the name of extension point. For example, for LoadBalance, get the RandomLoadBalance class according to random</span>
- Class<?> clazz = getExtensionClasses().get(name);
-
- T instance = (T) EXTENSION_INSTANCES.get(clazz);
- <span class="hljs-keyword">if</span> (instance == <span class="hljs-keyword">null</span>) {
- <span class="hljs-comment">// Use reflection to call newInstance to create an example of an extension class</span>
- EXTENSION_INSTANCES.putIfAbsent(clazz, (T) clazz.newInstance());
- instance = (T) EXTENSION_INSTANCES.get(clazz);
- }
- <span class="hljs-comment">// Make dependency injection for the extended class samples</span>
- injectExtension(instance);
- <span class="hljs-comment">// If there is a wrapper, add the wrapper</span>
- Set<Class<?>> wrapperClasses = cachedWrapperClasses;
- <span class="hljs-keyword">if</span> (wrapperClasses != <span class="hljs-keyword">null</span> && !wrapperClasses.isEmpty()) {
- <span class="hljs-keyword">for</span> (Class<?> wrapperClass : wrapperClasses) {
- instance = injectExtension((T) wrapperClass.getConstructor(type).newInstance(instance));
- }
- }
- <span class="hljs-keyword">return</span> instance;
-}
-</code></pre>
-<p>The createExtension method has done the following:</p>
-<ol>
-<li>First, get the corresponding extension class according to name. Read the extension point configuration file from the <code>META-INF</code> folder under ClassPath.</li>
-<li>Use reflection to create an instance of an extended class.</li>
-<li>make dependency injection for the attributes of the extended class instance. That is, IoC.</li>
-<li>If there is a wrapper, add the wrapper. That is, AOP.</li>
-</ol>
-<p>Let's focus on these four processes.</p>
-<ol>
-<li>Get the corresponding extension class according to name. Let’s read the code first:</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">private</span> Map<String, Class<?>> getExtensionClasses() {
- Map<String, Class<?>> classes = cachedClasses.get();
- <span class="hljs-keyword">if</span> (classes == <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">synchronized</span> (cachedClasses) {
- classes = cachedClasses.get();
- <span class="hljs-keyword">if</span> (classes == <span class="hljs-keyword">null</span>) {
- classes = loadExtensionClasses();
- cachedClasses.set(classes);
- }
- }
- }
- <span class="hljs-keyword">return</span> classes;
- }
-
-<span class="hljs-comment">// synchronized in getExtensionClasses</span>
-<span class="hljs-keyword">private</span> Map<String, Class<?>> loadExtensionClasses() {
- <span class="hljs-keyword">final</span> SPI defaultAnnotation = type.getAnnotation(SPI.class);
- <span class="hljs-keyword">if</span> (defaultAnnotation != <span class="hljs-keyword">null</span>) {
- String value = defaultAnnotation.value();
- <span class="hljs-keyword">if</span> (value != <span class="hljs-keyword">null</span> && (value = value.trim()).length() > <span class="hljs-number">0</span>) {
- String[] names = NAME_SEPARATOR.split(value);
- <span class="hljs-keyword">if</span> (names.length > <span class="hljs-number">1</span>) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalStateException(<span class="hljs-string">"more than 1 default extension name on extension "</span> + type.getName());
- }
- <span class="hljs-keyword">if</span> (names.length == <span class="hljs-number">1</span>) cachedDefaultName = names[<span class="hljs-number">0</span>];
- }
- }
-
- Map<String, Class<?>> extensionClasses = <span class="hljs-keyword">new</span> HashMap<String, Class<?>>();
- loadFile(extensionClasses, DUBBO_INTERNAL_DIRECTORY);
- loadFile(extensionClasses, DUBBO_DIRECTORY);
- loadFile(extensionClasses, SERVICES_DIRECTORY);
- <span class="hljs-keyword">return</span> extensionClasses;
-}
-</code></pre>
-<p>This process is very simple. Get the extension class from the cache first, and if it does not exist, load it from the configuration file. The path of the configuration file has been mentioned before:</p>
-<ul>
-<li><code>META-INF/dubbo/internal</code></li>
-<li><code>META-INF/dubbo</code></li>
-<li><code>META-INF/services</code></li>
-</ul>
-<ol start="2">
-<li>Use reflection to create an extended instance. This process is very simple. We can do this using <code>clazz.newInstance()</code>. The attributes of the extended instance created are all null values.</li>
-<li>Extended instance is automatic assembly. In the actual scenario, there have dependencies between classes. Dependencies are also referenced in the extended instance, such as a simple Java class, an extension of another Dubbo, or a Spring Bean. The situation of dependencies is complex, and Dubbo's processing is relatively complicated. We will have a special chapter to explain it later. Now, we just need to know that Dubbo can correctly inject common dependencies in extension points, Du [...]
-<li>Extended instance is auto-wrapping. Auto-wrapping is about implementing Spring like AOP functionality. Dubbo uses it to implement some common functions internally, such as logging, monitoring, and so on. The contents of the extended instance auto-wrapper will also be explained separately later.</li>
-</ol>
-<p>After the above 4 steps, Dubbo creates and initializes an extended instance. The dependencies of this instance are injected and packaged as needed. At this point, this extended instance can be used.</p>
-<h2>Auto-assembly of Dubbo SPI advanced usage</h2>
-<p>The relevant code for auto-assembly is in the injectExtension method:</p>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">private</span> T <span class="hljs-title">injectExtension</span><span class="hljs-params">(T instance)</span> </span>{
- <span class="hljs-keyword">for</span> (Method method : instance.getClass().getMethods()) {
- <span class="hljs-keyword">if</span> (method.getName().startsWith(<span class="hljs-string">"set"</span>)
- && method.getParameterTypes().length == <span class="hljs-number">1</span>
- && Modifier.isPublic(method.getModifiers())) {
- Class<?> pt = method.getParameterTypes()[<span class="hljs-number">0</span>];
-
- String property = method.getName().length() > <span class="hljs-number">3</span> ? method.getName().substring(<span class="hljs-number">3</span>, <span class="hljs-number">4</span>).toLowerCase() + method.getName().substring(<span class="hljs-number">4</span>) : <span class="hljs-string">""</span>;
- Object object = objectFactory.getExtension(pt, property);
- <span class="hljs-keyword">if</span> (object != <span class="hljs-keyword">null</span>) {
- method.invoke(instance, object);
- }
- }
- }
- <span class="hljs-keyword">return</span> instance;
-}
-</code></pre>
-<p>To accomplish the automatic assembly of dependencies of the extended instances, you first need to know what the dependencies are and what the types of dependencies are. The solution of Dubbo is to find the Java standard setter method. That is, the method name starting with set has only one parameter. If such a set method exists in an extension class, Dubbo injects it into dependencies, which is similar to the injection of Spring's set method. However, dependency injection in Dubbo is [...]
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">private</span> <span class="hljs-title">ExtensionLoader</span><span class="hljs-params">(Class<?> type)</span> </span>{
- <span class="hljs-keyword">this</span>.type = type;
- objectFactory = (type == ExtensionFactory.class ? <span class="hljs-keyword">null</span> : ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension());
-}
-</code></pre>
-<p>ObjectFacore is also an extension, obtained through <code>ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension()</code>.</p>
-<p><img src="https://raw.githubusercontent.com/vangoleo/wiki/master/dubbo/dubbo-extensionfactory.png" alt="Dubbo-ExtensionFactory | left"></p>
-<p>ExtensionFactory includes three implementations:</p>
-<ol>
-<li>SpiExtensionFactory: use Dubbo's Spi to load Extension.</li>
-<li>SpringExtensionFactory: load Extension from the Spring container.</li>
-<li>AdaptiveExtensionFactory: adaptive AdaptiveExtensionLoader</li>
-</ol>
-<p>Pay attention to the AdaptiveExtensionLoader here, the source code is as follows:</p>
-<pre><code class="language-java"><span class="hljs-meta">@Adaptive</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">AdaptiveExtensionFactory</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">ExtensionFactory</span> </span>{
-
- <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> List<ExtensionFactory> factories;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">AdaptiveExtensionFactory</span><span class="hljs-params">()</span> </span>{
- ExtensionLoader<ExtensionFactory> loader = ExtensionLoader.getExtensionLoader(ExtensionFactory.class);
- List<ExtensionFactory> list = <span class="hljs-keyword">new</span> ArrayList<ExtensionFactory>();
- <span class="hljs-keyword">for</span> (String name : loader.getSupportedExtensions()) {
- list.add(loader.getExtension(name));
- }
- factories = Collections.unmodifiableList(list);
- }
-
- <span class="hljs-keyword">public</span> <T> <span class="hljs-function">T <span class="hljs-title">getExtension</span><span class="hljs-params">(Class<T> type, String name)</span> </span>{
- <span class="hljs-keyword">for</span> (ExtensionFactory factory : factories) {
- T extension = factory.getExtension(type, name);
- <span class="hljs-keyword">if</span> (extension != <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">return</span> extension;
- }
- }
- <span class="hljs-keyword">return</span> <span class="hljs-keyword">null</span>;
- }
-}
-</code></pre>
-<p>The AdaptiveExtensionLoader class has @Adaptive annotations. As mentioned earlier, Dubbo creates an adaptive instance for each extension. If the extension class has @Adaptive annotations, it will use it as an adaptive class. If not, Dubbo will create one for us. So <code>ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension())</code> will return an AdaptiveExtensionLoader instance as an adaptive extension instance.
-The AdaptiveExtensionLoader will iterate through all the ExtensionFactory implementations and try to load the extensions. If found, return. If not, continue to find it in the next ExtensionFactory. Dubbo has two ExtensionFactory built in, which are searched from Dubbo's own extension mechanism and Spring container. Since ExtensionFactory itself is also an extension point, we can implement our own ExtensionFactory to enable automatic assembly of Dubbo to support our custom components. For [...]
-<h2>AOP of Dubbo SPI advanced usage</h2>
-<p>We often use AOP functionality when using Spring. Insert other logic before and after the method of the target class. For example, Spring AOP is usually used to implement logging, monitoring, and authentication, and so on.
-Does Dubbo's extension mechanism also support similar features? The answer is yes. In Dubbo, there is a special class called the Wrapper class. It uses the wrapper class to wrap the original extension point instance through the decorator pattern, and then inserts additional logic before and after the original extension point implementation to implement AOP functionality.</p>
-<h3>What is the Wrapper class</h3>
-<p>So what kind of class is the Wrapper class in the Dubbo extension mechanism? The Wrapper class is a class that has a replication constructor and also is a typical decorator pattern. Here's a Wrapper class:</p>
-<pre><code class="language-java"><span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">A</span></span>{
- <span class="hljs-keyword">private</span> A a;
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">A</span><span class="hljs-params">(A a)</span></span>{
- <span class="hljs-keyword">this</span>.a = a;
- }
-}
-</code></pre>
-<p>Class A has a constructor <code>public A(A a)</code>, and the argument to the constructor is A itself. Such a class can be a Wrapper class in the Dubbo extension mechanism. Such Wrapper classes in Dubbo include ProtocolFilterWrapper, ProtocolListenerWrapper, and so on. You can check the source code to deepen your understanding.</p>
-<h3>How to configure the Wrapper class</h3>
-<p>The Wrapper class in Dubbo is also an extension point. Like other extension points, it is also configured in the <code>META-INF</code> folder. For example, the ProtocolFilterWrapper and ProtocolListenerWrapper in the previous example are configured in the path <code>dubbo-rpc/dubbo-rpc-api/src/main/resources/META-INF/dubbo/internal/org.apache.dubbo.rpc.Protocol</code>:</p>
-<pre><code class="language-text">filter=org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper
-listener=org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper
-mock=org.apache.dubbo.rpc.support.MockProtocol
-</code></pre>
-<p>When Dubbo loads the extension configuration file, there is a piece of code as follows:</p>
-<pre><code class="language-java"><span class="hljs-keyword">try</span> {
- clazz.getConstructor(type);
- Set<Class<?>> wrappers = cachedWrapperClasses;
- <span class="hljs-keyword">if</span> (wrappers == <span class="hljs-keyword">null</span>) {
- cachedWrapperClasses = <span class="hljs-keyword">new</span> ConcurrentHashSet<Class<?>>();
- wrappers = cachedWrapperClasses;
- }
- wrappers.add(clazz);
-} <span class="hljs-keyword">catch</span> (NoSuchMethodException e) {}
-</code></pre>
-<p>The meaning of this code is that if the extension class has a copy constructor, it will be saved for later use. The class that has the copy constructor is the Wrapper class. The parameter obtained by <code>clazz.getConstructor(type)</code> is the constructor of the extension point interface. Note that the parameter type of the constructor is an extension point interface, not an extension class.
-Take Protocol as an example. The configuration file <code>dubbo-rpc/dubbo-rpc-api/src/main/resources/META-INF/dubbo/internal/org.apache.dubbo.rpc.Protocol defines filter=org.apache.dubbo.rpc.protocol. ProtocolFilterWrapper</code>.
-The code of ProtocolFilterWrapper is as follows:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">ProtocolFilterWrapper</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Protocol</span> </span>{
-
- <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> Protocol protocol;
-
- <span class="hljs-comment">// One parameter is the copy constructor of Protocol</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">ProtocolFilterWrapper</span><span class="hljs-params">(Protocol protocol)</span> </span>{
- <span class="hljs-keyword">if</span> (protocol == <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"protocol == null"</span>);
- }
- <span class="hljs-keyword">this</span>.protocol = protocol;
- }
-}
-</code></pre>
-<p>ProtocolFilterWrapper has a constructor <code>public ProtocolFilterWrapper(Protocol protocol)</code>, and the parameter is the extension point Protocol. So it is a Wrapper class in the Dubbo extension mechanism. The ExtensionLoader will cache it. When creating Extension instances later, the ExtensionLoader use these wrapper classes to wrap the original Extension point in turn.</p>
-<h2>Extension point adaptive</h2>
-<p>As mentioned earlier, Dubbo needs to determine which extension to use based on method parameters at runtime. So there is an extension point adaptive instance. In fact, it is an extension point proxy that delays the selection of extensions from starting Dubbo to calling RPC. Each extension point in Dubbo has an adaptive class. If it is not explicitly provided, Dubbo will automatically create one for us. By default, Javaassist is used.
-Let's first look at the code to create an adaptive extension class:</p>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">public</span> T <span class="hljs-title">getAdaptiveExtension</span><span class="hljs-params">()</span> </span>{
- Object instance = cachedAdaptiveInstance.get();
- <span class="hljs-keyword">if</span> (instance == <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">synchronized</span> (cachedAdaptiveInstance) {
- instance = cachedAdaptiveInstance.get();
- <span class="hljs-keyword">if</span> (instance == <span class="hljs-keyword">null</span>) {
- instance = createAdaptiveExtension();
- cachedAdaptiveInstance.set(instance);
- }
- }
- }
-
- <span class="hljs-keyword">return</span> (T) instance;
-}
-</code></pre>
-<p>Continue to read the createAdaptiveExtension method:</p>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">private</span> T <span class="hljs-title">createAdaptiveExtension</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">return</span> injectExtension((T) getAdaptiveExtensionClass().newInstance());
-}
-</code></pre>
-<p>Continue to read the getAdaptiveExtensionClass method:</p>
-<pre><code class="language-java"><span class="hljs-keyword">private</span> Class<?> getAdaptiveExtensionClass() {
- getExtensionClasses();
- <span class="hljs-keyword">if</span> (cachedAdaptiveClass != <span class="hljs-keyword">null</span>) {
- <span class="hljs-keyword">return</span> cachedAdaptiveClass;
- }
- <span class="hljs-keyword">return</span> cachedAdaptiveClass = createAdaptiveExtensionClass();
-}
-</code></pre>
-<p>Continue to read the createAdaptiveExtensionClass method. After a long journey, we finally come to a concrete realization. Look at this createAdaptiveExtensionClass method, which first generates the Java source code for the adaptive class, and then compile the source code into Java bytecode and load it into the JVM.</p>
-<pre><code class="language-java"><span class="hljs-keyword">private</span> Class<?> createAdaptiveExtensionClass() {
- String code = createAdaptiveExtensionClassCode();
- ClassLoader classLoader = findClassLoader();
- org.apache.dubbo.common.compiler.Compiler compiler = ExtensionLoader.getExtensionLoader(org.apache.dubbo.common.compiler.Compiler.class).getAdaptiveExtension();
- <span class="hljs-keyword">return</span> compiler.compile(code, classLoader);
-}
-</code></pre>
-<p>The default implementation of Compiler's code is javassist.</p>
-<pre><code class="language-java"><span class="hljs-meta">@SPI</span>(<span class="hljs-string">"javassist"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">Compiler</span> </span>{
- Class<?> compile(String code, ClassLoader classLoader);
-}
-</code></pre>
-<p>The createAdaptiveExtensionClassCode () method uses a StringBuilder to build Java source code for the adaptive class. The method implementation is relatively long, and the code is not posted here. The approach to bytecode generation is also interesting, first generating Java source code, then compiling it and loading it into the jvm. In this way, the generated Java class can be better controlled. And it doesn't have to care about the API of the bytecode generation framework. Because t [...]
-Below are the Java code example for Protocol adaptive class created by createAdaptiveExtensionClassCode method:</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> org.apache.dubbo.rpc;
-
-<span class="hljs-keyword">import</span> org.apache.dubbo.common.extension.ExtensionLoader;
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Protocol</span>$<span class="hljs-title">Adaptive</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">org</span>.<span class="hljs-title">apache</span>.<span class="hljs-title">dubbo</span>.<span class="hljs-title">rpc</span>.<span class="hljs-title">Protocol</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">destroy</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> UnsupportedOperationException(<span class="hljs-string">"method public abstract void org.apache.dubbo.rpc.Protocol.destroy() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!"</span>);
- }
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">int</span> <span class="hljs-title">getDefaultPort</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> UnsupportedOperationException(<span class="hljs-string">"method public abstract int org.apache.dubbo.rpc.Protocol.getDefaultPort() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!"</span>);
- }
-
- <span class="hljs-keyword">public</span> org.apache.dubbo.rpc.<span class="hljs-function">Exporter <span class="hljs-title">export</span><span class="hljs-params">(org.apache.dubbo.rpc.Invoker arg0)</span> <span class="hljs-keyword">throws</span> org.apache.dubbo.rpc.RpcException </span>{
- <span class="hljs-keyword">if</span> (arg0 == <span class="hljs-keyword">null</span>) <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"org.apache.dubbo.rpc.Invoker argument == null"</span>);
- <span class="hljs-keyword">if</span> (arg0.getUrl() == <span class="hljs-keyword">null</span>)
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"org.apache.dubbo.rpc.Invoker argument getUrl() == null"</span>);
- org.apache.dubbo.common.URL url = arg0.getUrl();
- String extName = (url.getProtocol() == <span class="hljs-keyword">null</span> ? <span class="hljs-string">"dubbo"</span> : url.getProtocol());
- <span class="hljs-keyword">if</span> (extName == <span class="hljs-keyword">null</span>)
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalStateException(<span class="hljs-string">"Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url("</span> + url.toString() + <span class="hljs-string">") use keys([protocol])"</span>);
- org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
- <span class="hljs-keyword">return</span> extension.export(arg0);
- }
-
- <span class="hljs-keyword">public</span> org.apache.dubbo.rpc.<span class="hljs-function">Invoker <span class="hljs-title">refer</span><span class="hljs-params">(java.lang.Class arg0, org.apache.dubbo.common.URL arg1)</span> <span class="hljs-keyword">throws</span> org.apache.dubbo.rpc.RpcException </span>{
- <span class="hljs-keyword">if</span> (arg1 == <span class="hljs-keyword">null</span>) <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalArgumentException(<span class="hljs-string">"url == null"</span>);
- org.apache.dubbo.common.URL url = arg1;
- String extName = (url.getProtocol() == <span class="hljs-keyword">null</span> ? <span class="hljs-string">"dubbo"</span> : url.getProtocol());
- <span class="hljs-keyword">if</span> (extName == <span class="hljs-keyword">null</span>)
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalStateException(<span class="hljs-string">"Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url("</span> + url.toString() + <span class="hljs-string">") use keys([protocol])"</span>);
- org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
- <span class="hljs-keyword">return</span> extension.refer(arg0, arg1);
- }
-}
-</code></pre>
-<p>The general logic is the same as at the beginning. The parameters are parsed through the url, and the parsed logic is controlled by the value parameter of @adaptive, and then the extension points implementation are obtained according to the name of the extension point. And then finally make the call. If you want to know the specific construction logic of .Java code, you can see the complete implementation of <code>createAdaptiveExtensionClassCode</code>.
-In the generated Protocol$Adaptive, both the getDefaultPort and destroy methods are found to throw the exception directly. Why? Take a look at the source code of Protocol:</p>
-<pre><code class="language-java"><span class="hljs-meta">@SPI</span>(<span class="hljs-string">"dubbo"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">Protocol</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">int</span> <span class="hljs-title">getDefaultPort</span><span class="hljs-params">()</span></span>;
-
- <span class="hljs-meta">@Adaptive</span>
- <T> <span class="hljs-function">Exporter<T> <span class="hljs-title">export</span><span class="hljs-params">(Invoker<T> invoker)</span> <span class="hljs-keyword">throws</span> RpcException</span>;
-
- <span class="hljs-meta">@Adaptive</span>
- <T> <span class="hljs-function">Invoker<T> <span class="hljs-title">refer</span><span class="hljs-params">(Class<T> type, URL url)</span> <span class="hljs-keyword">throws</span> RpcException</span>;
-
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">destroy</span><span class="hljs-params">()</span></span>;
-}
-</code></pre>
-<p>As you can see, there are four methods in the Protocol interface, but only the methods of export and refer use the @Adaptive annotation. Dubbo automatically generates adaptive instances, and only the methods modified by @Adaptive has a specific implementation. Therefore, in the Protocol$Adaptive class, only the export and refer methods have specific implementations, and the rest of the methods throw exceptions.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-spi-2.json b/en-us/blog/introduction-to-dubbo-spi-2.json
deleted file mode 100644
index 188bef6..0000000
--- a/en-us/blog/introduction-to-dubbo-spi-2.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "introduction-to-dubbo-spi-2.md",
- "__html": "<h1>Dubbo extensible mechanism source code analysis</h1>\n<p>In the <a href=\"./introduction-to-dubbo-spi.md\">actual implementation of the Dubbo extensibility mechanism</a>, we learned some concepts of the Dubbo extension mechanism, explored the implementation of LoadBalance in Dubbo, and implemented a LoadBalance on our own. Do you think Dubbo's extension mechanism is great? Next, we will go deep into the source code of Dubbo and see what it is.</p>\n<h2>ExtensionLoader</h [...]
- "link": "/en-us/blog/introduction-to-dubbo-spi-2.html",
- "meta": {
- "title": "Dubbo extensible mechanism source code analysis",
- "keywords": "Dubbo, SPI, source code analysis",
- "description": "This article introduces the principles and details of Dubbo's SPI."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-spi.html b/en-us/blog/introduction-to-dubbo-spi.html
deleted file mode 100644
index d274b27..0000000
--- a/en-us/blog/introduction-to-dubbo-spi.html
+++ /dev/null
@@ -1,205 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, SPI" />
- <meta name="description" content="This article introduces Dubbo's SPI mechanism." />
- <!-- 网页标签标题 -->
- <title>Dubbo Extension Mechanism in Action</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>1. Extension Mechanism of Dubbo</h2>
-<p>Dubbo is claimed as a high-performance RPC framework on its official website. Today, I want to talk about another great specialty of Dubbo --- its scalability. As quote: Rome wasn’t built in a day. Any successful system always starts as a prototype. It is impossible to design a perfect system at the beginning. Instead, we should focus on true demand and keep improving the system. On the coding side, it requires us to pay attention on abstraction layers and high-level isolation. In th [...]
-When talking about software design, people always mention scalability. A framework with good scalability requires the following:
-1.The framework should follow opening/closed principle: software entities should be open for extension, but closed for modification; This means a framework should allow the maintainer to add new functions with as few modifications as possible.
-2.The framework should allow the user to add new functions by adding code on his project without modifying the framework's original source code base.
-With microkernel architecture and extension mechanism, Dubbo satisfies such requirements and achieves good scalability. In the following chapters, we will discuss Dubbo's extension mechanism in detail.</p>
-<h2>2.Extension Solutions</h2>
-<p>Creating Extensible applications usually considers:</p>
-<ul>
-<li>Factory method pattern</li>
-<li>IoC container</li>
-<li>OSGi (Open Services Gateway initiative)</li>
-</ul>
-<p>As a framework, Dubbo does not wish to rely on other IoC containers such as Spring, Guice. OSGi is too complicated to fit Dubbo. In the end, Dubbo SPI is inherited from standard JDK SPI and makes it more powerful.</p>
-<h2>3.Java SPI Mechanism</h2>
-<p>We will first discuss Java SPI mechanism, which is a basis for understanding Dubbo’s extension mechanism. If you are familiar with Java SPI, you can skip this part.</p>
-<p>Java SPI (Service Provider Interface) is a feature for discovering and loading implementations matching a given interface provided in JDK. We can create a text file with the same name as the interface under resource directory <code>META-INF/services</code>. The content of the file is the fully qualified class name of the SPI implementation, in which each component is separated by a line breaker. JDK uses <code>java.util.ServiceLoader</code> to load implementations of a service. Let us [...]
-<ol>
-<li>Define an interface IRepository to store data.</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">IRepository</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">void</span> <span class="hljs-title">save</span><span class="hljs-params">(String data)</span></span>;
-}
-</code></pre>
-<ol start="2">
-<li>Create 2 implementations for IRepository: MysqlRepository and MongoRepository</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">MysqlRepository</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">IRepository</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">save</span><span class="hljs-params">(String data)</span> </span>{
- System.out.println(<span class="hljs-string">"Save "</span> + data + <span class="hljs-string">" to Mysql"</span>);
- }
-}
-</code></pre>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">MongoRepository</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">IRepository</span> </span>{
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">save</span><span class="hljs-params">(String data)</span> </span>{
- System.out.println(<span class="hljs-string">"Save "</span> + data + <span class="hljs-string">" to Mongo"</span>);
- }
-}
-</code></pre>
-<ol start="3">
-<li>Create a configuration file under <code>META-INF/services</code>.</li>
-</ol>
-<p>The file name is <code>META-INF/services/com.demo.IRepository</code>, the content of file is:</p>
-<pre><code class="language-text">com.demo.MongoRepository
-com.demo.MysqlRepository
-</code></pre>
-<ol start="4">
-<li>Load IRepository using ServiceLoader</li>
-</ol>
-<pre><code class="language-java">ServiceLoader<IRepository> serviceLoader = ServiceLoader.load(IRepository.class);
-Iterator<IRepository> it = serviceLoader.iterator();
-<span class="hljs-keyword">while</span> (it != <span class="hljs-keyword">null</span> && it.hasNext()){
- IRepository demoService = it.next();
- System.out.println(<span class="hljs-string">"class:"</span> + demoService.getClass().getName());
- demoService.save(<span class="hljs-string">"tom"</span>);
-}
-</code></pre>
-<p>In the above example, we created an extension and two of its applications. We created the configuration file in ClassPath and loaded the extensions using ServiceLoader. The final output is:
-class:testDubbo.MongoRepository
-Save tom to Mongo
-class:testDubbo.MysqlRepository
-Save tom to Mysql</p>
-<h2>4. Dubbo SPI Mechanism</h2>
-<p>Java SPI is simple to use. It also supports basic extension point functions, however, it has some disadvantages:</p>
-<ul>
-<li>It will load and instantiate all implementations at once to find the requested implementation.</li>
-<li>The configuration file only includes the extension implementation but does not name them, which makes it hard to reference them in applications.</li>
-<li>If extensions depend on other extensions, Java SPI cannot automatically load the dependency SPI.</li>
-<li>It does not provide functions such as IOC or AOP in Spring.</li>
-<li>It is hard to assemble extensions with other frameworks. For example, if the extension depends on Spring bean, the original Java SPI will not support it.</li>
-</ul>
-<p>Therefore, Java SPI is good for some simple scenarios, but does not fit for Dubbo. Dubbo makes some extensions on the original SPI mechanism. We will discuss more about the Dubbo SPI mechanism in the following sections.</p>
-<h2>5. Basic Concepts for Dubbo Extension Point Mechanism</h2>
-<p>Before diving into Dubbo's extension mechanism，Let us first declare some basic concepts in Dubbo SPI. Those terms will appear multiple times in the following section.</p>
-<h3>5.1 Extension Point</h3>
-<p>an interface of java.</p>
-<h3>5.2 Extension</h3>
-<p>an implementation class of the Extension Point</p>
-<h3>5.3 Extension Instance</h3>
-<p>instance of an extension point implementation class</p>
-<h3>5.4 Extension Adaptive Instance</h3>
-<p>Maybe it is a little difficult to understand this concept when hearing about it the first time. It may help you understand it better by calling it an extension proxy class. The extension adaptive instance is actually an extension proxy, which implements the method of extension point interface. When calling the interface method of the extension point, it will decide which extension to use according to the actual parameters. For example, the extension point of an IRepository has one sav [...]
-<ul>
-<li>There are two configurations in Dubbo, one is a fixed system-level configuration and it will not be changed after Dubbo launches. Another is the run-time configuration that may be different for each RPC. For instance, the timeout is configured as 10 seconds in the xml file, which will not change after Dubbo launches. However, for a certain PRC call, we can set its timeout to 30 seconds so as to override the system-level configuration. For Dubbo, the parameters called in each RPC is u [...]
-<li>Our class is usually singleton-scaled, such as beans of Spring IoC Container. When instantiating beans, if it depends on some specific extension point, it will know which extension to use, otherwise, the bean will not know how to choose extensions. At this time, a proxy mode is needed, which implements the interface of an extension point. The method can dynamically select the appropriate extension according to the run-time parameters, and this proxy is an adaptive instance. Adaptive [...]
-</ul>
-<h3>5.5 @SPI</h3>
-<p>@SPI annotation works on the interface of the extension point, which indicates that the interface is an extension point, and can be loaded by Dubbo ExtentionLoader. If there is no such ExtentionLoader, the call will throw an exception.</p>
-<h3>5.6 @Adaptive</h3>
-<p>@Adaptive annotation is used on the method that extends the interface, which indicates an adaptive method. When Dubbo generates an adaptive instance for an extension point, if the function has @Adaptive annotation, then Dubbo will generate the corresponding code for the method. The method determines which extension to use according to the parameters. When @Adaptive annotation is used on the class to implement a Decorator class, it is similar to the Decorator pattern, whose major funct [...]
-<h3>5.7 ExtentionLoader</h3>
-<p>Similar to the Java SPI ServiceLoader, it is responsible for loading extensions and life-cycle maintenance.</p>
-<h3>5.8 Extension Alias</h3>
-<p>Different from Java, each extension in Dubbo has an alias, which is used to reference them in the application, such as</p>
-<pre><code class="language-bash">random=com.alibaba.dubbo.rpc.cluster.loadbalance.RandomLoadBalance
-roundrobin=com.alibaba.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance
-</code></pre>
-<p>where random, roundrobin are alias of the corresponding extensions, and we can directly use them in the configuration file.</p>
-<h3>5.9 Paths</h3>
-<p>Similar to the way Java SPI loading the extension configuration from the <code>META-INF/services</code> directory, Dubbo will also load the extension configuration file from the following path:</p>
-<ul>
-<li><code>META-INF/dubbo/internal</code></li>
-<li><code>META-INF/dubbo</code></li>
-<li><code>META-INF/services</code></li>
-</ul>
-<h2>6. Interpretation for Dubbo's LoadBalance Extension Point</h2>
-<p>Now that we know some basic idea about Dubbo, let us check a practical extension point in Dubbo to get some intuition.</p>
-<p>We take the Dubbo’s LoadBalance extension point as an example. A service in Dubbo usually has multiple providers. When a consumer calls the service, he needs to choose one of the providers. This is an example of LoadBalance. Now, let us figure out how LoadBalance becomes an extension point in Dubbo.</p>
-<h3>6.1 LoadBalance Interfance</h3>
-<pre><code class="language-java"><span class="hljs-meta">@SPI</span>(RandomLoadBalance.NAME)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">LoadBalance</span> </span>{
-
- <span class="hljs-meta">@Adaptive</span>(<span class="hljs-string">"loadbalance"</span>)
- <T> <span class="hljs-function">Invoker<T> <span class="hljs-title">select</span><span class="hljs-params">(List<Invoker<T>> invokers, URL url, Invocation invocation)</span> <span class="hljs-keyword">throws</span> RpcException</span>;
-}
-</code></pre>
-<p>LoadBalance interface has only one select method. Select method chose one invoker among multiple invokers. In the code above, the elements related to Dubbo SPI are:</p>
-<ul>
-<li>@SPI(<a href="http://RandomLoadBalance.NAME">RandomLoadBalance.NAME</a>) @SPI is used for LoadBalance interface, which indicates that the LoadBalance interface is an extension point. Without the @SPI annotation, if we try to load the extension, it will throw an exception. @SPI annotation has one parameter, and this parameter represents the Alias of the default implementation of the extension point. If there has no explicitly specified extension, the default implementation will be used.
-<code>RandomLoadBalance.NAME</code> is a constant with value “random” and is a random load balancing implementation. The definition of random is in the configuration file <code>META-INF/dubbo/internal/com.alibaba.dubbo.rpc.cluster.LoadBalance</code>:</li>
-</ul>
-<pre><code class="language-bash">random=com.alibaba.dubbo.rpc.cluster.loadbalance.RandomLoadBalance
-roundrobin=com.alibaba.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance
-leastactive=com.alibaba.dubbo.rpc.cluster.loadbalance.LeastActiveLoadBalance
-consistenthash=com.alibaba.dubbo.rpc.cluster.loadbalance.ConsistentHashLoadBalance
-</code></pre>
-<p>There are four extension implementations of LoadBalance defined in the configuration file. The implementation of load balancing will not be covered in this article. The only thing we need to know is that Dubbo provides four kinds of load balancing implementations. We can explicitly specify an implementation by using xml file, properties file or JVM parameter. If there has no explicitly specified implementation, Dubbo will use random as default.</p>
-<p><img src="https://raw.githubusercontent.com/vangoleo/wiki/master/dubbo/dubbo_loadbalance.png" alt="dubbo-loadbalance | left"></p>
-<ul>
-<li>@Adaptive("loadbalance") Applying @Adaptive annotation on select method indicates that select method is an adaptive method. Dubbo will automatically generate the corresponding code for the method. When select method is called, it will decide which extension to apply based on the method parameters. @Adaptive parameter <code>loadbalance</code> indicates that the value of loadbalance in method is the extension implementation that will be actually called. However, we cannot fi [...]
-</ul>
-<h3>6.2 Obtain LoadBalance extension</h3>
-<p>The code of LoadBalance in Dubbo is as follows:</p>
-<pre><code class="language-java">LoadBalance lb = ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(loadbalanceName);
-</code></pre>
-<p>Using ExtensionLoader.getExtensionLoader(LoadBalance.class) method to obtain an implementation of ExtensionLoader, then we call getExtension and pass an extension alias to obtain the corresponding extension implementation.</p>
-<h2>7. Customize a LoadBalance Extension</h2>
-<p>In this session, we will use a simple example to implement a LoadBalance and integrate it into Dubbo. I will show some important steps and codes, and the complete demo can be downloaded from the following address(<a href="https://github.com/vangoleo/dubbo-spi-demo">https://github.com/vangoleo/dubbo-spi-demo</a>).</p>
-<h3>7.1 implement LoadBalance Interface</h3>
-<p>First, we build a LoadBalance instance. Since we just need the instance to demonstrate Dubbo extension mechanism, it will be very simple. We choose the first invoker and print a log sentence in the console.</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.dubbo.spi.demo.consumer;
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoLoadBalance</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">LoadBalance</span> </span>{
- <span class="hljs-meta">@Override</span>
- <span class="hljs-keyword">public</span> <T> <span class="hljs-function">Invoker<T> <span class="hljs-title">select</span><span class="hljs-params">(List<Invoker<T>> invokers, URL url, Invocation invocation)</span> <span class="hljs-keyword">throws</span> RpcException </span>{
- System.out.println(<span class="hljs-string">"DemoLoadBalance: Select the first invoker..."</span>);
- <span class="hljs-keyword">return</span> invokers.get(<span class="hljs-number">0</span>);
- }
-}
-</code></pre>
-<h3>7.2 Add extension configuration file</h3>
-<p>Add file:<code>META-INF/dubbo/com.alibaba.dubbo.rpc.cluster.LoadBalance</code>. The content of file is:</p>
-<pre><code class="language-bash">demo=com.dubbo.spi.demo.consumer.DemoLoadBalance
-</code></pre>
-<h3>7.3 Configure customized LoadBalance</h3>
-<p>Through the above 2 steps, we have already added a LoadBalance implementation named demo, and set up the configuration file. In the next step, we need to explicitly tell Dubbo to implement the demo while doing load balancing. If we use Dubbo through spring, we could set it up in the xml file.</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:reference</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"helloService"</span> <span class="hljs-attr">interface</span>=<span class="hljs-string">"com.dubbo.spi.demo.api.IHelloService"</span> <span class="hljs-attr">loadbalance</span>=<span class="hljs-string">"demo"</span> /></span>
-</code></pre>
-<p>Configure <loadbalance="demo"> in <a href="dubbo:reference">dubbo:reference</a> at consumer part.</p>
-<h3>7.4 launch Dubbo</h3>
-<p>Launch Dubbo and call IHelloService, the console will output log: <code>DemoLoadBalance: Select the first invoker...</code>, which means Dubbo does use our customized LoadBalance.</p>
-<h2>Summary</h2>
-<p>So far, we learnt the basic concepts of Dubbo SPI beginning with Java SPI, and we used LoadBalance in Dubbo as an example to help us understand better. Finally, we practiced and created a customized LoadBalance and integrated it to Dubbo. We believe that combining concepts and practice, everyone can get a better idea of Dubbo’s scalability. To summarize, Dubbo SPI has the following features:</p>
-<ul>
-<li>Build extensions on Dubbo does not require modifications on the original source code base.</li>
-<li>The customized Dubbo extension point implementation is a normal Java class. Dubbo does not introduce any specialized elements, and have almost zero code intrusion.
-*Extension registration on Dubbo requires only configuration file under the ClassPath directory. It is simple to use and has no effect on the existing code. This meets opening/closed principle.</li>
-<li>Dubbo's extension mechanism default: @SPI("dubbo") represents the default SPI object.</li>
-<li>Dubbo's extension mechanism supports the advanced features such as IoC and AoP, etc.</li>
-<li>Dubbo's extension mechanism supports third-party IoC containers. It supports Spring beans by default and can be extended to other containers, such as Google/Guice.</li>
-<li>It is easy to switch the implementation of the extension point because it requires only modifications on the specific implementation in the configuration file without changing the code.</li>
-</ul>
-<p>In the next article, we will go deep and check Dubbo's source code to learn more about Dubbo's extensibility mechanism.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/introduction-to-dubbo-spi.json b/en-us/blog/introduction-to-dubbo-spi.json
deleted file mode 100644
index f46d9de..0000000
--- a/en-us/blog/introduction-to-dubbo-spi.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "introduction-to-dubbo-spi.md",
- "__html": "<h1>Dubbo Extension Mechanism in Action</h1>\n<h2>1. Extension Mechanism of Dubbo</h2>\n<p>Dubbo is claimed as a high-performance RPC framework on its official website. Today, I want to talk about another great specialty of Dubbo --- its scalability. As quote: Rome wasn’t built in a day. Any successful system always starts as a prototype. It is impossible to design a perfect system at the beginning. Instead, we should focus on true demand and keep improving the system. On t [...]
- "link": "/en-us/blog/introduction-to-dubbo-spi.html",
- "meta": {
- "title": "Dubbo Extension Mechanism in Action",
- "keywords": "Dubbo, SPI",
- "description": "This article introduces Dubbo's SPI mechanism."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/pinpoint.html b/en-us/blog/pinpoint.html
deleted file mode 100644
index be221c7..0000000
--- a/en-us/blog/pinpoint.html
+++ /dev/null
@@ -1,403 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Pinpoint, tracing" />
- <meta name="description" content="This article introduces how to use Pinpoint to track Dubbo applications and monitor applications' performance." />
- <!-- 网页标签标题 -->
- <title>Tracking with Pinpoint</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).</p>
-<h2>What is Pinpoint</h2>
-<p><a href="https://github.com/naver/pinpoint">Pinpoint</a> is an APM (Application Performance Management) tool for large-scale distributed systems written in Java. Inspired by Dapper, Pinpoint provides a solution to help analyze the overall structure of the system and how components within them are interconnected by tracing transactions across distributed applications.</p>
-<p>You should definitely check Pinpoint out If you want to</p>
-<p>understand your application topology at a glance
-monitor your application in Real-Time
-gain code-level visibility to every transaction
-install APM Agents without changing a single line of code
-have minimal impact on the performance (approximately 3% increase in resource usage)</p>
-<h3>ServerMap</h3>
-<p>Understand the topology of any distributed systems by visualizing how their components are interconnected. Clicking on a node reveals details about the component, such as its current status, and transaction count.</p>
-<h3>Realtime Active Thread Chart</h3>
-<p>Monitor active threads inside applications in real-time.</p>
-<h3>Request/Response Scatter Chart</h3>
-<p>Visualize request count and response patterns over time to identify potential problems. Transactions can be selected for additional detail by dragging over the chart.</p>
-<h3>CallStack</h3>
-<p>Gain code-level visibility to every transaction in a distributed environment, identifying bottlenecks and points of failure in a single view.</p>
-<h3>Inspector</h3>
-<p>View additional details on the application such as CPU usage, Memory/Garbage Collection, TPS, and JVM arguments.</p>
-<h3>Supported Modules (last updated 2018/04/01)</h3>
-<ul>
-<li>JDK 6+</li>
-<li>Tomcat 6/7/8, Jetty 8/9, JBoss EAP 6, Resin 4, Websphere 6/7/8, Vertx 3.3/3.4/3.5</li>
-<li>Spring, Spring Boot (Embedded Tomcat, Jetty)</li>
-<li>Apache HTTP Client 3.x/4.x, JDK HttpConnector, GoogleHttpClient, OkHttpClient, NingAsyncHttpClient</li>
-<li>Thrift Client, Thrift Service, DUBBO PROVIDER, DUBBO CONSUMER</li>
-<li>ActiveMQ, RabbitMQ</li>
-<li>MySQL, Oracle, MSSQL, CUBRID,POSTGRESQL, MARIA</li>
-<li>Arcus, Memcached, Redis, CASSANDRA</li>
-<li>iBATIS, MyBatis</li>
-<li>DBCP, DBCP2, HIKARICP</li>
-<li>gson, Jackson, Json Lib</li>
-<li>log4j, Logback</li>
-</ul>
-<h2>Pinpoint and Dubbo</h2>
-<h3>Quickstart Pinpoint</h3>
-<p><a href="http://naver.github.io/pinpoint/quickstart.html">Quick start</a>（No neet to start TestApp）</p>
-<h3>Dubbo demo</h3>
-<h4>Create API module</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span>
- <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<p>Create API interface：</p>
-<pre><code>package com.example.demoapi;
-
-public interface HelloService {
- String sayHello(String name);
-}
-</code></pre>
-<h4>Dubbo provider</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span> <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-provider<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">packaging</span>></span>jar<span class="hljs-tag"></<span class="hljs-name">packaging</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">name</span>></span>demo-provider<span class="hljs-tag"></<span class="hljs-name">name</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">parent</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-parent<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>2.0.3.RELEASE<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">relativePath</span>/></span> <span class="hljs-comment"><!-- lookup parent from repository --></span>
- <span class="hljs-tag"></<span class="hljs-name">parent</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">properties</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.build.sourceEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.build.sourceEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.reporting.outputEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.reporting.outputEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">java.version</span>></span>1.8<span class="hljs-tag"></<span class="hljs-name">java.version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">properties</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">repositories</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>sonatype-nexus-snapshots<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">url</span>></span>https://oss.sonatype.org/content/repositories/snapshots<span class="hljs-tag"></<span class="hljs-name">url</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>false<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>true<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repositories</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependencies</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.alibaba.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>dubbo-spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.2.0<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-test<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">scope</span>></span>test<span class="hljs-tag"></<span class="hljs-name">scope</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependencies</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">build</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-maven-plugin<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">build</span>></span>
-
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<ol>
-<li><code>HelloService</code> interface：</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.demoprovider.provider;
-
-<span class="hljs-keyword">import</span> com.alibaba.dubbo.config.annotation.Service;
-<span class="hljs-keyword">import</span> com.example.demoapi.HelloService;
-
-<span class="hljs-meta">@Service</span>(version = <span class="hljs-string">"${demo.service.version}"</span>,
- application = <span class="hljs-string">"${dubbo.application.id}"</span>,
- protocol = <span class="hljs-string">"${dubbo.protocol.id}"</span>,
- registry = <span class="hljs-string">"${dubbo.registry.id}"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">HelloServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">HelloService</span> </span>{
- <span class="hljs-keyword">static</span> <span class="hljs-keyword">int</span> i = <span class="hljs-number">0</span>;
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- i++;
- <span class="hljs-keyword">if</span> (i % <span class="hljs-number">3</span> == <span class="hljs-number">0</span>) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> RuntimeException(<span class="hljs-string">"ex"</span>);
- }
- <span class="hljs-keyword">return</span> <span class="hljs-string">"Hello "</span> + name + <span class="hljs-string">"!"</span>;
- }
-}
-</code></pre>
-<ol start="2">
-<li>Spring Boot bootstrap：</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.demoprovider;
-
-<span class="hljs-keyword">import</span> org.springframework.boot.SpringApplication;
-<span class="hljs-keyword">import</span> org.springframework.boot.autoconfigure.SpringBootApplication;
-
-<span class="hljs-meta">@SpringBootApplication</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoProviderApplication</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- SpringApplication.run(DemoProviderApplication.class, args);
- }
-}
-</code></pre>
-<ol start="3">
-<li><code>application.properties</code>：</li>
-</ol>
-<pre><code class="language-properties"><span class="hljs-comment"># Spring boot application</span>
-<span class="hljs-meta">spring.application.name</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-meta">server.port</span> = <span class="hljs-string">9090</span>
-<span class="hljs-meta">management.port</span> = <span class="hljs-string">9091</span>
-<span class="hljs-comment">
-# Service version</span>
-<span class="hljs-meta">demo.service.version</span> = <span class="hljs-string">1.0.0</span>
-<span class="hljs-comment">
-# Base packages to scan Dubbo Components (e.g @Service , @Reference)</span>
-<span class="hljs-meta">dubbo.scan.basePackages</span> = <span class="hljs-string">com.example.demoprovider</span>
-<span class="hljs-comment">
-# Dubbo Config properties</span>
-<span class="hljs-comment">## ApplicationConfig Bean</span>
-<span class="hljs-meta">dubbo.application.id</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-meta">dubbo.application.name</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-comment">
-## ProtocolConfig Bean</span>
-<span class="hljs-meta">dubbo.protocol.id</span> = <span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.name</span> = <span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.port</span> = <span class="hljs-string">12345</span>
-<span class="hljs-comment">
-## RegistryConfig Bean</span>
-<span class="hljs-meta">dubbo.registry.id</span> = <span class="hljs-string">my-registry</span>
-<span class="hljs-meta">dubbo.registry.address</span> = <span class="hljs-string">N/A</span>
-</code></pre>
-<h4>Dubbo consumer</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span> <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-consumer<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">packaging</span>></span>jar<span class="hljs-tag"></<span class="hljs-name">packaging</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">name</span>></span>demo-consumer<span class="hljs-tag"></<span class="hljs-name">name</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">parent</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-parent<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>2.0.3.RELEASE<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">relativePath</span>/></span> <span class="hljs-comment"><!-- lookup parent from repository --></span>
- <span class="hljs-tag"></<span class="hljs-name">parent</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">properties</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.build.sourceEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.build.sourceEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.reporting.outputEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.reporting.outputEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">java.version</span>></span>1.8<span class="hljs-tag"></<span class="hljs-name">java.version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">properties</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">repositories</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>sonatype-nexus-snapshots<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">url</span>></span>https://oss.sonatype.org/content/repositories/snapshots<span class="hljs-tag"></<span class="hljs-name">url</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>false<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>true<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repositories</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependencies</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-web<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.alibaba.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>dubbo-spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.2.0<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-test<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">scope</span>></span>test<span class="hljs-tag"></<span class="hljs-name">scope</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependencies</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">build</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-maven-plugin<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">configuration</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">classifier</span>></span>exec<span class="hljs-tag"></<span class="hljs-name">classifier</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">configuration</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">build</span>></span>
-
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<ol>
-<li><code>@Reference</code> injection <code>HelloService</code></li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.democonsumer.controller;
-
-<span class="hljs-keyword">import</span> com.alibaba.dubbo.config.annotation.Reference;
-<span class="hljs-keyword">import</span> com.example.demoapi.HelloService;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RequestMapping;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RequestParam;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RestController;
-
-<span class="hljs-meta">@RestController</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoConsumerController</span> </span>{
- <span class="hljs-meta">@Reference</span>(version = <span class="hljs-string">"${demo.service.version}"</span>,
- application = <span class="hljs-string">"${dubbo.application.id}"</span>,
- url = <span class="hljs-string">"dubbo://<Real IP Address>:12345"</span>)
- <span class="hljs-keyword">private</span> HelloService helloService;
-
- <span class="hljs-meta">@RequestMapping</span>(<span class="hljs-string">"/sayHello"</span>)
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(@RequestParam String name)</span> </span>{
- <span class="hljs-keyword">return</span> helloService.sayHello(name);
- }
-}
-</code></pre>
-<ol start="2">
-<li>Spring Boot bootstrap:</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.democonsumer;
-
-<span class="hljs-keyword">import</span> org.springframework.boot.SpringApplication;
-<span class="hljs-keyword">import</span> org.springframework.boot.autoconfigure.SpringBootApplication;
-
-<span class="hljs-meta">@SpringBootApplication</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoConsumerApplication</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- SpringApplication.run(DemoConsumerApplication.class, args);
- }
-}
-</code></pre>
-<ol start="3">
-<li><code>application.properties</code>:</li>
-</ol>
-<pre><code class="language-properties"><span class="hljs-comment"># Spring boot application</span>
-<span class="hljs-meta">spring.application.name</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-meta">server.port</span>=<span class="hljs-string">8080</span>
-<span class="hljs-meta">management.port</span>=<span class="hljs-string">8081</span>
-<span class="hljs-comment">
-# Service Version</span>
-<span class="hljs-meta">demo.service.version</span>=<span class="hljs-string">1.0.0</span>
-<span class="hljs-comment">
-# Dubbo Config properties</span>
-<span class="hljs-comment">## ApplicationConfig Bean</span>
-<span class="hljs-meta">dubbo.application.id</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-meta">dubbo.application.name</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-comment">
-## ProtocolConfig Bean</span>
-<span class="hljs-meta">dubbo.protocol.id</span>=<span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.name</span>=<span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.port</span>=<span class="hljs-string">12345</span>
-</code></pre>
-<h3>Using Pinpoint-agent to start <code>Dubbo provider</code> and <code>Dubbo consumer</code></h3>
-<ol>
-<li>Maven clean package</li>
-</ol>
-<pre><code>mvn clean package
-</code></pre>
-<ol start="2">
-<li>Start provider</li>
-</ol>
-<pre><code>java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-provider -Dpinpoint.applicationName=DP target/demo-provider-0.0.1-SNAPSHOT.jar
-</code></pre>
-<ol start="3">
-<li>Start consumer</li>
-</ol>
-<pre><code>java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-consumer -Dpinpoint.applicationName=DC target/demo-comsumer-0.0.1-SNAPSHOT-exec.jar
-</code></pre>
-<ol start="4">
-<li>Access the consumer address to simulate user requests</li>
-</ol>
-<p><code>http://localhost:8080/sayHello?name=ABC</code></p>
-<h2>Using Pinpoint locate problems</h2>
-<h3>Homepage</h3>
-<p><img src="../../img/blog/en_pinpoint-home.png" alt="/admin-guide/images/pinpoint-home.png"></p>
-<blockquote>
-<p>The user request here is double the number of requests for DubboProvider, because the favicon.ico icon request is recorded.</p>
-</blockquote>
-<h3>Call tree</h3>
-<p><img src="../../img/blog/en_pinpoint-calltree.png" alt="/admin-guide/images/pinpoint-calltree.png"></p>
-<h3>Mixed view</h3>
-<p><img src="../../img/blog/en_pinpoint-mixedview.png" alt="/admin-guide/images/pinpoint-mixedview.png"></p>
-<h3>Other</h3>
-<p>The example simply simulates the provision and call of Dubbo, and does not carry out the application of other middleware such as database. For detailed use, please refer to the Pinpoint document.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/pinpoint.json b/en-us/blog/pinpoint.json
deleted file mode 100644
index 80cf5c9..0000000
--- a/en-us/blog/pinpoint.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "pinpoint.md",
- "__html": "<h1>Tracking with Pinpoint</h1>\n<p>After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).< [...]
- "link": "/en-us/blog/pinpoint.html",
- "meta": {
- "title": "Tracking with Pinpoint",
- "keywords": "Dubbo, Pinpoint, tracing",
- "description": "This article introduces how to use Pinpoint to track Dubbo applications and monitor applications' performance."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/prepare-an-apache-release.html b/en-us/blog/prepare-an-apache-release.html
deleted file mode 100644
index a0d2182..0000000
--- a/en-us/blog/prepare-an-apache-release.html
+++ /dev/null
@@ -1,489 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Apache, Release" />
- <meta name="description" content="This article introduces how to the Apache publish content and process" />
- <!-- 网页标签标题 -->
- <title>Understanding the Apache Release Cycle</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Understanding the Apache Release Cycle</h2>
-<p>In general, Source Release is the key and the required content of Apache. But Binary Release is optional, Dubbo can choose whether to release binary packages to the Apache repository or to the Maven central repository.</p>
-<p>Please refer to the following links for more information on ASF's release guide:</p>
-<ul>
-<li><a href="http://www.apache.org/dev/release-publishing">Apache Release Guide</a></li>
-<li><a href="http://www.apache.org/dev/release.html">Apache Release Policy</a></li>
-<li><a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Maven Release Info</a></li>
-</ul>
-<h2>Preparation of Local Building Environment</h2>
-<p>Mainly including the related preparation of signature utilities and Maven repository certification</p>
-<ol>
-<li>
-<p>Install GPG,refer to <a href="https://www.gnupg.org/download/index.html">https://www.gnupg.org/download/index.html</a></p>
-<ul>
-<li>For example, in Mac OS</li>
-</ul>
-<pre><code class="language-sh">$ brew install gpg
-$ gpg --version <span class="hljs-comment">#check version,should be 2.x</span>
-</code></pre>
-</li>
-<li>
-<p>Generate the key with GPG</p>
-<ul>
-<li>Generate the key according to the prompt</li>
-</ul>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> gpg2 --full-gen-key</span>
-gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc.
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.
-
-Please select what kind of key you want:
- (1) RSA and RSA (default)
- (2) DSA and Elgamal
- (3) DSA (sign only)
- (4) RSA (sign only)
-Your selection? 1
-RSA keys may be between 1024 and 4096 bits long.
-What keysize do you want? (2048) 4096
-Requested keysize is 4096 bits
-Please specify how long the key should be valid.
- 0 = key does not expire
- <n> = key expires in n days
- <n>w = key expires in n weeks
- <n>m = key expires in n months
- <n>y = key expires in n years
-Key is valid for? (0)
-Key does not expire at all
-Is this correct? (y/N) y
-
-GnuPG needs to construct a user ID to identify your key.
-
-Real name: Robert Burrell Donkin
-Email address: rdonkin@apache.org
-Comment: CODE SIGNING KEY
-You selected this USER-ID:
- "Robert Burrell Donkin (CODE SIGNING KEY) <rdonkin@apache.org>"
-
-Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
-You need a Passphrase to protect your secret key. # enter the password, which will be used frequently when packaging.
-</code></pre>
-<ul>
-<li>View key id</li>
-</ul>
-<pre><code class="language-sh">$ gpg --list-keys
-pub rsa4096/28681CB1 2018-04-26 <span class="hljs-comment"># 28681CB1 is the key id</span>
-uid [ultimate] liujun (apache-dubbo) <liujun@apache.org>
-sub rsa4096/D3D6984B 2018-04-26
-
-<span class="hljs-comment">########### Note: Different diaplay for different version.</span>
-$ gpg --list-keys
-pub rsa4096 2018-11-12 [SC]
- 63AAE9838F4A303E40BAF5FEA3A1CA7A5D4A3981 <span class="hljs-comment"># Last 8 character(5D4A3981) as key id，it will be used when send public key to keyserver</span>
-uid [ 绝对 ] Victory Cao (CODE SIGNING KEY) <victory@apache.org>
-sub rsa4096 2018-11-12 [E]
-
-
-<span class="hljs-comment"># send public key to keyserver via key id </span>
-$ gpg --keyserver pgpkeys.mit.edu --send-key 28681CB1
-<span class="hljs-comment"># Here pgpkeys.mit.edu is a random selection of keyserver. Any key server from the list https://sks-keyservers.net/status/ is acceptable because they are automatically synchronized.</span>
-</code></pre>
-<ul>
-<li>If there are multiple public keys，you can set the default key</li>
-</ul>
-<p>~/.gnupg/gpg.conf</p>
-<pre><code class="language-proper"># If you have more than 1 secret key in your keyring, you may want to
-# uncomment the following option and set your preferred keyid.
-
-default-key 28681CB1
-</code></pre>
-<ul>
-<li>If there are multiple public keys, you can also delete unuseful key：</li>
-</ul>
-<pre><code class="language-sh"><span class="hljs-comment">### Delete the private key first, then delete the public key.</span>
-
-$ gpg --yes --delete-secret-keys shenglicao2@gmail.com <span class="hljs-comment">### indicate email address </span>
-
-$ gpg --delete-keys 1808C6444C781C0AEA0AAD4C4D6A8007D20DB8A4
-
-</code></pre>
-</li>
-<li>
-<p>Set up Apache central repository.</p>
-<ul>
-<li>The parent pom of Dubbo project is apache pom</li>
-</ul>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">parent</span>></span>
-<span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.apache<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
-<span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>apache<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
-<span class="hljs-tag"><<span class="hljs-name">version</span>></span>19<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">parent</span>></span>
-</code></pre>
-<ul>
-<li>
-<p>Add the following contents to .m2/settings.xml</p>
-<p>Enter the passwords after
-encrypting by <a href="http://maven.apache.org/guides/mini/guide-encryption.html">maven-encryption-plugin</a></p>
-</li>
-</ul>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">settings</span>></span>
-...
- <span class="hljs-tag"><<span class="hljs-name">servers</span>></span>
- <span class="hljs-comment"><!-- To publish a snapshot of some part of Maven --></span>
- <span class="hljs-tag"><<span class="hljs-name">server</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>apache.snapshots.https<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">username</span>></span> <span class="hljs-comment"><!-- YOUR APACHE LDAP USERNAME --></span> <span class="hljs-tag"></<span class="hljs-name">username</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">password</span>></span> <span class="hljs-comment"><!-- YOUR APACHE LDAP PASSWORD (encrypted) --></span> <span class="hljs-tag"></<span class="hljs-name">password</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">server</span>></span>
- <span class="hljs-comment"><!-- To stage a release of some part of Maven --></span>
- <span class="hljs-tag"><<span class="hljs-name">server</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>apache.releases.https<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">username</span>></span> <span class="hljs-comment"><!-- YOUR APACHE LDAP USERNAME --></span> <span class="hljs-tag"></<span class="hljs-name">username</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">password</span>></span> <span class="hljs-comment"><!-- YOUR APACHE LDAP PASSWORD (encrypted) --></span> <span class="hljs-tag"></<span class="hljs-name">password</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">server</span>></span>
- ...
- <span class="hljs-comment"><!-- gpg passphrase used when generate key --></span>
- <span class="hljs-tag"><<span class="hljs-name">server</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>gpg.passphrase<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">passphrase</span>></span><span class="hljs-comment"><!-- yourKeyPassword --></span><span class="hljs-tag"></<span class="hljs-name">passphrase</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">server</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">servers</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">settings</span>></span>
-</code></pre>
-</li>
-</ol>
-<h2>Pack & Upload</h2>
-<ol>
-<li>
-<p>Pull the new branch from the master branch as the release branch. If you want to release the ${release_version} version now, pull the new branch ${release_version}-release from 2.6.x. Then the
-modifications and taggings related to ${release_version} Release Candidates are applied to ${release_version}-release branch, and is merged into the master branch after the final release.</p>
-</li>
-<li>
-<p>First of all, verify that the maven component packing, source packing, signature, etc are working properly on the ${release_version}-release branch.</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> mvn clean install -Papache-release</span>
-<span class="hljs-meta">$</span><span class="bash"> mvn deploy</span>
-</code></pre>
-</li>
-</ol>
-<p>This push the snapshot package to the maven central repository.</p>
-<ol start="3">
-<li>
-<p>Release with maven-release-plugin</p>
-<ul>
-<li>verify with dryRun</li>
-</ul>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> mvn release:prepare -Prelease -Darguments=<span class="hljs-string">"-Dmaven.test.skip=true"</span> -DautoVersionSubmodules=<span class="hljs-literal">true</span> -Dusername=YOUR GITHUB ID -DdryRun=<span class="hljs-literal">true</span></span>
-</code></pre>
-<ul>
-<li>After verification, run release:prepare</li>
-</ul>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> mvn release:clean</span>
-<span class="hljs-meta">$</span><span class="bash"> mvn release:prepare -Prelease -Darguments=<span class="hljs-string">"-Dmaven.test.skip=true"</span> -DautoVersionSubmodules=<span class="hljs-literal">true</span> -Dusername=YOUR GITHUB ID -DpushChanges=<span class="hljs-literal">false</span></span>
-</code></pre>
-<blockquote>
-<p>If you are promted to input password for pushing to GitHub (basically including adding new commits and tags), do not input your login password of GitHub. Use <code>Personal access tokens</code> instead. You can go to <a href="https://github.com/settings/profile">https://github.com/settings/profile</a>, click <code>Developer settings</code> -> <code>Personal access tokens</code>, and generate a new token if not. Please refer to this <a href="https://help.github.com/articles/creating [...]
-you need to choose the release artifactId, next artifactId and the release tag, the default tag is dubbo-parent-xxxx, you need to change it to dubbo-xxxx</p>
-</blockquote>
-<p>After executing the above commands, you will find that:</p>
-<ol>
-<li>source-release.zip and bin-release.zip are generated under dubbo-distribution directory, please unzip it and check the file structure</li>
-<li><code>-DpushChanges=false</code> tells maven not to push the commits and tags to the remote repostiroy. If not specified, the version tag will be pushed to github repository, you will see a commit called <code>[maven-release-plugin] prepare release dubbo-x.x.x</code> added.</li>
-<li>The branch version is upgraded to ${release_version+1}-SNAPSHOT automatically. If <code>-DpushChanges=true</code> is specified, the modifications will be pushed to the remote repository, you will see a commit called <code>[maven-release-plugin] prepare for next development iteration</code> added.</li>
-</ol>
-<p>If <code>-DpushChanges=false</code> is specified, you will have to manually push the commit to remote repository before go to next step.</p>
-<ul>
-<li>Run release:perform</li>
-</ul>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> mvn release:perform -Prelease -Darguments=<span class="hljs-string">"-Dmaven.test.skip=true"</span> -DautoVersionSubmodules=<span class="hljs-literal">true</span> -Dusername=YOUR GITHUB ID</span>
-</code></pre>
-<p>Maven will download the source code from the tag you just pushed, compile it, and deploy to remote maven repsoitry in staging state.</p>
-</li>
-</ol>
-<h3>Note</h3>
-<blockquote>
-<p>When you deploy the package into repository, it will be interrupted for network. So you must restart to desploy.<br>
-The problem is that missing package occurred many times at deploying. So you should check the quantity of package, especially parent package.</p>
-</blockquote>
-<h2>Prepare Apache Release</h2>
-<ol>
-<li>
-<p>Prepare the svn local environment (Apache hosting the release content of project by svn)</p>
-</li>
-<li>
-<p>Checkout dubbo to local directory</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> svn checkout https://dist.apache.org/repos/dist/dev/incubator/dubbo</span>
-</code></pre>
-<p>Assume that the local directory is <code>~/apache/incubator/dubbo</code></p>
-</li>
-<li>
-<p>The current release version is ${release_version}, new directory</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> <span class="hljs-built_in">cd</span> ~/apache/incubator/dubbo <span class="hljs-comment"># dubbo svn root directory</span></span>
-<span class="hljs-meta">$</span><span class="bash"> mkdir <span class="hljs-variable">${release_version}</span></span>
-</code></pre>
-</li>
-<li>
-<p>Add public key to <a href="https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS">KEYS</a> file if you are the first time to be a release manager. KEYS is mainly used to allow people who participate in the voting to be imported locally to verify the correctness of the sign.</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> gpg -a --<span class="hljs-built_in">export</span> your_key_id >> KEYS</span>
-</code></pre>
-<p>For more information on how to get your key id, please refer to this <a href="https://help.github.com/articles/generating-a-new-gpg-key/">guide</a></p>
-</li>
-<li>
-<p>Copy the source.zip package from the Dubbo root directory to the svn local repository dubbo/${release_version}</p>
-</li>
-<li>
-<p>Generate sha512 sign</p>
-<p>For source-release.zip</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> shasum -a 512 apache-dubbo-<span class="hljs-variable">${release_version}</span>-<span class="hljs-built_in">source</span>-release.zip >> apache-dubbo-<span class="hljs-variable">${release_version}</span>-<span class="hljs-built_in">source</span>-release.zip.sha512</span>
-</code></pre>
-<p>For bin-release.zip</p>
-<p>Please add <code>-b</code> paramter when generating sha512 for bin-release.zip, which indicates it is a binary file.</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> shasum -b -a 512 apache-dubbo-<span class="hljs-variable">${release_version}</span>-bin-release.zip >> apache-dubbo-<span class="hljs-variable">${release_version}</span>-bin-release.zip.sha512</span>
-</code></pre>
-<p>You should generate something like this:</p>
-<pre><code>b8f13d1df6d6c9a1facc72fafc00b2d22bea1e600517c507467d8fca2f776a7a3877101742da53114bfa629ca5b941eb4d9ef989de43f0833e2a794e7ccf5c8a *apache-dubbo-spring-boot-project-2.7.0-bin-release.zip
-</code></pre>
-<p>Note there is a <code>*</code> sign before the file name.</p>
-</li>
-<li>
-<p>If the binary release is accompanied with the source release. Run the following command in the dubbo-distribution module:</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> mvn install</span>
-</code></pre>
-<p>Go to target directory, copy bin-release.zip and bin-release.zip.asc to svn local repository dubbo/${release_version}, and refer to step 6 to generate sha512 sign.</p>
-</li>
-<li>
-<p>Commit to Apache svn</p>
-<pre><code class="language-shell"><span class="hljs-meta">$</span><span class="bash"> svn status</span>
-<span class="hljs-meta">$</span><span class="bash"> svn commit -m <span class="hljs-string">'prepare for ${release_version} RC1'</span></span>
-</code></pre>
-</li>
-</ol>
-<h2>Verify Release Candidates</h2>
-<p><strong>A full check list can be found <a href="https://wiki.apache.org/incubator/IncubatorReleaseChecklist">here</a></strong></p>
-<p>The verification link includes but is not limited to the following contents and forms:</p>
-<h3>Check signatures and hashes are good</h3>
-<h4>check the sha512 sum</h4>
-<pre><code class="language-sh">$ shasum -c apache-dubbo-<span class="hljs-variable">${release_version}</span>-<span class="hljs-built_in">source</span>-release.zip.sha512
-$ shasum -c apache-dubbo-<span class="hljs-variable">${release_version}</span>-bin-release.zip.sha512
-</code></pre>
-<h4>check the gpg signarure</h4>
-<p>If it's your first time verify a release candidte, you should import public keys first.</p>
-<pre><code class="language-sh"> $ curl https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS >> KEYS <span class="hljs-comment"># download public keys to local directory</span>
- $ gpg --import KEYS <span class="hljs-comment"># import keys</span>
- $ gpg —edit-key liujun
- > trust <span class="hljs-comment"># type trust command</span>
-</code></pre>
-<p>Now, you can verify signature with command</p>
-<pre><code class="language-sh">gpg --verify apache-dubbo-2.6.3-source-release.zip.asc apache-dubbo-2.6.3-source-release.zip
-gpg --verify apache-dubbo-2.6.3-bin-release.zip.asc apache-dubbo-2.6.3-bin-release.zip
-</code></pre>
-<h3>Check source release file content</h3>
-<p>Unzip apache-dubbo-${release_version}-source-release.zip to the default directory and check the following:</p>
-<ul>
-<li>Directory with 'incubating' in name
-<code>apache-dubbo-${release_version}-source-release</code></li>
-<li>DISCLAIMER exists</li>
-<li>LICENSE and NOTICE exists and contents are good</li>
-<li>All files and no binary files exist</li>
-<li>All files has standard ASF License header</li>
-<li>Can compile from source</li>
-<li>All unit tests can pass<pre><code class="language-sh">mvn clean <span class="hljs-built_in">test</span> <span class="hljs-comment"># This will run all unit tests</span>
-<span class="hljs-comment"># you can also open rat and style plugin to check if every file meets requirements.</span>
-mvn clean <span class="hljs-built_in">test</span> -Drat.skip=<span class="hljs-literal">false</span> -Dcheckstyle.skip=<span class="hljs-literal">false</span>
-</code></pre>
-</li>
-<li>Release candidates match with corresponding tags, you can find tag link and hash in vote email.
-<ul>
-<li>check the version number in pom.xml are the same</li>
-<li>check there are no extra files or directories in the source package, for example, no empty directories or useless log files.<br>
-<code>diff -r rc_dir tag_dir</code></li>
-<li>check the top n tag commits, dive into the related files and check if the source package has the same changes</li>
-</ul>
-</li>
-</ul>
-<h3>Check binary distribution file content</h3>
-<p>Unzip apache-dubbo-${release_version}-bin-release.zip and check:</p>
-<ul>
-<li>Check signatures are good</li>
-<li>'incubating' in name</li>
-<li>LICENSE and NOTICE exists and contents are good</li>
-</ul>
-<p>Note that if the binary distribution contains third party files, you may need to update LICENSE file by adding the 3rd party license files. If these dependency is Apache License 2.0, and it contains NOTICE file, you may also need to update NOTICE file as well.</p>
-<h2>Release vote</h2>
-<p>The voting is divided into two phases:</p>
-<ol>
-<li>Dubbo community votes and sends the voting email to <a href="mailto:dev@dubbo.apache.org">dev@dubbo.apache.org</a>. After reviewing by community developers and winning 3 binding tickets that agree to release, you can go to the next stage of voting.</li>
-<li>Apache community votes and sends the voting email to <a href="mailto:general@incubator.apache.org">general@incubator.apache.org</a>. After reviewing by Apache IPMC(Incubator PMC) members and winning 3 binding votes that agree to release, you will be allowed to release officially.</li>
-</ol>
-<p>The mail template for Apache Dubbo vote：</p>
-<pre><code class="language-tex">Hello Dubbo Community,
-
-This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2.
-
-The release candidates:
-https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/
-
-Git tag for the release:
-https://github.com/apache/dubbo/tree/dubbo-2.6.2
-
-Hash for the release tag:
-afab04c53edab38d52275d2a198ea1aff7a4f41e
-
-Release Notes:
-https://github.com/apache/dubbo/releases/tag/untagged-4775c0a22c60fca55118
-
-The artifacts have been signed with Key : 28681CB1, which can be found in the keys file:
-https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
-
-The vote will be open for at least 72 hours or until necessary number of votes are reached.
-
-Please vote accordingly:
-
-[ ] +1 approve
-[ ] +0 no opinion
-[ ] -1 disapprove with the reason
-
-Thanks,
-The Apache Dubbo (Incubating) Team
-</code></pre>
-<p>The mail template for Apache Incubator vote：</p>
-<pre><code class="language-text">Hello all,
-
-This is a call for vote to release Apache Dubbo (Incubating) version 2.6.4.
-
-The Apache Dubbo community has voted on and approved a proposal to release
-Apache Dubbo (Incubating) version 2.6.4.
-
-We now kindly request the Incubator PMC members review and vote on this
-incubator release.
-
-Apache Dubbo™ is a high-performance, java based, open source
-RPC framework. Dubbo offers three key functionalities, which include
-interface based remote call, fault tolerance & load balancing, and
-automatic service registration & discovery.
-
-Dubbo community vote and result thread:
-https://lists.apache.org/thread.html/8d5c39eece6288beed2e22ca976350728c571d2a9cef1c9a9e56a409@%3Cdev.dubbo.apache.org%3E
-A minor issue also can be found in the above thread.
-
-The release candidates (RC1):
-https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.4
-
-Git tag for the release (RC1):
-https://github.com/apache/dubbo/tree/dubbo-2.6.4
-
-Hash for the release tag:
-88037747a3b69d3225c73f6fbcda36ebd8435887
-
-Release Notes:
-*https://github.com/apache/dubbo/blob/dubbo-2.6.4/CHANGES.md
-<https://github.com/apache/dubbo/blob/dubbo-2.6.4/CHANGES.md>*
-
-The artifacts have been signed with Key : 7955FB6D1DD21CF7, which can be
-found in the keys file:
-https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
-
-Look at here for how to verify this release candidate:
-https://github.com/apache/dubbo-website/blob/asf-site/blog/en-us/prepare-an-apache-release.md#prepare-apache-release
-
-The vote will be open for at least 72 hours or until necessary number of
-votes are reached.
-
-Please vote accordingly:
-[ ] +1 approve
-[ ] +0 no opinion
-[ ] -1 disapprove with the reason
-
-Thanks,
-The Apache Dubbo (Incubating) Team
-</code></pre>
-<p>The mail template to announce the vote result:</p>
-<pre><code class="language-text">We’ve received 3 +1 binding votes and one +1 non-binding vote:
-
-+1 binding, Ian Luo
-+1 binding, Huxing Zhang
-+1 binding, Jun Liu
-
-+1 non-binding, Jerrick
-
-I will create a new vote thread in Apache community now.
-
-Best regards,
-The Apache Dubbo (Incubating) Team
-</code></pre>
-<h2>Official Release</h2>
-<p>When the release vote has passed,</p>
-<ol>
-<li>Add the release files to <a href="https://dist.apache.org/repos/dist/release/incubator/dubbo">official release directory</a></li>
-<li>Remove the release files in <a href="https://dist.apache.org/repos/dist/dev/incubator/dubbo">dev directory</a></li>
-<li>Remove the the release file for the previous release under <a href="https://dist.apache.org/repos/dist/release/incubator/dubbo/">official release directory</a>, which will be archived and can be found <a href="https://archive.apache.org/dist/incubator/dubbo/">here</a></li>
-<li>Publish <a href="https://github.com/apache/dubbo/releases">release notes</a> on Github.</li>
-<li>Update the recommend dependency on <a href="https://github.com/apache/dubbo#maven-dependency">Github</a> to the latest version, also update the version in other place if necessary.</li>
-<li>Add the download link to official website <a href="http://dubbo.apache.org/en-us/blog/download.html">http://dubbo.apache.org/en-us/blog/download.html</a>, using the ASF mirror system. The latest release download link should be something like <a href="https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/$VERSION/apache-dubbo-$VERSION-source-release.zip">this</a>. The download link for the previous release version should be changed like <a href="https://archive.apache.org/dist/in [...]
-<li>Make sure all the commits in the release branch are merged into master branch, and then remove the remote release branch. For example: <code>git push origin --delete 2.7.0-release</code></li>
-<li>Send mail to <a href="mailto:dev@dubbo.apache.org">dev@dubbo.apache.org</a> and <a href="mailto:general@incubator.apache.org">general@incubator.apache.org</a>, notify the community that the release is completed.
-The mail template to announce release:</li>
-</ol>
-<pre><code class="language-text">Hello Community,
-
-The Apache Dubbo team is pleased to announce that the
-2.6.6 has just been released.
-
-Apache Dubbo™ is a high-performance, java based, open source
-RPC framework. Dubbo offers three key functionalities, which include
-interface based remote call, fault tolerance & load balancing, and
-automatic service registration & discovery.
-
-Both the source release[1] and the maven binary release[2] are available
-now, you can also find the detailed release notes in here[3].
-
-
-If you have any usage questions, or have problems when upgrading or find
-any problems about enhancements included in this release, please don’t
-hesitate to let us know by sending feedback to this mailing list or filing
-an issue on GitHub[4].
-
-
-
-=====
-*Disclaimer*
-
-Apache Dubbo is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet [...]
-
-
-[1] http://dubbo.apache.org/en-us/blog/download.html
-[2] http://central.maven.org/maven2/com/alibaba/dubbo
-[3] https://github.com/apache/dubbo/releases
-[4] https://github.com/apache/dubbo/issues
-
-</code></pre>
-<h2>Complete Maven Convenient Binary release</h2>
-<p><strong><a href="https://repository.apache.org/">repository.apache.org</a> The permissions of the nexus repository have been applied, see <a href="https://issues.apache.org/jira/browse/INFRA-16451">jira</a>。</strong></p>
-<p>To release the maven artifacts, go to <a href="https://repository.apache.org">repository.apache.org</a>, and choose the staging repository, click the release button. Wait for a moment and verify it at <a href="https://repository.apache.org/content/repositories/releases/org/apache/dubbo/">here</a>, make sure your artifacts are there and correct. It will take some time to sync to maven central repository. You can verify it at <a href="https://repo.maven.apache.org/maven2/org/apache/dubb [...]
-<h2>FAQ</h2>
-<h4>gpg: signing failed: Inappropriate ioctl for device</h4>
-<p>If you've encoutered this error, try the following commands:</p>
-<pre><code>export GPG_TTY=$(tty)
-</code></pre>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/prepare-an-apache-release.json b/en-us/blog/prepare-an-apache-release.json
deleted file mode 100644
index adb0d68..0000000
--- a/en-us/blog/prepare-an-apache-release.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "prepare-an-apache-release.md",
- "__html": "<h1>How to prepare an the Apache Release</h1>\n<h2>Understanding the Apache Release Cycle</h2>\n<p>In general, Source Release is the key and the required content of Apache. But Binary Release is optional, Dubbo can choose whether to release binary packages to the Apache repository or to the Maven central repository.</p>\n<p>Please refer to the following links for more information on ASF's release guide:</p>\n<ul>\n<li><a href=\"http://www.apache.org/dev/release-publishing\"> [...]
- "link": "/en-us/blog/prepare-an-apache-release.html",
- "meta": {
- "title": "Understanding the Apache Release Cycle",
- "keywords": "Dubbo, Apache, Release",
- "description": "This article introduces how to the Apache publish content and process"
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/qcon-beijing-2018.html b/en-us/blog/qcon-beijing-2018.html
deleted file mode 100644
index 5644491..0000000
--- a/en-us/blog/qcon-beijing-2018.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, roadmap, QCon Beijing" />
- <meta name="description" content="This article will introduce you that Dubbo roadmap is announced in QCon Beijing 2018." />
- <!-- 网页标签标题 -->
- <title>Dubbo roadmap is announced in QCon Beijing 2018</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>Ian Luo has delivered a great talk at QCon Beijing 2018, where the roadmap of Dubbo has also be announced. Please enjoy the <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/qcon2018/dubbo-present-and-future.pdf">slides</a>!</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/qcon-beijing-2018.json b/en-us/blog/qcon-beijing-2018.json
deleted file mode 100644
index 6ff4dc1..0000000
--- a/en-us/blog/qcon-beijing-2018.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "qcon-beijing-2018.md",
- "__html": "<h2>Dubbo roadmap is announced in QCon Beijing 2018</h2>\n<p>Ian Luo has delivered a great talk at QCon Beijing 2018, where the roadmap of Dubbo has also be announced. Please enjoy the <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/qcon2018/dubbo-present-and-future.pdf\">slides</a>!</p>\n",
- "link": "/en-us/blog/qcon-beijing-2018.html",
- "meta": {
- "title": "Dubbo roadmap is announced in QCon Beijing 2018",
- "keywords": "Dubbo, roadmap, QCon Beijing",
- "description": "This article will introduce you that Dubbo roadmap is announced in QCon Beijing 2018."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/sentinel-introduction-for-dubbo.html b/en-us/blog/sentinel-introduction-for-dubbo.html
deleted file mode 100644
index 19feef3..0000000
--- a/en-us/blog/sentinel-introduction-for-dubbo.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Sentinel, current limit, fuse" />
- <meta name="description" content="This article introduces the Sentinel and how to integrate it with Dubbo." />
- <!-- 网页标签标题 -->
- <title>Sentinel: The flow sentinel of Dubbo services</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<p>In large clusters there may be thousands of Dubbo service instances in production, with continuous traffic coming in. However, in distributed systems, some services may be unavailable due to various of failure such as traffic surge, high system load, and network latency. If no control actions are performed, this may cause cascading failure, affecting the availability of the service. So we need a powerful library - Sentinel, which can guarantee the stability of the service, to protect [...]
-<h2>Introduction to Sentinel</h2>
-<p><a href="https://github.com/alibaba/Sentinel">Sentinel</a> is a powerful library opensourced by Alibaba Middleware Team. Sentinel takes "<strong>flow</strong>" as the breakthrough point, and covers multiple fields including flow control, concurrency, circuit breaking and load protection to protect service stability.</p>
-<p>There are mainly three features in Sentinel:</p>
-<ul>
-<li><strong>Flow Control</strong>: Sentinel can control the traffic flow of resource calls based on different runtime metrics (such as QPS, number of threads, system load, etc.), for different invocation paths, and adjust random traffic to appropriate shapes (e.g. uniform speed).</li>
-<li><strong>Circuit Breaking</strong>: When a resource in the invocation chain is unstable (average RT increase or exception ratio increase), Sentinel will fast-fail the call request for this resource to avoid affecting other resources, causing cascade failure.</li>
-<li><strong>System Load Protection</strong>: Sentinel can be used to protect your server in case the system load goes too high. It helps you to achieve a good balance between system load and incoming requests.</li>
-</ul>
-<p>The commonly used circuit breaker/isolation library in production is <a href="https://github.com/Netflix/Hystrix">Netflix Hystrix</a>. Hystrix focuses on the concept of isolation, which isolates dependencies (that is resource in Sentinel) through thread pools or semaphores. The benefit of Hystrix thread pool isolation is that the isolation is thorough, but the downside is that you have to create a lot of thread pools, pre-divide dependencies, and allocate thread pools to each dependen [...]
-<p>Hystrix uses Circuit Breaker Pattern to automatically fast-fail the service when exception ratio exceeds the threshold. Sentinel's circuit breaking feature is more versatile, which supports two metrics: average response time and failure ratio. Sentinel also provides various invocation chain path and flow control effects support, as well as the ability to adjust the traffic in real time according to the system load to protect the system. At the same time, Sentinel also provides a real- [...]
-<h2>Best Practice for using Dubbo with Sentinel</h2>
-<p><a href="https://github.com/dubbo/dubbo-sentinel-support">Sentinel Dubbo Adapter</a> provides service consumer filter and provider filter for Dubbo services. We can add the following dependency in <code>pom.xml</code> (if you are using Maven):</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.alibaba.csp<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>sentinel-dubbo-adapter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>x.y.z<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
-</code></pre>
-<p>The two filters are enabled by default. Once you add the dependency, the Dubbo services and methods will become protected resources in Sentinel, which can leverage Sentinel's flow control and guard ability when rules are configured. If you don't want to enable the filter, you can manually disable it. For example:</p>
-<pre><code class="language-java"><span class="hljs-meta">@Bean</span>
-<span class="hljs-function"><span class="hljs-keyword">public</span> ConsumerConfig <span class="hljs-title">consumerConfig</span><span class="hljs-params">()</span> </span>{
- ConsumerConfig consumerConfig = <span class="hljs-keyword">new</span> ConsumerConfig();
- consumerConfig.setFilter(<span class="hljs-string">"-sentinel.dubbo.consumer.filter"</span>);
- <span class="hljs-keyword">return</span> consumerConfig;
-}
-</code></pre>
-<p>We've provided sereval demos, you can check here: <a href="https://github.com/alibaba/Sentinel/tree/master/sentinel-demo/sentinel-demo-dubbo">sentinel-demo-dubbo</a>。</p>
-<h3>Service Provider</h3>
-<p>Dubbo service providers provide services for outside world and handle requests from consumers. To protect the service provider from suffering the proliferation of traffic flow, you can set flow rules in <strong>QPS mode</strong> to the service provider. Thus, when the number of requests per second exceeds the threshold, new requests are automatically rejected.</p>
-<p>The flow control for Dubbo services has two granularities: service interface and service method.</p>
-<ul>
-<li>Service interface：resourceName format is <code>interfaceName</code>，e.g. <code>com.alibaba.csp.sentinel.demo.dubbo.FooService</code></li>
-<li>Service method：resourceName format is <code>interfaceName:methodSignature</code>，e.g. <code>com.alibaba.csp.sentinel.demo.dubbo.FooService:sayHello(java.lang.String)</code></li>
-</ul>
-<p>For the detail of flow rule configuration and flow control, please refer to <a href="https://github.com/alibaba/Sentinel/wiki/Flow-Control">Flow Control | Sentinel</a>.</p>
-<p>Let's take a look at the effect of the QPS flow control. Assume that we have a service interface <code>com.alibaba.csp.sentinel.demo.dubbo.FooService</code>, which contains a method <code>sayHello(java.lang.String)</code>. We set flow rule for service provider (QPS count = 10). Then we do RPC 15 times at service consumer continuously in 1s. We can see the blocked metrics in the log. The log of blocked calls is located in <code>~/logs/csp/sentinel-block.log</code>：</p>
-<pre><code>2018-07-24 17:13:43|1|com.alibaba.csp.sentinel.demo.dubbo.FooService:sayHello(java.lang.String),FlowException,default,|5,0
-</code></pre>
-<p>Log messages will also appear in provider's metric log：</p>
-<pre><code>1532423623000|2018-07-24 17:13:43|com.alibaba.csp.sentinel.demo.dubbo.FooService|15|0|15|0|3
-1532423623000|2018-07-24 17:13:43|com.alibaba.csp.sentinel.demo.dubbo.FooService:sayHello(java.lang.String)|10|5|10|0|0
-</code></pre>
-<p>In many circumstances, it's also significant to control traffic flow based on the <strong>caller</strong>. For example, assuming that there are two services A and B, both of them initiate remote call requests to the service provider. If we want to limit the calls from service B only, we can set the <code>limitApp</code> of flow rule as the identifier of service B (e.g. service name). The Sentinel Dubbo Adapter will automatically resolve the Dubbo consumer's <em>application name</em> a [...]
-<blockquote>
-<p>Note: Dubbo consumer does not provide its Dubbo application name when doing RPC, so developers should manually put the application name into <em>attachment</em> at consumer side, then extract it at provider side. Sentinel Dubbo Adapter has implemented a filter where consumer can carry application name information to provider automatically. If the counsmer does not use Sentinel Dubbo Adapter but requires flow control based on caller, developers can manually put the application name int [...]
-</blockquote>
-<p>The <code>sentinel-block.log</code> will also record caller name. For example:</p>
-<pre><code>2018-07-25 16:26:48|1|com.alibaba.csp.sentinel.demo.dubbo.FooService:sayHello(java.lang.String),FlowException,default,demo-consumer|5,0
-</code></pre>
-<p>The <code>demo-consumer</code> in the log is the caller name (origin).</p>
-<h3>Service Consumer</h3>
-<p>Dubbo service consumers act as a client to invoke the remote service. Each service may depend on several downstream services. If a service A depends on the downstream service B, and service B is unstable (i.e. the response time becomes longer), the number of threads where service A invokes service B will accumulate, thus may eventually run out of service A's thread pool. We use the thread count to control access to downstream service B. This can ensure service itself not affected by o [...]
-<p>The thread-count-based flow control mode does not require us to explicitly perform thread pool isolation. Sentinel will control the number of threads of the resource, and the excess requests will be rejected directly until the stacked tasks are completed.</p>
-<h3>Sentinel Dashboard</h3>
-<p>For ease of use, Sentinel provides a Dashboard for configuring rules, viewing monitoring metrics, machine discovery, and more. We only need to start the dashborad according to the <a href="https://github.com/alibaba/Sentinel/wiki/Dashboard">Sentinel dashboard documentation</a>, then add the appropriate parameters to the corresponding application and launch it. For example, the startup parameters of the service provider demo in this article is:</p>
-<pre><code class="language-bash">-Djava.net.preferIPv4Stack=<span class="hljs-literal">true</span> -Dcsp.sentinel.api.port=8720 -Dcsp.sentinel.dashboard.server=localhost:8080 -Dproject.name=dubbo-provider-demo
-</code></pre>
-<p>After launching the service provider demo, we can find our application in the Sentinel dashboard. It's convenient to configure the rules in the dashboard：</p>
-<p><img src="../../img/blog/sentinel-dashboard-view-rules.png" alt="Rule List"></p>
-<p>Or view real-time metrics：</p>
-<p><img src="../../img/blog/sentinel-dashboard-metrics.png" alt="Real-time metrics monitoring"></p>
-<h2>Summary</h2>
-<p>This blog post only introduces the simplest scenario in Sentinel - Traffic Flow Control. Sentinel can handle more complex scenarios like circuit breaking, cold starting and uniform traffic flow. For more scenarios, you can dig into <a href="https://github.com/alibaba/Sentinel/wiki">Sentinel Wiki</a>.</p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/sentinel-introduction-for-dubbo.json b/en-us/blog/sentinel-introduction-for-dubbo.json
deleted file mode 100644
index 1454dde..0000000
--- a/en-us/blog/sentinel-introduction-for-dubbo.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "sentinel-introduction-for-dubbo.md",
- "__html": "<h1>Sentinel: The flow sentinel of Dubbo services</h1>\n<p>In large clusters there may be thousands of Dubbo service instances in production, with continuous traffic coming in. However, in distributed systems, some services may be unavailable due to various of failure such as traffic surge, high system load, and network latency. If no control actions are performed, this may cause cascading failure, affecting the availability of the service. So we need a powerful library - Se [...]
- "link": "/en-us/blog/sentinel-introduction-for-dubbo.html",
- "meta": {
- "title": "Sentinel: The flow sentinel of Dubbo services",
- "keywords": "Dubbo, Sentinel, current limit, fuse",
- "description": "This article introduces the Sentinel and how to integrate it with Dubbo."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/spring-boot-dubbo-start-stop-analysis.html b/en-us/blog/spring-boot-dubbo-start-stop-analysis.html
deleted file mode 100644
index 2049f8e..0000000
--- a/en-us/blog/spring-boot-dubbo-start-stop-analysis.html
+++ /dev/null
@@ -1,217 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Spring Boot, source code analysis" />
- <meta name="description" content="This article introduces the implementation details of app start and stop in `dubbo-spring-boot-project`." />
- <!-- 网页标签标题 -->
- <title>Source code analysis of spring-boot+Dubbo App start and stop</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Introduction</h2>
-<p><a href="https://github.com/apache/dubbo-spring-boot-project">Dubbo Spring Boot</a> project is dedicated to simplifying the development of the Dubbo RPC framework in the Spring Boot application. It also integrates the feature of Spring Boot:</p>
-<ul>
-<li><a href="https://github.com/apache/dubbo-spring-boot-project/blob/master/dubbo-spring-boot-autoconfigure">Autoconfigure</a> (ex: Annotation driver, Autoconfigure, etc.)</li>
-<li><a href="https://github.com/apache/dubbo-spring-boot-project/blob/master/dubbo-spring-boot-actuator">Production-Ready</a> (ex: Security, Healthy check, Externalize configuration, etc.)</li>
-</ul>
-<h2>The analysis of DubboConsumer startup</h2>
-<p>Have you ever thought about this : since the <code>DubboConsumerDemo</code> application in <code>dubbo-spring-boot-project</code> has only one line of code, why not just exit directly when the <code>main</code> method is executed?</p>
-<pre><code class="language-java"><span class="hljs-meta">@SpringBootApplication</span>(scanBasePackages = <span class="hljs-string">"com.alibaba.boot.dubbo.demo.consumer.controller"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DubboConsumerDemo</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- SpringApplication.run(DubboConsumerDemo.class,args);
- }
-
-}
-</code></pre>
-<p>In fact, to answer this question, we need to abstract it first, that is, under what circumstances will a JVM process exit?</p>
-<p>Take Java 8 as an example. By referring to the JVM language specification[1], there is a clear description in Section 12.8:</p>
-<blockquote>
-<p>A program terminates all its activity and <em>exits</em> when one of two things happens:</p>
-<ul>
-<li>All the threads that are not daemon threads terminate.</li>
-<li>Some thread invokes the <code>exit</code> method of class <code>Runtime</code> or class <code>System</code>, and the <code>exit</code> operation is not forbidden by the security manager.</li>
-</ul>
-</blockquote>
-<p>Therefore, in view of the above situation, we judge that there must be some non-daemon thread not exiting. All thread information can be seen by <code>jstack</code>, including whether they are daemon threads, and <code>jstack</code> can be used to find out which threads are non-daemon.</p>
-<pre><code class="language-sh">➜ jstack 57785 | grep tid | grep -v <span class="hljs-string">"daemon"</span>
-<span class="hljs-string">"container-0"</span> <span class="hljs-comment">#37 prio=5 os_prio=31 tid=0x00007fbe312f5800 nid=0x7103 waiting on condition [0x0000700010144000]</span>
-<span class="hljs-string">"container-1"</span> <span class="hljs-comment">#49 prio=5 os_prio=31 tid=0x00007fbe3117f800 nid=0x7b03 waiting on condition [0x0000700010859000]</span>
-<span class="hljs-string">"DestroyJavaVM"</span> <span class="hljs-comment">#83 prio=5 os_prio=31 tid=0x00007fbe30011000 nid=0x2703 waiting on condition [0x0000000000000000]</span>
-<span class="hljs-string">"VM Thread"</span> os_prio=31 tid=0x00007fbe3005e800 nid=0x3703 runnable
-<span class="hljs-string">"GC Thread#0"</span> os_prio=31 tid=0x00007fbe30013800 nid=0x5403 runnable
-<span class="hljs-string">"GC Thread#1"</span> os_prio=31 tid=0x00007fbe30021000 nid=0x5303 runnable
-<span class="hljs-string">"GC Thread#2"</span> os_prio=31 tid=0x00007fbe30021800 nid=0x2d03 runnable
-<span class="hljs-string">"GC Thread#3"</span> os_prio=31 tid=0x00007fbe30022000 nid=0x2f03 runnable
-<span class="hljs-string">"G1 Main Marker"</span> os_prio=31 tid=0x00007fbe30040800 nid=0x5203 runnable
-<span class="hljs-string">"G1 Conc#0"</span> os_prio=31 tid=0x00007fbe30041000 nid=0x4f03 runnable
-<span class="hljs-string">"G1 Refine#0"</span> os_prio=31 tid=0x00007fbe31044800 nid=0x4e03 runnable
-<span class="hljs-string">"G1 Refine#1"</span> os_prio=31 tid=0x00007fbe31045800 nid=0x4d03 runnable
-<span class="hljs-string">"G1 Refine#2"</span> os_prio=31 tid=0x00007fbe31046000 nid=0x4c03 runnable
-<span class="hljs-string">"G1 Refine#3"</span> os_prio=31 tid=0x00007fbe31047000 nid=0x4b03 runnable
-<span class="hljs-string">"G1 Young RemSet Sampling"</span> os_prio=31 tid=0x00007fbe31047800 nid=0x3603 runnable
-<span class="hljs-string">"VM Periodic Task Thread"</span> os_prio=31 tid=0x00007fbe31129000 nid=0x6703 waiting on condition
-
-</code></pre>
-<blockquote>
-<p>We can find all the thread digests by <code>grep tid</code> here, and find the line that doesn't contain the daemon keyword by <code>grep -v</code> command.</p>
-</blockquote>
-<p>We can get some information from the above results:</p>
-<ul>
-<li>There are two "suspicious" threads : <code>container-0</code>, <code>container-1</code>. They are non-daemon thread in wait state.</li>
-<li>There are alse some threads about GC, and threads that start with <code>VM</code>. They are also some non-daemon threads, but they are most likely the JVM's own threads, which we can ignore for now.</li>
-</ul>
-<p>In summary, we can infer that it is likely that the <code>container-0</code> and <code>container-1</code> cause the JVM to not exit. Now let's search through the source code to find out who created the two threads.</p>
-<p>By the source code analysis of Spring-boot, we can find these code in the <code>startDaemonAwaitThread</code> method of <code>org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer</code>.</p>
-<pre><code class="language-java"> <span class="hljs-function"><span class="hljs-keyword">private</span> <span class="hljs-keyword">void</span> <span class="hljs-title">startDaemonAwaitThread</span><span class="hljs-params">()</span> </span>{
- Thread awaitThread = <span class="hljs-keyword">new</span> Thread(<span class="hljs-string">"container-"</span> + (containerCounter.get())) {
-
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span><span class="hljs-params">()</span> </span>{
- TomcatEmbeddedServletContainer.<span class="hljs-keyword">this</span>.tomcat.getServer().await();
- }
-
- };
- awaitThread.setContextClassLoader(getClass().getClassLoader());
- awaitThread.setDaemon(<span class="hljs-keyword">false</span>);
- awaitThread.start();
- }
-</code></pre>
-<p>Let's add a breakpoint in this method, and focus on the call stack:</p>
-<pre><code class="language-plain">initialize:115, TomcatEmbeddedServletContainer (org.springframework.boot.context.embedded.tomcat)
-<init>:84, TomcatEmbeddedServletContainer (org.springframework.boot.context.embedded.tomcat)
-getTomcatEmbeddedServletContainer:554, TomcatEmbeddedServletContainerFactory (org.springframework.boot.context.embedded.tomcat)
-getEmbeddedServletContainer:179, TomcatEmbeddedServletContainerFactory (org.springframework.boot.context.embedded.tomcat)
-createEmbeddedServletContainer:164, EmbeddedWebApplicationContext (org.springframework.boot.context.embedded)
-onRefresh:134, EmbeddedWebApplicationContext (org.springframework.boot.context.embedded)
-refresh:537, AbstractApplicationContext (org.springframework.context.support)
-refresh:122, EmbeddedWebApplicationContext (org.springframework.boot.context.embedded)
-refresh:693, SpringApplication (org.springframework.boot)
-refreshContext:360, SpringApplication (org.springframework.boot)
-run:303, SpringApplication (org.springframework.boot)
-run:1118, SpringApplication (org.springframework.boot)
-run:1107, SpringApplication (org.springframework.boot)
-main:35, DubboConsumerDemo (com.alibaba.boot.dubbo.demo.consumer.bootstrap)
-</code></pre>
-<p>It can be seen that during the startup process of the Spring-boot application, the above method is executed since the execution of Tomcat exposes the HTTP service by default. Also, all threads started by Tomcat are daemon threads by default, such as the Acceptor of the listening request, threads in working threads, etc. Thus the JVM will also exit after the startup is complete in there is no extra control here. Therefore, it is necessary to explicitly start a thread and continue to wa [...]
-<p>Let's dig deeper to find out how the thread stay alive in Tomcat's <code>this.tomcat.getServer().await()</code> method.</p>
-<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">await</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-comment">// ...</span>
- <span class="hljs-keyword">if</span>( port==-<span class="hljs-number">1</span> ) {
- <span class="hljs-keyword">try</span> {
- awaitThread = Thread.currentThread();
- <span class="hljs-keyword">while</span>(!stopAwait) {
- <span class="hljs-keyword">try</span> {
- Thread.sleep( <span class="hljs-number">10000</span> );
- } <span class="hljs-keyword">catch</span>( InterruptedException ex ) {
- <span class="hljs-comment">// continue and check the flag</span>
- }
- }
- } <span class="hljs-keyword">finally</span> {
- awaitThread = <span class="hljs-keyword">null</span>;
- }
- <span class="hljs-keyword">return</span>;
- }
- <span class="hljs-comment">// ...</span>
- }
-</code></pre>
-<p>In the await method, the current thread checks the variable <code>stopAwait</code> every 10 seconds in a while loop. It is a <code>volatile</code> variable that is used to ensure that the current thread can see the change immediately after the variable being modified by another thread. If there is no change, it will stay in the loop. This is the reason why the thread does not exit, which is also the reason that the entire Spring-boot application doesn't exit.</p>
-<p>Since Spring-boot application enables port 8080 and 8081(management port) at the same time, there are actually two Tomcats. So there are two threads named <code>container-0</code> and <code>container-1</code>.</p>
-<p>Next, let's see how this Spring-boot application exits.</p>
-<h2>The analysis of DubboConsumer exit</h2>
-<p>As mentioned in the previous description, there is a thread that checks the variable <code>stopAwait</code> continuously. So there must be a thread to modify <code>stopAwait</code> at Stop, thus break the while loop. But who is modifying this variable?</p>
-<p>By analyzing the source code, we can see that there is only one method that modifies <code>stopAwait</code> : <code>org.apache.catalina.core.StandardServer#stopAwait</code>. To figure out who is calling this method, we add a breakpoint here.</p>
-<blockquote>
-<p>Note that after adding a breakpoint in Intellij IDEA's Debug mode, we also need to type <code>kill -s INT $PID</code> or <code>kill -s TERM $PID</code> in command line to trigger the breakpoint. Due to buggy IDEA, a single click to the stop button won't trigger the breakpoint.</p>
-</blockquote>
-<p>You can see the method is called by a thread called <code>Thread-3</code>:</p>
-<pre><code class="language-java">stopAwait:<span class="hljs-number">390</span>, StandardServer (org.apache.catalina.core)
-stopInternal:<span class="hljs-number">819</span>, StandardServer (org.apache.catalina.core)
-stop:<span class="hljs-number">226</span>, LifecycleBase (org.apache.catalina.util)
-stop:<span class="hljs-number">377</span>, Tomcat (org.apache.catalina.startup)
-stopTomcat:<span class="hljs-number">241</span>, TomcatEmbeddedServletContainer (org.springframework.boot.context.embedded.tomcat)
-stop:<span class="hljs-number">295</span>, TomcatEmbeddedServletContainer (org.springframework.boot.context.embedded.tomcat)
-stopAndReleaseEmbeddedServletContainer:<span class="hljs-number">306</span>, EmbeddedWebApplicationContext (org.springframework.boot.context.embedded)
-onClose:<span class="hljs-number">155</span>, EmbeddedWebApplicationContext (org.springframework.boot.context.embedded)
-doClose:<span class="hljs-number">1014</span>, AbstractApplicationContext (org.springframework.context.support)
-run:<span class="hljs-number">929</span>, AbstractApplicationContext$<span class="hljs-number">2</span> (org.springframework.context.support)
-</code></pre>
-<p>Through source code analysis, it was executed by Spring's registered <code>ShutdownHook</code>.</p>
-<pre><code class="language-java"> <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">registerShutdownHook</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">if</span> (<span class="hljs-keyword">this</span>.shutdownHook == <span class="hljs-keyword">null</span>) {
- <span class="hljs-comment">// No shutdown hook registered yet.</span>
- <span class="hljs-keyword">this</span>.shutdownHook = <span class="hljs-keyword">new</span> Thread() {
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">synchronized</span> (startupShutdownMonitor) {
- doClose();
- }
- }
- };
- Runtime.getRuntime().addShutdownHook(<span class="hljs-keyword">this</span>.shutdownHook);
- }
- }
-</code></pre>
-<p>By reffering the Java API documentation[2], we found that ShutdownHook will be executed under the following two cases.</p>
-<blockquote>
-<p>The Java virtual machine <em>shuts down</em> in response to two kinds of events:</p>
-<ul>
-<li>The program <em>exits</em> normally, when the last non-daemon thread exits or when the <code>exit</code> (equivalently, <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/System.html#exit-int-"><code>System.exit</code></a>) method is invoked, or</li>
-<li>The virtual machine is <em>terminated</em> in response to a user interrupt, such as typing <code>^C</code>, or a system-wide event, such as user logoff or system shutdown.</li>
-</ul>
-</blockquote>
-<ol>
-<li>So it's either a call of <code>System.exit()</code></li>
-<li>Respond to external signals, such as Ctrl+C(actually sent as SIGINT signal), or <code>SIGTERM</code> signal (<code>kill $PID</code> will send <code>SIGTERM</code> signal by default)</li>
-</ol>
-<p>Therefore, the normal application will execute the above ShutdownHook during the stop process (except <code>kill -9 $PID</code>). Its function is not only to close the Tomcat, but also to perform other cleanup work. It is unnecessary to go into details.</p>
-<h2>Summary</h2>
-<ol>
-<li>During the startup of <code>DubboConsumer</code>, an independent non-daemon thread is launched to query the status of the variable continuously, thus the process can't exit.</li>
-<li>To stop the <code>DubboConsumer</code>, one should call ShutdownHook to change the variable to let the thread break the loop.</li>
-</ol>
-<h2>Problems</h2>
-<p>In the example of DubboProvider, we see that Provider doesn't start Tomcat to provide HTTP service, then how does the program stays alive without exiting? We will answer this question in the next article.</p>
-<h3>Notice</h3>
-<p>By running the following unit test which create a thread in <code>Intellij IDEA</code> , we are surprised to find that the program exits with less than 1000s. Why?(The thread being created is a non-daemon thread)</p>
-<pre><code class="language-java"> <span class="hljs-meta">@Test</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">test</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">new</span> Thread(<span class="hljs-keyword">new</span> Runnable() {
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-keyword">try</span> {
- Thread.sleep(<span class="hljs-number">1000000</span>);
- } <span class="hljs-keyword">catch</span> (InterruptedException e) {
- e.printStackTrace();
- }
- }
- }).start();
- }
-</code></pre>
-<p>[1] <a href="https://docs.oracle.com/javase/specs/jls/se8/html/jls-12.html#jls-12.8">https://docs.oracle.com/javase/specs/jls/se8/html/jls-12.html#jls-12.8</a></p>
-<p>[2] <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Runtime.html#addShutdownHook">https://docs.oracle.com/javase/8/docs/api/java/lang/Runtime.html#addShutdownHook</a></p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/spring-boot-dubbo-start-stop-analysis.json b/en-us/blog/spring-boot-dubbo-start-stop-analysis.json
deleted file mode 100644
index 60e0cc8..0000000
--- a/en-us/blog/spring-boot-dubbo-start-stop-analysis.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "spring-boot-dubbo-start-stop-analysis.md",
- "__html": "<h1>Source code analysis of spring-boot+Dubbo App start and stop</h1>\n<h2>Introduction</h2>\n<p><a href=\"https://github.com/apache/dubbo-spring-boot-project\">Dubbo Spring Boot</a> project is dedicated to simplifying the development of the Dubbo RPC framework in the Spring Boot application. It also integrates the feature of Spring Boot:</p>\n<ul>\n<li><a href=\"https://github.com/apache/dubbo-spring-boot-project/blob/master/dubbo-spring-boot-autoconfigure\">Autoconfigure</ [...]
- "link": "/en-us/blog/spring-boot-dubbo-start-stop-analysis.html",
- "meta": {
- "title": "Source code analysis of spring-boot+Dubbo App start and stop",
- "keywords": "Dubbo, Spring Boot, source code analysis",
- "description": "This article introduces the implementation details of app start and stop in `dubbo-spring-boot-project`."
- }
-}
\ No newline at end of file
diff --git a/en-us/blog/tracing-with-skywalking.html b/en-us/blog/tracing-with-skywalking.html
deleted file mode 100644
index c028770..0000000
--- a/en-us/blog/tracing-with-skywalking.html
+++ /dev/null
@@ -1,131 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="Dubbo, Skywalking, tracing, distribute tracking" />
- <meta name="description" content="This article introduces how to use Apache Skywalking to track Dubbo applications." />
- <!-- 网页标签标题 -->
- <title>Tracing Dubbo service with Apache Skywalking(incubator)</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/blogDetail.css" />
-</head>
-<body>
- <div id="root"><div class="blog-detail-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a hr [...]
-<h2>Introduction to Apache Skywalking(Incubator)</h2>
-<p><a href="https://github.com/apache/incubator-skywalking">Apache Skywalking(Incubator)</a> is the APM system that it designed for micro-services architectures and cloud native architecture systems and supports distribute tracking. <a href="https://github.com/apache/incubator-skywalking">Apache skywalking (incubator)</a> collects and analyzes the trace data and generates the relationship between the application and the service metric, Apache skywalking supports multiple languages agen [...]
-<p>Currently, Skywalking has supported analysis the operation of distributed systems from 6 visual dimensions. The overview view is a global view of your applications and components, including the number of components and applications, application alarm fluctuations, slow service lists, and application throughput; The topology shows the topological relationship of the whole application; The application view represents the upstream and downstream relationship of the application from singl [...]
-<h2>Dubbo and Apache Skywalking(Incubator)</h2>
-<h3>Build the Dubbo demo project</h3>
-<p>The Dubbo demo has been uploaded to the <a href="https://github.com/SkywalkingTest/dubbo-trace-example">GitHub repository</a>.</p>
-<h4>API project</h4>
-<p>Service interface definition:
-package org.apache.skywalking.demo.interfaces;</p>
-<p>public interface HelloService {
-String sayHello(String name);
-}</p>
-<h4>Service provider project</h4>
-<p>package org.apache.skywalking.demo.provider;</p>
-<p>@Service(version = "<span class="katex"><span class="katex-mathml"><math><semantics><mrow><mrow><mi>d</mi><mi>e</mi><mi>m</mi><mi>o</mi><mi mathvariant="normal">.</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>v</mi><mi>i</mi><mi>c</mi><mi>e</mi><mi mathvariant="normal">.</mi><mi>v</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>i</mi><mi>o</mi><mi>n</mi></mrow><mi mathvariant="normal">"</mi><mo separator="true">,</mo><mi>a</mi><mi>p</mi><mi>p</mi><mi>l</mi><mi>i</mi><mi>c</mi><mi>a</mi><mi>t< [...]
- application = "</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="strut" style="height:0.69444em;"></span><span class="strut bottom" style="height:0.8888799999999999em;vertical-align:-0.19444em;"></span><span class="base textstyle uncramped"><span class="mord textstyle uncramped"><span class="mord mathit">d</span><span class="mord mathit">e</span><span class="mord mathit">m</span><span class="mord mathit">o</span><span class="mord mathrm [...]
-protocol = "<span class="katex"><span class="katex-mathml"><math><semantics><mrow><mrow><mi>d</mi><mi>u</mi><mi>b</mi><mi>b</mi><mi>o</mi><mi mathvariant="normal">.</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>t</mi><mi>o</mi><mi>c</mi><mi>o</mi><mi>l</mi><mi mathvariant="normal">.</mi><mi>i</mi><mi>d</mi></mrow><mi mathvariant="normal">"</mi><mo separator="true">,</mo><mi>r</mi><mi>e</mi><mi>g</mi><mi>i</mi><mi>s</mi><mi>t</mi><mi>r</mi><mi>y</mi><mo>=</mo><mi mathvariant="normal">&q [...]
- registry = "</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="strut" style="height:0.69444em;"></span><span class="strut bottom" style="height:0.8888799999999999em;vertical-align:-0.19444em;"></span><span class="base textstyle uncramped"><span class="mord textstyle uncramped"><span class="mord mathit">d</span><span class="mord mathit">u</span><span class="mord mathit">b</span><span class="mord mathit">b</span><span class="mord mathit">o [...]
-public class HelloServiceImpl implements HelloService {</p>
-<pre><code>public String sayHello(String name) {
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(1));
- return "Hello, " + name;
-}
-</code></pre>
-<p>}</p>
-<h4>Service consumer project</h4>
-<p>package org.apache.skywalking.demo.consumer;</p>
-<p>@RestController
-public class ConsumerController {</p>
-<pre><code>private static int COUNT = 0;
-
-@Reference(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- url = "dubbo://localhost:20880", timeout = 60000)
-private HelloService helloService;
-
-@GetMapping("/sayHello/{name}")
-public String sayHello(@PathVariable(name = "name") String name) {
- if ((COUNT++) % 3 == 0){
- throw new RuntimeException();
- }
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(2));
- return helloService.sayHello(name);
-}
-</code></pre>
-<p>}</p>
-<h3>Deploy Apache Skywalking(incubator)</h3>
-<p><a href="https://github.com/apache/incubator-skywalking">Apache skywalking (Incubator)</a> offers two deployment modes: single-node mode and cluster mode,Here is the single-node mode deployment step, and more about how to deploy skywalking with cluster mode, please reference <a href="https://github.com/apache/incubator-skywalking/blob/master/docs/en/Deploy-backend-in-cluster-mode.md">document</a>.</p>
-<h4>Third-party components</h4>
-<ol>
-<li>JDK 8+</li>
-<li>Elasticsearch 5.x</li>
-</ol>
-<h4>Deployment step</h4>
-<ol>
-<li>Download <a href="http://skywalking.apache.org/downloads/">Apache Skywalking Collector</a></li>
-<li>Deploy Elasticsearch service
-<ul>
-<li>Set <code>cluster.name</code> to <code>CollectorDBCluster</code></li>
-<li>Set <code>network.host</code> to <code>0.0.0.0</code></li>
-<li>Start elasticsearch service</li>
-</ul>
-</li>
-<li>Unzip and start the Skywalking Collector. Run the ' bin/startup.sh ' command to start skywalking Collector</li>
-</ol>
-<h4>Deploy the demo</h4>
-<p>Before you deploy the demo service, please run the following command:</p>
-<pre><code>./mvnw clean package
-</code></pre>
-<h4>Deploy the provider service</h4>
-<pre><code>java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-provider -Dskywalking.collector.servers=localhost:10800 dubbo-provider/target/dubbo-provider.jar
-</code></pre>
-<h4>Deploy the consumer service</h4>
-<pre><code>java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-consumer -Dskywalking.collector.servers=localhost:10800 dubbo-consumer/target/dubbo-consumer.jar
-</code></pre>
-<h4>visit demo service</h4>
-<pre><code>curl http://localhost:8080/sayHello/test
-</code></pre>
-<h2>Skywalking scren snapshot</h2>
-<h3>Dashboard</h3>
-<p><img src="../../img/blog/skywalking-dashboard.png" alt="/admin-guide/images/skywalking-dashboard.png"></p>
-<h3>Topology</h3>
-<p><img src="../../img/blog/skywalking-topology.png" alt="/admin-guide/images/skywalking-topology.png"></p>
-<h3>Application view</h3>
-<p><img src="../../img/blog/skywalking-application.png" alt="/admin-guide/images/skywalking-application.png"></p>
-<p>JVM Information
-<img src="../../img/blog/skywalking-application_instance.png" alt="/admin-guide/images/skywalking-application_instance.png"></p>
-<h3>Service view</h3>
-<p>Consumer side
-<img src="../../img/blog/skywalking-service-consumer.png" alt="/admin-guide/images/skywalking-service-consumer.png"></p>
-<p>provider side
-<img src="../../img/blog/skywalking-service-provider.png" alt="/admin-guide/images/skywalking-service-provider.png"></p>
-<h3>Trace</h3>
-<p><img src="../../img/blog/skywalking-trace.png" alt="/admin-guide/images/skywalking-trace.png"></p>
-<p>Span info
-<img src="../../img/blog/skywalking-span-Info.png" alt="/admin-guide/images/skywalking-span-Info.png"></p>
-<h3>Alarm view</h3>
-<p><img src="../../img/blog/skywalking-alarm.png" alt="/admin-guide/images/skywalking-alarm.png"></p>
-</section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events</a></ [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/blogDetail.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/blog/tracing-with-skywalking.json b/en-us/blog/tracing-with-skywalking.json
deleted file mode 100644
index 71388a7..0000000
--- a/en-us/blog/tracing-with-skywalking.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "filename": "tracing-with-skywalking.md",
- "__html": "<h1>Tracing Dubbo service with Apache Skywalking(incubator)</h1>\n<h2>Introduction to Apache Skywalking(Incubator)</h2>\n<p><a href=\"https://github.com/apache/incubator-skywalking\">Apache Skywalking(Incubator)</a> is the APM system that it designed for micro-services architectures and cloud native architecture systems and supports distribute tracking. <a href=\"https://github.com/apache/incubator-skywalking\">Apache skywalking (incubator)</a> collects and analyzes the tra [...]
- "link": "/en-us/blog/tracing-with-skywalking.html",
- "meta": {
- "title": "Tracing Dubbo service with Apache Skywalking(incubator)",
- "keywords": "Dubbo, Skywalking, tracing, distribute tracking",
- "description": "This article introduces how to use Apache Skywalking to track Dubbo applications."
- }
-}
\ No newline at end of file
diff --git a/en-us/community/index.html b/en-us/community/index.html
deleted file mode 100644
index 9a5de1b..0000000
--- a/en-us/community/index.html
+++ /dev/null
@@ -1,32 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="community" />
- <meta name="description" content="community" />
- <!-- 网页标签标题 -->
- <title>community</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/community.css" />
-</head>
-<body>
- <div id="root"><div class="community-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a href [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/community.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/README.html b/en-us/docs/admin/README.html
deleted file mode 100644
index 3a51bb7..0000000
--- a/en-us/docs/admin/README.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="README" />
- <meta name="description" content="README" />
- <!-- 网页标签标题 -->
- <title>README</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/README.json b/en-us/docs/admin/README.json
deleted file mode 100644
index 905d401..0000000
--- a/en-us/docs/admin/README.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "README.md",
- "__html": "<p>This document explains the structure, deploy procedure and function of Dubbo Admin</p>\n",
- "link": "/en-us/docs/admin/README.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/SUMMARY.html b/en-us/docs/admin/SUMMARY.html
deleted file mode 100644
index 250e3d6..0000000
--- a/en-us/docs/admin/SUMMARY.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="SUMMARY" />
- <meta name="description" content="SUMMARY" />
- <!-- 网页标签标题 -->
- <title>SUMMARY</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<li><a href="introduction.md">1 Dubbo Admin introduction</a>
-<ul>
-<li><a href="serviceSearch.md">1.1 service search and detail</a></li>
-<li><a href="serviceGovernance.md">1.2 service governance</a></li>
-<li><a href="serviceTest.md">1.3 service test</a></li>
-</ul>
-</li>
-</ul>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/SUMMARY.json b/en-us/docs/admin/SUMMARY.json
deleted file mode 100644
index 4e28087..0000000
--- a/en-us/docs/admin/SUMMARY.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "SUMMARY.md",
- "__html": "<ul>\n<li><a href=\"introduction.md\">1 Dubbo Admin introduction</a>\n<ul>\n<li><a href=\"serviceSearch.md\">1.1 service search and detail</a></li>\n<li><a href=\"serviceGovernance.md\">1.2 service governance</a></li>\n<li><a href=\"serviceTest.md\">1.3 service test</a></li>\n</ul>\n</li>\n</ul>\n",
- "link": "/en-us/docs/admin/SUMMARY.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/admin-console.html b/en-us/docs/admin/install/admin-console.html
deleted file mode 100644
index 4fe2800..0000000
--- a/en-us/docs/admin/install/admin-console.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="admin-console" />
- <meta name="description" content="admin-console" />
- <!-- 网页标签标题 -->
- <title>admin-console</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>The current version of dubbo admin is under development, including: route rule, dynamic configuration, access control, weight adjustment, load balance, etc.</p>
-<p>Install:</p>
-<pre><code class="language-sh">git <span class="hljs-built_in">clone</span> https://github.com/apache/dubbo-admin.git /var/tmp/dubbo-admin
-<span class="hljs-built_in">cd</span> /var/tmp/dubbo-admin
-mvn clean package
-</code></pre>
-<p>Configuration <sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup>:</p>
-<pre><code class="language-sh">configuration file：
-dubbo-admin-backend/src/main/resources/application.properties
-configurations：
-dubbo.registry.address=zookeeper://127.0.0.1:2181
-</code></pre>
-<p>Start:</p>
-<pre><code class="language-sh">mvn --projects dubbo-admin-backend spring-boot:run
-</code></pre>
-<p>For more information, please visit:</p>
-<pre><code class="language-sh">https://github.com/apache/dubbo-admin
-</code></pre>
-<p>Visit [^2]:</p>
-<pre><code>http://127.0.0.1:8080
-</code></pre>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p>There's no login for current version, will be added later <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/admin-console.json b/en-us/docs/admin/install/admin-console.json
deleted file mode 100644
index 9a0b9e5..0000000
--- a/en-us/docs/admin/install/admin-console.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "admin-console.md",
- "__html": "<h1>Install admin console</h1>\n<p>The current version of dubbo admin is under development, including: route rule, dynamic configuration, access control, weight adjustment, load balance, etc.</p>\n<p>Install:</p>\n<pre><code class=\"language-sh\">git <span class=\"hljs-built_in\">clone</span> https://github.com/apache/dubbo-admin.git /var/tmp/dubbo-admin\n<span class=\"hljs-built_in\">cd</span> /var/tmp/dubbo-admin\nmvn clean package\n</code></pre>\n<p>Configuration <sup cla [...]
- "link": "/en-us/docs/admin/install/admin-console.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/consumer-demo.html b/en-us/docs/admin/install/consumer-demo.html
deleted file mode 100644
index 95956cb..0000000
--- a/en-us/docs/admin/install/consumer-demo.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="consumer-demo" />
- <meta name="description" content="consumer-demo" />
- <!-- 网页标签标题 -->
- <title>consumer-demo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>install:</p>
-<pre><code class="language-sh">git <span class="hljs-built_in">clone</span> https://github.com/apache/dubbo.git
-<span class="hljs-built_in">cd</span> dubbo
-Please start Provider first
-add -Djava.net.preferIPv4Stack=<span class="hljs-literal">true</span> <span class="hljs-keyword">if</span> your IDE is Intellij Idea
-</code></pre>
-<p>configuration:</p>
-<pre><code class="language-sh">resource/META-INFO.spring/dubbo-demo-consumer.xml
-change dubbo:registry to the real registry center address
-</code></pre>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/consumer-demo.json b/en-us/docs/admin/install/consumer-demo.json
deleted file mode 100644
index 90eebcb..0000000
--- a/en-us/docs/admin/install/consumer-demo.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "consumer-demo.md",
- "__html": "<h1>install demo consumer</h1>\n<p>install:</p>\n<pre><code class=\"language-sh\">git <span class=\"hljs-built_in\">clone</span> https://github.com/apache/dubbo.git\n<span class=\"hljs-built_in\">cd</span> dubbo\nPlease start Provider first\nadd -Djava.net.preferIPv4Stack=<span class=\"hljs-literal\">true</span> <span class=\"hljs-keyword\">if</span> your IDE is Intellij Idea\n</code></pre>\n<p>configuration:</p>\n<pre><code class=\"language-sh\">resource/META-INFO.spring/du [...]
- "link": "/en-us/docs/admin/install/consumer-demo.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/introduction.html b/en-us/docs/admin/install/introduction.html
deleted file mode 100644
index 3e6c0b6..0000000
--- a/en-us/docs/admin/install/introduction.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="introduction" />
- <meta name="description" content="introduction" />
- <!-- 网页标签标题 -->
- <title>introduction</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>You can run Demo Provider and Demo Consumer only, the default discovery strategy is Multicast by configuration center broadcast, do not run the two parts on the same machine, if you have to do so, set <code>unicast=false</code>, like <code>multicast://224.5.6.7:1234?unicast=false</code>, or the unicast send to consumer will be taken by provider, and the same for consumers. Only multicast has this issue</p>
-<p>You can run multiple Demo Provider and Demo consumer to verify load balance. Demo Consumer can run multi instance directly. Because of port conflict, you can either run multi Demo Providers on different machines or modify the value of <code>dubbo.protocol.port</code> in <code>conf/dubbo.properties</code> under the install directory of <code>conf/dubbo.properties</code></p>
-<p>You can add Simple Monitor as a monitor center, the default discovery strategy is Multicast by configuration center broadcast, display the dependency relationship, call times and cost</p>
-<p>You can use Zookeeper instead of Multicast as the configuration center, after Zookeeper Registry installation, modify <code>conf/dubbo.properties</code> under the installation directory of Demo Provider, Demo Consumer and Simple Monitor, change the value of <code>dubbo.registry.address</code> to <code>zookeeper://127.0.0.1:2181</code>(<code>redis://127.0.0.1:6379</code> for Redis Registry). the value for Simple Registry is <code>dubbo://127.0.0.1:9090</code></p>
-<p>Zookeeper configuration address is recommended</p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/introduction.json b/en-us/docs/admin/install/introduction.json
deleted file mode 100644
index 4821997..0000000
--- a/en-us/docs/admin/install/introduction.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "introduction.md",
- "__html": "<h1>Install manual</h1>\n<p>You can run Demo Provider and Demo Consumer only, the default discovery strategy is Multicast by configuration center broadcast, do not run the two parts on the same machine, if you have to do so, set <code>unicast=false</code>, like <code>multicast://224.5.6.7:1234?unicast=false</code>, or the unicast send to consumer will be taken by provider, and the same for consumers. Only multicast has this issue</p>\n<p>You can run multiple Demo Provider an [...]
- "link": "/en-us/docs/admin/install/introduction.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/provider-demo.html b/en-us/docs/admin/install/provider-demo.html
deleted file mode 100644
index ef9c7e9..0000000
--- a/en-us/docs/admin/install/provider-demo.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="provider-demo" />
- <meta name="description" content="provider-demo" />
- <!-- 网页标签标题 -->
- <title>provider-demo</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>install:</p>
-<pre><code class="language-sh">git <span class="hljs-built_in">clone</span> https://github.com/apache/dubbo.git
-<span class="hljs-built_in">cd</span> dubbo
-run org.apache.dubbo.demo.provider.Provider under dubbo-demo-provider module
-add -Djava.net.preferIPv4Stack=<span class="hljs-literal">true</span> <span class="hljs-keyword">if</span> your IDE is Intellij Idea
-</code></pre>
-<p>configuration:</p>
-<pre><code class="language-sh">resource/META-INFO.spring/dubbo-demo-provider.xml
-change dubbo:registry to a real registry server address, zookeeper is recommanded
-</code></pre>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/provider-demo.json b/en-us/docs/admin/install/provider-demo.json
deleted file mode 100644
index 64105fd..0000000
--- a/en-us/docs/admin/install/provider-demo.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "provider-demo.md",
- "__html": "<h1>install demo provider</h1>\n<p>install:</p>\n<pre><code class=\"language-sh\">git <span class=\"hljs-built_in\">clone</span> https://github.com/apache/dubbo.git\n<span class=\"hljs-built_in\">cd</span> dubbo\nrun org.apache.dubbo.demo.provider.Provider under dubbo-demo-provider module\nadd -Djava.net.preferIPv4Stack=<span class=\"hljs-literal\">true</span> <span class=\"hljs-keyword\">if</span> your IDE is Intellij Idea\n</code></pre>\n<p>configuration:</p>\n<pre><code c [...]
- "link": "/en-us/docs/admin/install/provider-demo.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/redis.html b/en-us/docs/admin/install/redis.html
deleted file mode 100644
index 49b81b4..0000000
--- a/en-us/docs/admin/install/redis.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="redis" />
- <meta name="description" content="redis" />
- <!-- 网页标签标题 -->
- <title>redis</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>Redis <sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup> introductions, please refer to: <a href="http://dubbo.apache.org/books/dubbo-user-book-en/references/registry/redis.html">Redis application center manual</a>。</p>
-<p>you need an origin Redis server only, and change the value from <code>dubbo.registry.addrss</code> to <code>redis://127.0.0.1:6379</code> in <code>conf/dubbo.properties</code> of <a href="http://dubbo.apache.org/books/dubbo-user-book-en/quick-start.html">quick start</a></p>
-<p>Redis configuration center cluster <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup> write multiple server in client side and read from a single server.</p>
-<p>Install:</p>
-<pre><code class="language-sh">wget http://redis.googlecode.com/files/redis-2.4.8.tar.gz
-tar xzf redis-2.4.8.tar.gz
-<span class="hljs-built_in">cd</span> redis-2.4.8
-make
-</code></pre>
-<p>Configuration:</p>
-<pre><code class="language-sh">vi redis.conf
-</code></pre>
-<p>Start:</p>
-<pre><code class="language-sh">nohup ./src/redis-server redis.conf &
-</code></pre>
-<p>Stop:</p>
-<pre><code class="language-sh">killall redis-server
-</code></pre>
-<ul>
-<li>Command line <sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup>:</li>
-</ul>
-<pre><code class="language-sh">./src/redis-cli
-hgetall /dubbo/com.foo.BarService/providers
-</code></pre>
-<p>Or:</p>
-<pre><code class="language-sh">telnet 127.0.0.1 6379
-hgetall /dubbo/com.foo.BarService/providers
-</code></pre>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p>Redis is a high performance KV store server, please refer to: <a href="http://redis.io/topics/quickstart">http://redis.io/topics/quickstart</a> <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn2" class="footnote-item"><p>Support for version <code>2.1.0</code> and higher <a href="#fnref2" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn3" class="footnote-item"><p>Please refer to: <a href="http://redis.io/commands">http://redis.io/commands</a> <a href="#fnref3" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/redis.json b/en-us/docs/admin/install/redis.json
deleted file mode 100644
index 3ac1038..0000000
--- a/en-us/docs/admin/install/redis.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "redis.md",
- "__html": "<h1>install Redis register center</h1>\n<p>Redis <sup class=\"footnote-ref\"><a href=\"#fn1\" id=\"fnref1\">[1]</a></sup> introductions, please refer to: <a href=\"http://dubbo.apache.org/books/dubbo-user-book-en/references/registry/redis.html\">Redis application center manual</a>。</p>\n<p>you need an origin Redis server only, and change the value from <code>dubbo.registry.addrss</code> to <code>redis://127.0.0.1:6379</code> in <code>conf/dubbo.properties</code> of <a href=\ [...]
- "link": "/en-us/docs/admin/install/redis.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/simple-monitor-center.html b/en-us/docs/admin/install/simple-monitor-center.html
deleted file mode 100644
index 1a47971..0000000
--- a/en-us/docs/admin/install/simple-monitor-center.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="simple-monitor-center" />
- <meta name="description" content="simple-monitor-center" />
- <!-- 网页标签标题 -->
- <title>simple-monitor-center</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h4>The function of monitor center will be merged to dubbo admin, based on metrics, coming soon</h4>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/simple-monitor-center.json b/en-us/docs/admin/install/simple-monitor-center.json
deleted file mode 100644
index 3650495..0000000
--- a/en-us/docs/admin/install/simple-monitor-center.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "simple-monitor-center.md",
- "__html": "<h1>install Simple monitor center</h1>\n<h4>The function of monitor center will be merged to dubbo admin, based on metrics, coming soon</h4>\n",
- "link": "/en-us/docs/admin/install/simple-monitor-center.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/simple-registry-center.html b/en-us/docs/admin/install/simple-registry-center.html
deleted file mode 100644
index 2b46c5e..0000000
--- a/en-us/docs/admin/install/simple-registry-center.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="simple-registry-center" />
- <meta name="description" content="simple-registry-center" />
- <!-- 网页标签标题 -->
- <title>simple-registry-center</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/simple-registry-center.json b/en-us/docs/admin/install/simple-registry-center.json
deleted file mode 100644
index 1231365..0000000
--- a/en-us/docs/admin/install/simple-registry-center.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "simple-registry-center.md",
- "__html": "<h1>install Simple configuration center</h1>\n",
- "link": "/en-us/docs/admin/install/simple-registry-center.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/install/zookeeper.html b/en-us/docs/admin/install/zookeeper.html
deleted file mode 100644
index 0884c09..0000000
--- a/en-us/docs/admin/install/zookeeper.html
+++ /dev/null
@@ -1,101 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="zookeeper" />
- <meta name="description" content="zookeeper" />
- <!-- 网页标签标题 -->
- <title>zookeeper</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>zookeeper register center client version: <code>dubbo-2.3.3</code> and above<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></p>
-<p>Dubbo changes nothing of Zookeeper's server side, an original Zookeeper server is fine. All change happens while calling Zookeeper's client side</p>
-<p>install:</p>
-<pre><code class="language-sh">wget http://archive.apache.org/dist/zookeeper/zookeeper-3.3.3/zookeeper-3.3.3.tar.gz
-tar zxvf zookeeper-3.3.3.tar.gz
-<span class="hljs-built_in">cd</span> zookeeper-3.3.3
-cp conf/zoo_sample.cfg conf/zoo.cfg
-</code></pre>
-<p>configuration:</p>
-<pre><code class="language-sh">vi conf/zoo.cfg
-</code></pre>
-<p>If cluster is not needed, the content of <code>zoo.cfg</code> is as below <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup>:</p>
-<pre><code class="language-properties"><span class="hljs-attr">tickTime</span>=<span class="hljs-string">2000</span>
-<span class="hljs-attr">initLimit</span>=<span class="hljs-string">10</span>
-<span class="hljs-attr">syncLimit</span>=<span class="hljs-string">5</span>
-<span class="hljs-attr">dataDir</span>=<span class="hljs-string">/home/dubbo/zookeeper-3.3.3/data</span>
-<span class="hljs-attr">clientPort</span>=<span class="hljs-string">2181</span>
-</code></pre>
-<p>If cluster is needed, the content of <code>zoo.cfg</code> is as below <sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup>:</p>
-<pre><code class="language-properties"><span class="hljs-attr">tickTime</span>=<span class="hljs-string">2000</span>
-<span class="hljs-attr">initLimit</span>=<span class="hljs-string">10</span>
-<span class="hljs-attr">syncLimit</span>=<span class="hljs-string">5</span>
-<span class="hljs-attr">dataDir</span>=<span class="hljs-string">/home/dubbo/zookeeper-3.3.3/data</span>
-<span class="hljs-attr">clientPort</span>=<span class="hljs-string">2181</span>
-<span class="hljs-meta">server.1</span>=<span class="hljs-string">10.20.153.10:2555:3555</span>
-<span class="hljs-meta">server.2</span>=<span class="hljs-string">10.20.153.11:2555:3555</span>
-</code></pre>
-<p>Put myid file in data directory <sup class="footnote-ref"><a href="#fn4" id="fnref4">[4]</a></sup>:</p>
-<pre><code class="language-sh">mkdir data
-vi myid
-</code></pre>
-<p>Myid is the number after <code>server</code> in <code>zoo.cfg</code>. The first one's content is 1, the second one's content is 2:</p>
-<pre><code>1
-</code></pre>
-<p>Start:</p>
-<pre><code class="language-sh">./bin/zkServer.sh start
-</code></pre>
-<p>Stop:</p>
-<pre><code class="language-sh">./bin/zkServer.sh stop
-</code></pre>
-<p>Command line <sup class="footnote-ref"><a href="#fn5" id="fnref5">[5]</a></sup>:</p>
-<pre><code class="language-sh">telnet 127.0.0.1 2181
-dump
-</code></pre>
-<p>Or:</p>
-<pre><code class="language-shell">echo dump | nc 127.0.0.1 2181
-</code></pre>
-<p>Usage:</p>
-<pre><code class="language-xml">dubbo.registry.address=zookeeper://10.20.153.10:2181?backup=10.20.153.11:2181
-</code></pre>
-<p>Or:</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:registry</span> <span class="hljs-attr">protocol</span>=<span class="hljs-string">"zookeeper"</span> <span class="hljs-attr">address</span>=<span class="hljs-string">"10.20.153.10:2181,10.20.153.11:2181"</span> /></span>
-</code></pre>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p>Zookeeper is a sub project of Apache <a href="http://Hadoop.As">Hadoop.As</a> it is robust, we recommend to use in production environment. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn2" class="footnote-item"><p>Data directory should be changed into your real output directory <a href="#fnref2" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn3" class="footnote-item"><p>Data directory and server address should be changed into your real machine information <a href="#fnref3" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn4" class="footnote-item"><p><code>dataDir</code> in <code>zoo.cfg</code> <a href="#fnref4" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn5" class="footnote-item"><p><a href="http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html">http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html</a> <a href="#fnref5" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/install/zookeeper.json b/en-us/docs/admin/install/zookeeper.json
deleted file mode 100644
index 22a53b8..0000000
--- a/en-us/docs/admin/install/zookeeper.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "zookeeper.md",
- "__html": "<h1>install Zookeeper configuration center</h1>\n<p>zookeeper register center client version: <code>dubbo-2.3.3</code> and above<sup class=\"footnote-ref\"><a href=\"#fn1\" id=\"fnref1\">[1]</a></sup></p>\n<p>Dubbo changes nothing of Zookeeper's server side, an original Zookeeper server is fine. All change happens while calling Zookeeper's client side</p>\n<p>install:</p>\n<pre><code class=\"language-sh\">wget http://archive.apache.org/dist/zookeeper/zookeeper-3.3.3/zookeepe [...]
- "link": "/en-us/docs/admin/install/zookeeper.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/introduction.html b/en-us/docs/admin/introduction.html
deleted file mode 100644
index f61ce91..0000000
--- a/en-us/docs/admin/introduction.html
+++ /dev/null
@@ -1,95 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="introduction" />
- <meta name="description" content="introduction" />
- <!-- 网页标签标题 -->
- <title>introduction</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>Now version 0.1 has been released, frontend uses Vue and Vuetify as javascript framework and UI framework, backend uses spring framework, you can deploy the whole project with maven or deploy frontend and backend separately.</p>
-<h3>Deploy the whole project through maven</h3>
-<ul>
-<li>install</li>
-</ul>
-<pre><code class="language-sh">git <span class="hljs-built_in">clone</span> https://github.com/apache/dubbo-admin.git
-<span class="hljs-built_in">cd</span> dubbo-admin
-mvn clean package
-<span class="hljs-built_in">cd</span> dubbo-admin-distribution/target
-java -jar dubbo-admin-0.1.jar
-</code></pre>
-<ul>
-<li>visit<br>
-<a href="http://localhost:8080">http://localhost:8080</a></li>
-</ul>
-<h3>Deploy frontend and backend separately</h3>
-<ul>
-<li>frontend deploy</li>
-</ul>
-<pre><code class="language-sh"><span class="hljs-built_in">cd</span> dubbo-admin-ui
-npm run install
-npm run dev
-</code></pre>
-<ul>
-<li>backend deploy</li>
-</ul>
-<pre><code class="language-sh"><span class="hljs-built_in">cd</span> dubbo-admin-server
-mvn clean package
-<span class="hljs-built_in">cd</span> target
-java -jar dubbo-admin-server-0.1.jar
-</code></pre>
-<ul>
-<li>visit<br>
-<a href="http://localhost:8081">http://localhost:8081</a></li>
-<li>in this mode, any modify of frontend will be hot reloaded</li>
-</ul>
-<h3>configuration: <sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></h3>
-<p>configuration file location</p>
-<pre><code class="language-sh">dubbo-admin-server/src/main/resources/application.properties
-</code></pre>
-<p>configuration:</p>
-<pre><code class="language-properties"><span class="hljs-meta">admin.config-center</span>=<span class="hljs-string">zookeeper://127.0.0.1:2181</span>
-<span class="hljs-meta">admin.registry.address</span>=<span class="hljs-string">zookeeper://127.0.0.1:2181</span>
-<span class="hljs-meta">admin.metadata-report.address</span>=<span class="hljs-string">zookeeper://127.0.0.1:2181</span>
-</code></pre>
-<p>the three configure item above are configuration center, registry center and metadata center respectively, you can find explanation about the three centers <a href="../user/configuration/config-center.md">here</a>
-Same as Dubbo 2.7, you can set the addresses of metadata center and registry center on configuration center, in zookeeper, the path and content are as below:</p>
-<pre><code class="language-properties"><span class="hljs-comment"># /dubbo/config/dubbo/dubbo.properties</span>
-<span class="hljs-meta">dubbo.registry.address</span>=<span class="hljs-string">zookeeper://127.0.0.1:2181</span>
-<span class="hljs-meta">dubbo.metadata-report.address</span>=<span class="hljs-string">zookeeper://127.0.0.1:2181</span>
-</code></pre>
-<p>the addresses in configuration center have higher priority than those in <code>application.properties</code></p>
-<p>visit documents on github:</p>
-<pre><code class="language-sh">https://github.com/apache/dubbo-admin
-</code></pre>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p>there's no login module in the current version. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/introduction.json b/en-us/docs/admin/introduction.json
deleted file mode 100644
index ec39b06..0000000
--- a/en-us/docs/admin/introduction.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "introduction.md",
- "__html": "<h1>Dubbo Admin introduction</h1>\n<p>Now version 0.1 has been released, frontend uses Vue and Vuetify as javascript framework and UI framework, backend uses spring framework, you can deploy the whole project with maven or deploy frontend and backend separately.</p>\n<h3>Deploy the whole project through maven</h3>\n<ul>\n<li>install</li>\n</ul>\n<pre><code class=\"language-sh\">git <span class=\"hljs-built_in\">clone</span> https://github.com/apache/dubbo-admin.git\n<span cl [...]
- "link": "/en-us/docs/admin/introduction.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/dubbo-ops.html b/en-us/docs/admin/ops/dubbo-ops.html
deleted file mode 100644
index 45a1318..0000000
--- a/en-us/docs/admin/ops/dubbo-ops.html
+++ /dev/null
@@ -1,44 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="dubbo-ops" />
- <meta name="description" content="dubbo-ops" />
- <!-- 网页标签标题 -->
- <title>dubbo-ops</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>Page search</h2>
-<p>If you need to manage a Dubbo service, you need to search it first and open it's management page</p>
-<p><img src="../sources/images/dubbo-search.jpg" alt="/admin-guide/images/dubbo-search.png"></p>
-<h2>Service provider page</h2>
-<p><img src="../sources/images/dubbo-providers.jpg" alt="/admin-guide/images/dubbo-providers.png"></p>
-<h2>Service consumer page</h2>
-<p><img src="../sources/images/dubbo-consumers.jpg" alt="/admin-guide/images/dubbo-consumers.png"></p>
-<h2>Add route rule page</h2>
-<p><img src="../sources/images/dubbo-add-route.jpg" alt="/admin-guide/images/dubbo-add-route.png"></p>
-<h2>Add dynamic configuration page</h2>
-<p><img src="../sources/images/dubbo-add-config.jpg" alt="/admin-guide/images/dubbo-add-config.png"></p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/dubbo-ops.json b/en-us/docs/admin/ops/dubbo-ops.json
deleted file mode 100644
index 1decedb..0000000
--- a/en-us/docs/admin/ops/dubbo-ops.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "dubbo-ops.md",
- "__html": "<h1>Ops console management</h1>\n<h2>Page search</h2>\n<p>If you need to manage a Dubbo service, you need to search it first and open it's management page</p>\n<p><img src=\"../sources/images/dubbo-search.jpg\" alt=\"/admin-guide/images/dubbo-search.png\"></p>\n<h2>Service provider page</h2>\n<p><img src=\"../sources/images/dubbo-providers.jpg\" alt=\"/admin-guide/images/dubbo-providers.png\"></p>\n<h2>Service consumer page</h2>\n<p><img src=\"../sources/images/dubbo-consume [...]
- "link": "/en-us/docs/admin/ops/dubbo-ops.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/introduction.html b/en-us/docs/admin/ops/introduction.html
deleted file mode 100644
index f6c3c3f..0000000
--- a/en-us/docs/admin/ops/introduction.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="introduction" />
- <meta name="description" content="introduction" />
- <!-- 网页标签标题 -->
- <title>introduction</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/introduction.json b/en-us/docs/admin/ops/introduction.json
deleted file mode 100644
index bca737c..0000000
--- a/en-us/docs/admin/ops/introduction.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "introduction.md",
- "__html": "<h1>Ops manual</h1>\n",
- "link": "/en-us/docs/admin/ops/introduction.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/pinpoint.html b/en-us/docs/admin/ops/pinpoint.html
deleted file mode 100644
index f8a33fe..0000000
--- a/en-us/docs/admin/ops/pinpoint.html
+++ /dev/null
@@ -1,403 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="pinpoint" />
- <meta name="description" content="pinpoint" />
- <!-- 网页标签标题 -->
- <title>pinpoint</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).</p>
-<h2>What is Pinpoint</h2>
-<p><a href="https://github.com/naver/pinpoint">Pinpoint</a> is an APM (Application Performance Management) tool for large-scale distributed systems written in Java. Inspired by Dapper, Pinpoint provides a solution to help analyze the overall structure of the system and how components within them are interconnected by tracing transactions across distributed applications.</p>
-<p>You should definitely check Pinpoint out If you want to</p>
-<p>understand your application topology at a glance
-monitor your application in Real-Time
-gain code-level visibility to every transaction
-install APM Agents without changing a single line of code
-have minimal impact on the performance (approximately 3% increase in resource usage)</p>
-<h3>ServerMap</h3>
-<p>Understand the topology of any distributed systems by visualizing how their components are interconnected. Clicking on a node reveals details about the component, such as its current status, and transaction count.</p>
-<h3>Realtime Active Thread Chart</h3>
-<p>Monitor active threads inside applications in real-time.</p>
-<h3>Request/Response Scatter Chart</h3>
-<p>Visualize request count and response patterns over time to identify potential problems. Transactions can be selected for additional detail by dragging over the chart.</p>
-<h3>CallStack</h3>
-<p>Gain code-level visibility to every transaction in a distributed environment, identifying bottlenecks and points of failure in a single view.</p>
-<h3>Inspector</h3>
-<p>View additional details on the application such as CPU usage, Memory/Garbage Collection, TPS, and JVM arguments.</p>
-<h3>Supported Modules (last updated 2018/04/01)</h3>
-<ul>
-<li>JDK 6+</li>
-<li>Tomcat 6/7/8, Jetty 8/9, JBoss EAP 6, Resin 4, Websphere 6/7/8, Vertx 3.3/3.4/3.5</li>
-<li>Spring, Spring Boot (Embedded Tomcat, Jetty)</li>
-<li>Apache HTTP Client 3.x/4.x, JDK HttpConnector, GoogleHttpClient, OkHttpClient, NingAsyncHttpClient</li>
-<li>Thrift Client, Thrift Service, DUBBO PROVIDER, DUBBO CONSUMER</li>
-<li>ActiveMQ, RabbitMQ</li>
-<li>MySQL, Oracle, MSSQL, CUBRID,POSTGRESQL, MARIA</li>
-<li>Arcus, Memcached, Redis, CASSANDRA</li>
-<li>iBATIS, MyBatis</li>
-<li>DBCP, DBCP2, HIKARICP</li>
-<li>gson, Jackson, Json Lib</li>
-<li>log4j, Logback</li>
-</ul>
-<h2>Pinpoint and Dubbo</h2>
-<h3>Quickstart Pinpoint</h3>
-<p><a href="http://naver.github.io/pinpoint/quickstart.html">Quick start</a>（No neet to start TestApp）</p>
-<h3>Dubbo demo</h3>
-<h4>Create API module</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span>
- <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<p>Create API interface：</p>
-<pre><code>package com.example.demoapi;
-
-public interface HelloService {
- String sayHello(String name);
-}
-</code></pre>
-<h4>Dubbo provider</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span> <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-provider<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">packaging</span>></span>jar<span class="hljs-tag"></<span class="hljs-name">packaging</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">name</span>></span>demo-provider<span class="hljs-tag"></<span class="hljs-name">name</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">parent</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-parent<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>2.0.3.RELEASE<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">relativePath</span>/></span> <span class="hljs-comment"><!-- lookup parent from repository --></span>
- <span class="hljs-tag"></<span class="hljs-name">parent</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">properties</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.build.sourceEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.build.sourceEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.reporting.outputEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.reporting.outputEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">java.version</span>></span>1.8<span class="hljs-tag"></<span class="hljs-name">java.version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">properties</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">repositories</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>sonatype-nexus-snapshots<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">url</span>></span>https://oss.sonatype.org/content/repositories/snapshots<span class="hljs-tag"></<span class="hljs-name">url</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>false<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>true<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repositories</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependencies</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.alibaba.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>dubbo-spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.2.0<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-test<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">scope</span>></span>test<span class="hljs-tag"></<span class="hljs-name">scope</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependencies</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">build</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-maven-plugin<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">build</span>></span>
-
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<ol>
-<li><code>HelloService</code> interface：</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.demoprovider.provider;
-
-<span class="hljs-keyword">import</span> org.apache.dubbo.config.annotation.Service;
-<span class="hljs-keyword">import</span> com.example.demoapi.HelloService;
-
-<span class="hljs-meta">@Service</span>(version = <span class="hljs-string">"${demo.service.version}"</span>,
- application = <span class="hljs-string">"${dubbo.application.id}"</span>,
- protocol = <span class="hljs-string">"${dubbo.protocol.id}"</span>,
- registry = <span class="hljs-string">"${dubbo.registry.id}"</span>)
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">HelloServiceImpl</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">HelloService</span> </span>{
- <span class="hljs-keyword">static</span> <span class="hljs-keyword">int</span> i = <span class="hljs-number">0</span>;
- <span class="hljs-meta">@Override</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(String name)</span> </span>{
- i++;
- <span class="hljs-keyword">if</span> (i % <span class="hljs-number">3</span> == <span class="hljs-number">0</span>) {
- <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> RuntimeException(<span class="hljs-string">"ex"</span>);
- }
- <span class="hljs-keyword">return</span> <span class="hljs-string">"Hello "</span> + name + <span class="hljs-string">"!"</span>;
- }
-}
-</code></pre>
-<ol start="2">
-<li>Spring Boot bootstrap：</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.demoprovider;
-
-<span class="hljs-keyword">import</span> org.springframework.boot.SpringApplication;
-<span class="hljs-keyword">import</span> org.springframework.boot.autoconfigure.SpringBootApplication;
-
-<span class="hljs-meta">@SpringBootApplication</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoProviderApplication</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- SpringApplication.run(DemoProviderApplication.class, args);
- }
-}
-</code></pre>
-<ol start="3">
-<li><code>application.properties</code>：</li>
-</ol>
-<pre><code class="language-properties"><span class="hljs-comment"># Spring boot application</span>
-<span class="hljs-meta">spring.application.name</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-meta">server.port</span> = <span class="hljs-string">9090</span>
-<span class="hljs-meta">management.port</span> = <span class="hljs-string">9091</span>
-<span class="hljs-comment">
-# Service version</span>
-<span class="hljs-meta">demo.service.version</span> = <span class="hljs-string">1.0.0</span>
-<span class="hljs-comment">
-# Base packages to scan Dubbo Components (e.g @Service , @Reference)</span>
-<span class="hljs-meta">dubbo.scan.basePackages</span> = <span class="hljs-string">com.example.demoprovider</span>
-<span class="hljs-comment">
-# Dubbo Config properties</span>
-<span class="hljs-comment">## ApplicationConfig Bean</span>
-<span class="hljs-meta">dubbo.application.id</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-meta">dubbo.application.name</span> = <span class="hljs-string">dubbo-provider-demo</span>
-<span class="hljs-comment">
-## ProtocolConfig Bean</span>
-<span class="hljs-meta">dubbo.protocol.id</span> = <span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.name</span> = <span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.port</span> = <span class="hljs-string">12345</span>
-<span class="hljs-comment">
-## RegistryConfig Bean</span>
-<span class="hljs-meta">dubbo.registry.id</span> = <span class="hljs-string">my-registry</span>
-<span class="hljs-meta">dubbo.registry.address</span> = <span class="hljs-string">N/A</span>
-</code></pre>
-<h4>Dubbo consumer</h4>
-<p>pom.xml</p>
-<pre><code class="language-xml"><span class="hljs-meta"><?xml version="1.0" encoding="UTF-8"?></span>
-<span class="hljs-tag"><<span class="hljs-name">project</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0"</span> <span class="hljs-attr">xmlns:xsi</span>=<span class="hljs-string">"http://www.w3.org/2001/XMLSchema-instance"</span>
- <span class="hljs-attr">xsi:schemaLocation</span>=<span class="hljs-string">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">modelVersion</span>></span>4.0.0<span class="hljs-tag"></<span class="hljs-name">modelVersion</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-consumer<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">packaging</span>></span>jar<span class="hljs-tag"></<span class="hljs-name">packaging</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">name</span>></span>demo-consumer<span class="hljs-tag"></<span class="hljs-name">name</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">parent</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-parent<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>2.0.3.RELEASE<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">relativePath</span>/></span> <span class="hljs-comment"><!-- lookup parent from repository --></span>
- <span class="hljs-tag"></<span class="hljs-name">parent</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">properties</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.build.sourceEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.build.sourceEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">project.reporting.outputEncoding</span>></span>UTF-8<span class="hljs-tag"></<span class="hljs-name">project.reporting.outputEncoding</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">java.version</span>></span>1.8<span class="hljs-tag"></<span class="hljs-name">java.version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">properties</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">repositories</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">id</span>></span>sonatype-nexus-snapshots<span class="hljs-tag"></<span class="hljs-name">id</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">url</span>></span>https://oss.sonatype.org/content/repositories/snapshots<span class="hljs-tag"></<span class="hljs-name">url</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>false<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">releases</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">enabled</span>></span>true<span class="hljs-tag"></<span class="hljs-name">enabled</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">snapshots</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repository</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">repositories</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependencies</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-web<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.alibaba.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>dubbo-spring-boot-starter<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.2.0<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>com.example<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>demo-api<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">version</span>></span>0.0.1-SNAPSHOT<span class="hljs-tag"></<span class="hljs-name">version</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-starter-test<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">scope</span>></span>test<span class="hljs-tag"></<span class="hljs-name">scope</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependency</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">dependencies</span>></span>
-
- <span class="hljs-tag"><<span class="hljs-name">build</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">groupId</span>></span>org.springframework.boot<span class="hljs-tag"></<span class="hljs-name">groupId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">artifactId</span>></span>spring-boot-maven-plugin<span class="hljs-tag"></<span class="hljs-name">artifactId</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">configuration</span>></span>
- <span class="hljs-tag"><<span class="hljs-name">classifier</span>></span>exec<span class="hljs-tag"></<span class="hljs-name">classifier</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">configuration</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugin</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">plugins</span>></span>
- <span class="hljs-tag"></<span class="hljs-name">build</span>></span>
-
-<span class="hljs-tag"></<span class="hljs-name">project</span>></span>
-</code></pre>
-<ol>
-<li><code>@Reference</code> injection <code>HelloService</code></li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.democonsumer.controller;
-
-<span class="hljs-keyword">import</span> org.apache.dubbo.config.annotation.Reference;
-<span class="hljs-keyword">import</span> com.example.demoapi.HelloService;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RequestMapping;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RequestParam;
-<span class="hljs-keyword">import</span> org.springframework.web.bind.annotation.RestController;
-
-<span class="hljs-meta">@RestController</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoConsumerController</span> </span>{
- <span class="hljs-meta">@Reference</span>(version = <span class="hljs-string">"${demo.service.version}"</span>,
- application = <span class="hljs-string">"${dubbo.application.id}"</span>,
- url = <span class="hljs-string">"dubbo://<Real IP Address>:12345"</span>)
- <span class="hljs-keyword">private</span> HelloService helloService;
-
- <span class="hljs-meta">@RequestMapping</span>(<span class="hljs-string">"/sayHello"</span>)
- <span class="hljs-function"><span class="hljs-keyword">public</span> String <span class="hljs-title">sayHello</span><span class="hljs-params">(@RequestParam String name)</span> </span>{
- <span class="hljs-keyword">return</span> helloService.sayHello(name);
- }
-}
-</code></pre>
-<ol start="2">
-<li>Spring Boot bootstrap:</li>
-</ol>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.example.democonsumer;
-
-<span class="hljs-keyword">import</span> org.springframework.boot.SpringApplication;
-<span class="hljs-keyword">import</span> org.springframework.boot.autoconfigure.SpringBootApplication;
-
-<span class="hljs-meta">@SpringBootApplication</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">DemoConsumerApplication</span> </span>{
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">void</span> <span class="hljs-title">main</span><span class="hljs-params">(String[] args)</span> </span>{
- SpringApplication.run(DemoConsumerApplication.class, args);
- }
-}
-</code></pre>
-<ol start="3">
-<li><code>application.properties</code>:</li>
-</ol>
-<pre><code class="language-properties"><span class="hljs-comment"># Spring boot application</span>
-<span class="hljs-meta">spring.application.name</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-meta">server.port</span>=<span class="hljs-string">8080</span>
-<span class="hljs-meta">management.port</span>=<span class="hljs-string">8081</span>
-<span class="hljs-comment">
-# Service Version</span>
-<span class="hljs-meta">demo.service.version</span>=<span class="hljs-string">1.0.0</span>
-<span class="hljs-comment">
-# Dubbo Config properties</span>
-<span class="hljs-comment">## ApplicationConfig Bean</span>
-<span class="hljs-meta">dubbo.application.id</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-meta">dubbo.application.name</span>=<span class="hljs-string">dubbo-consumer-demo</span>
-<span class="hljs-comment">
-## ProtocolConfig Bean</span>
-<span class="hljs-meta">dubbo.protocol.id</span>=<span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.name</span>=<span class="hljs-string">dubbo</span>
-<span class="hljs-meta">dubbo.protocol.port</span>=<span class="hljs-string">12345</span>
-</code></pre>
-<h3>Using Pinpoint-agent to start <code>Dubbo provider</code> and <code>Dubbo consumer</code></h3>
-<ol>
-<li>Maven clean package</li>
-</ol>
-<pre><code>mvn clean package
-</code></pre>
-<ol start="2">
-<li>Start provider</li>
-</ol>
-<pre><code>java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-provider -Dpinpoint.applicationName=DP target/demo-provider-0.0.1-SNAPSHOT.jar
-</code></pre>
-<ol start="3">
-<li>Start consumer</li>
-</ol>
-<pre><code>java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-consumer -Dpinpoint.applicationName=DC target/demo-comsumer-0.0.1-SNAPSHOT-exec.jar
-</code></pre>
-<ol start="4">
-<li>Access the consumer address to simulate user requests</li>
-</ol>
-<p><code>http://localhost:8080/sayHello?name=ABC</code></p>
-<h2>Using Pinpoint locate problems</h2>
-<h3>Homepage</h3>
-<p><img src="../sources/images/pinpoint-home.png" alt="/admin-guide/images/pinpoint-home.png"></p>
-<blockquote>
-<p>The user request here is double the number of requests for DubboProvider, because the favicon.ico icon request is recorded.</p>
-</blockquote>
-<h3>Call tree</h3>
-<p><img src="../sources/images/pinpoint-calltree.png" alt="/admin-guide/images/pinpoint-calltree.png"></p>
-<h3>Mixed view</h3>
-<p><img src="../sources/images/pinpoint-mixedview.png" alt="/admin-guide/images/pinpoint-mixedview.png"></p>
-<h3>Other</h3>
-<p>The example simply simulates the provision and call of Dubbo, and does not carry out the application of other middleware such as database. For detailed use, please refer to the Pinpoint document.</p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/pinpoint.json b/en-us/docs/admin/ops/pinpoint.json
deleted file mode 100644
index 7451bde..0000000
--- a/en-us/docs/admin/ops/pinpoint.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "pinpoint.md",
- "__html": "<h1>Tracking with Pinpoint</h1>\n<p>After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).< [...]
- "link": "/en-us/docs/admin/ops/pinpoint.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/skywalking.html b/en-us/docs/admin/ops/skywalking.html
deleted file mode 100644
index 6a0917b..0000000
--- a/en-us/docs/admin/ops/skywalking.html
+++ /dev/null
@@ -1,131 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="skywalking" />
- <meta name="description" content="skywalking" />
- <!-- 网页标签标题 -->
- <title>skywalking</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>Introduction to Apache Skywalking(Incubator)</h2>
-<p><a href="https://github.com/apache/incubator-skywalking">Apache Skywalking(Incubator)</a> is the APM system that it designed for micro-services architectures and cloud native architecture systems and supports distribute tracking. <a href="https://github.com/apache/incubator-skywalking">Apache skywalking (incubator)</a> collects and analyzes the trace data and generates the relationship between the application and the service metric, Apache skywalking supports multiple languages agen [...]
-<p>Currently, Skywalking has supported analysis the operation of distributed systems from 6 visual dimensions. The overview view is a global view of your applications and components, including the number of components and applications, application alarm fluctuations, slow service lists, and application throughput; The topology shows the topological relationship of the whole application; The application view represents the upstream and downstream relationship of the application from singl [...]
-<h2>Dubbo and Apache Skywalking(Incubator)</h2>
-<h3>Build the Dubbo demo project</h3>
-<p>The Dubbo demo has been uploaded to the <a href="https://github.com/SkywalkingTest/dubbo-trace-example">GitHub repository</a>.</p>
-<h4>API project</h4>
-<p>Service interface definition:
-package org.apache.skywalking.demo.interfaces;</p>
-<p>public interface HelloService {
-String sayHello(String name);
-}</p>
-<h4>Service provider project</h4>
-<p>package org.apache.skywalking.demo.provider;</p>
-<p>@Service(version = "<span class="katex"><span class="katex-mathml"><math><semantics><mrow><mrow><mi>d</mi><mi>e</mi><mi>m</mi><mi>o</mi><mi mathvariant="normal">.</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>v</mi><mi>i</mi><mi>c</mi><mi>e</mi><mi mathvariant="normal">.</mi><mi>v</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>i</mi><mi>o</mi><mi>n</mi></mrow><mi mathvariant="normal">"</mi><mo separator="true">,</mo><mi>a</mi><mi>p</mi><mi>p</mi><mi>l</mi><mi>i</mi><mi>c</mi><mi>a</mi><mi>t< [...]
- application = "</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="strut" style="height:0.69444em;"></span><span class="strut bottom" style="height:0.8888799999999999em;vertical-align:-0.19444em;"></span><span class="base textstyle uncramped"><span class="mord textstyle uncramped"><span class="mord mathit">d</span><span class="mord mathit">e</span><span class="mord mathit">m</span><span class="mord mathit">o</span><span class="mord mathrm [...]
-protocol = "<span class="katex"><span class="katex-mathml"><math><semantics><mrow><mrow><mi>d</mi><mi>u</mi><mi>b</mi><mi>b</mi><mi>o</mi><mi mathvariant="normal">.</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>t</mi><mi>o</mi><mi>c</mi><mi>o</mi><mi>l</mi><mi mathvariant="normal">.</mi><mi>i</mi><mi>d</mi></mrow><mi mathvariant="normal">"</mi><mo separator="true">,</mo><mi>r</mi><mi>e</mi><mi>g</mi><mi>i</mi><mi>s</mi><mi>t</mi><mi>r</mi><mi>y</mi><mo>=</mo><mi mathvariant="normal">&q [...]
- registry = "</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="strut" style="height:0.69444em;"></span><span class="strut bottom" style="height:0.8888799999999999em;vertical-align:-0.19444em;"></span><span class="base textstyle uncramped"><span class="mord textstyle uncramped"><span class="mord mathit">d</span><span class="mord mathit">u</span><span class="mord mathit">b</span><span class="mord mathit">b</span><span class="mord mathit">o [...]
-public class HelloServiceImpl implements HelloService {</p>
-<pre><code>public String sayHello(String name) {
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(1));
- return "Hello, " + name;
-}
-</code></pre>
-<p>}</p>
-<h4>Service consumer project</h4>
-<p>package org.apache.skywalking.demo.consumer;</p>
-<p>@RestController
-public class ConsumerController {</p>
-<pre><code>private static int COUNT = 0;
-
-@Reference(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- url = "dubbo://localhost:20880", timeout = 60000)
-private HelloService helloService;
-
-@GetMapping("/sayHello/{name}")
-public String sayHello(@PathVariable(name = "name") String name) {
- if ((COUNT++) % 3 == 0){
- throw new RuntimeException();
- }
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(2));
- return helloService.sayHello(name);
-}
-</code></pre>
-<p>}</p>
-<h3>Deploy Apache Skywalking(incubator)</h3>
-<p><a href="https://github.com/apache/incubator-skywalking">Apache skywalking (Incubator)</a> offers two deployment modes: single-node mode and cluster mode,Here is the single-node mode deployment step, and more about how to deploy skywalking with cluster mode, please reference <a href="https://github.com/apache/incubator-skywalking/blob/master/docs/en/Deploy-backend-in-cluster-mode.md">document</a>.</p>
-<h4>Third-party components</h4>
-<ol>
-<li>JDK 8+</li>
-<li>Elasticsearch 5.x</li>
-</ol>
-<h4>Deployment step</h4>
-<ol>
-<li>Download <a href="http://skywalking.apache.org/downloads/">Apache Skywalking Collector</a></li>
-<li>Deploy Elasticsearch service
-<ul>
-<li>Set <code>cluster.name</code> to <code>CollectorDBCluster</code></li>
-<li>Set <code>network.host</code> to <code>0.0.0.0</code></li>
-<li>Start elasticsearch service</li>
-</ul>
-</li>
-<li>Unzip and start the Skywalking Collector. Run the ' bin/startup.sh ' command to start skywalking Collector</li>
-</ol>
-<h4>Deploy the demo</h4>
-<p>Before you deploy the demo service, please run the following command:</p>
-<pre><code>./mvnw clean package
-</code></pre>
-<h4>Deploy the provider service</h4>
-<pre><code>java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-provider -Dskywalking.collector.servers=localhost:10800 dubbo-provider/target/dubbo-provider.jar
-</code></pre>
-<h4>Deploy the consumer service</h4>
-<pre><code>java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-consumer -Dskywalking.collector.servers=localhost:10800 dubbo-consumer/target/dubbo-consumer.jar
-</code></pre>
-<h4>visit demo service</h4>
-<pre><code>curl http://localhost:8080/sayHello/test
-</code></pre>
-<h2>Skywalking scren snapshot</h2>
-<h3>Dashboard</h3>
-<p><img src="../sources/images/skywalking-dashboard.png" alt="/admin-guide/images/skywalking-dashboard.png"></p>
-<h3>Topology</h3>
-<p><img src="../sources/images/skywalking-topology.png" alt="/admin-guide/images/skywalking-topology.png"></p>
-<h3>Application view</h3>
-<p><img src="../sources/images/skywalking-application.png" alt="/admin-guide/images/skywalking-application.png"></p>
-<p>JVM Information
-<img src="../sources/images/skywalking-application_instance.png" alt="/admin-guide/images/skywalking-application_instance.png"></p>
-<h3>Service view</h3>
-<p>Consumer side
-<img src="../sources/images/skywalking-service-consumer.png" alt="/admin-guide/images/skywalking-service-consumer.png"></p>
-<p>provider side
-<img src="../sources/images/skywalking-service-provider.png" alt="/admin-guide/images/skywalking-service-provider.png"></p>
-<h3>Trace</h3>
-<p><img src="../sources/images/skywalking-trace.png" alt="/admin-guide/images/skywalking-trace.png"></p>
-<p>Span info
-<img src="../sources/images/skywalking-span-Info.png" alt="/admin-guide/images/skywalking-span-Info.png"></p>
-<h3>Alarm view</h3>
-<p><img src="../sources/images/skywalking-alarm.png" alt="/admin-guide/images/skywalking-alarm.png"></p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/skywalking.json b/en-us/docs/admin/ops/skywalking.json
deleted file mode 100644
index c5b4b56..0000000
--- a/en-us/docs/admin/ops/skywalking.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "skywalking.md",
- "__html": "<h1>Tracing Dubbo service with Apache Skywalking(incubator)</h1>\n<h2>Introduction to Apache Skywalking(Incubator)</h2>\n<p><a href=\"https://github.com/apache/incubator-skywalking\">Apache Skywalking(Incubator)</a> is the APM system that it designed for micro-services architectures and cloud native architecture systems and supports distribute tracking. <a href=\"https://github.com/apache/incubator-skywalking\">Apache skywalking (incubator)</a> collects and analyzes the tra [...]
- "link": "/en-us/docs/admin/ops/skywalking.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/ops/skywalking.md b/en-us/docs/admin/ops/skywalking.md
deleted file mode 100644
index 510c823..0000000
--- a/en-us/docs/admin/ops/skywalking.md
+++ /dev/null
@@ -1,121 +0,0 @@
-# Tracing Dubbo service with Apache Skywalking(incubator)
-## Introduction to Apache Skywalking(Incubator)
-[Apache Skywalking(Incubator)](https://github.com/apache/incubator-skywalking) is the APM system that it designed for micro-services architectures and cloud native architecture systems and supports distribute tracking. [Apache skywalking (incubator)](https://github.com/apache/incubator-skywalking) collects and analyzes the trace data and generates the relationship between the application and the service metric, Apache skywalking supports multiple languages agent, for example [Java](htt [...]
-
-Currently, Skywalking has supported analysis the operation of distributed systems from 6 visual dimensions. The overview view is a global view of your applications and components, including the number of components and applications, application alarm fluctuations, slow service lists, and application throughput; The topology shows the topological relationship of the whole application; The application view represents the upstream and downstream relationship of the application from single a [...]
-
-## Dubbo and Apache Skywalking(Incubator)
-### Build the Dubbo demo project
-The Dubbo demo has been uploaded to the [GitHub repository](https://github.com/SkywalkingTest/dubbo-trace-example).
-#### API project
-Service interface definition:
-package org.apache.skywalking.demo.interfaces;
-
-public interface HelloService {
- String sayHello(String name);
-}
-#### Service provider project
-package org.apache.skywalking.demo.provider;
-
-@Service(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- protocol = "${dubbo.protocol.id}",
- registry = "${dubbo.registry.id}", timeout = 60000)
-public class HelloServiceImpl implements HelloService {
-
- public String sayHello(String name) {
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(1));
- return "Hello, " + name;
- }
-
-}
-#### Service consumer project
-package org.apache.skywalking.demo.consumer;
-
-@RestController
-public class ConsumerController {
-
- private static int COUNT = 0;
-
- @Reference(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- url = "dubbo://localhost:20880", timeout = 60000)
- private HelloService helloService;
-
- @GetMapping("/sayHello/{name}")
- public String sayHello(@PathVariable(name = "name") String name) {
- if ((COUNT++) % 3 == 0){
- throw new RuntimeException();
- }
- LockSupport.parkNanos(TimeUnit.SECONDS.toNanos(2));
- return helloService.sayHello(name);
- }
-}
-### Deploy Apache Skywalking(incubator)
-[Apache skywalking (Incubator)](https://github.com/apache/incubator-skywalking) offers two deployment modes: single-node mode and cluster mode,Here is the single-node mode deployment step, and more about how to deploy skywalking with cluster mode, please reference [document](https://github.com/apache/incubator-skywalking/blob/master/docs/en/Deploy-backend-in-cluster-mode.md).
-#### Third-party components
-1. JDK 8+
-2. Elasticsearch 5.x
-#### Deployment step
-1. Download [Apache Skywalking Collector](http://skywalking.apache.org/downloads/)
-2. Deploy Elasticsearch service
- * Set `cluster.name` to `CollectorDBCluster`
- * Set `network.host` to `0.0.0.0`
- * Start elasticsearch service
-3. Unzip and start the Skywalking Collector. Run the ' bin/startup.sh ' command to start skywalking Collector
-
-#### Deploy the demo
-Before you deploy the demo service, please run the following command:
-
-```
-./mvnw clean package
-```
-
-#### Deploy the provider service
-
-```
-java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-provider -Dskywalking.collector.servers=localhost:10800 dubbo-provider/target/dubbo-provider.jar
-```
-
-#### Deploy the consumer service
-
-```
-java -jar -javaagent:$AGENT_PATH/skywalking-agent.jar -Dskywalking.agent.application_code=dubbo-consumer -Dskywalking.collector.servers=localhost:10800 dubbo-consumer/target/dubbo-consumer.jar
-```
-
-#### visit demo service
-
-```
-curl http://localhost:8080/sayHello/test
-```
-
-## Skywalking scren snapshot
-
-### Dashboard
-
-
-### Topology
-
-
-### Application view
-
-
-JVM Information
-
-
-### Service view
-
-Consumer side
-
-
-provider side
-
-
-### Trace
-
-
-Span info
-
-
-### Alarm view
-
diff --git a/en-us/docs/admin/serviceGovernance.html b/en-us/docs/admin/serviceGovernance.html
deleted file mode 100644
index 000ddb3..0000000
--- a/en-us/docs/admin/serviceGovernance.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="serviceGovernance" />
- <meta name="description" content="serviceGovernance" />
- <!-- 网页标签标题 -->
- <title>serviceGovernance</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>Service governance</h2>
-<p>服务治理主要作用是改变运行时服务的行为和选址逻辑，达到限流，权重配置等目的，主要有以下几个功能：<br>
-the basic function of service governance is changing the runtime behaviour and routing logic, to do weight configuration and current limiting:</p>
-<h3>应用级别的服务治理</h3>
-<h3>application level service governance</h3>
-<p>在Dubbo2.6及更早版本中，所有的服务治理规则都只针对服务粒度，如果要把某条规则作用到应用粒度上，需要为应用下的所有服务配合相同的规则，变更，删除的时候也需要对应的操作，这样的操作很不友好，因此Dubbo2.7版本中增加了应用粒度的服务治理操作，对于条件路由(包括黑白名单)，动态配置(包括权重，负载均衡)都可以做应用级别的配置：<br>
-In Dubbo 2.6 or earlier version, all service governance rule are in service scope, if you need to make application scope rule, you need to set the same rule for all services under an application, modify and delete need the same operation, this is very unfriendly. In Dubbo 2.7, application scope service governance is supported, condition route(including black white list) and dynamic configuration(including weight, load balance) all support application scope config.
-<img src="../../../img/blog/admin/conditionRoute.jpg" alt="condition"><br>
-picture above is condition route configuration, can create and search by both application name and service name.</p>
-<h3>tag route</h3>
-<p>标签路由是Dubbo2.7引入的新功能，配置以应用作为维度，给不同的服务器打上不同名字的标签，配置如下图所示：
-tag route is a new feature in Dubbo2.7, in application scope, to set different tag on different server, the screenshot is shown as below:
-<img src="../../../img/blog/admin/route.jpg" alt="tag">
-the client can use <code>setAttachment</code> to specify different tag, is the above case, <code>setAttachment(tag1)</code>, the client will choose from the three servers in the picture above. In this way, you can implement features such as traffic isolation and gray release.</p>
-<h3>condition route</h3>
-<p>condition route is a traditional function in Dubbo, now you can create it in either service scope or application scope. Condition route is in <code>yaml</code> format, you can read <a href="../user/demo/routing-rule.md">here</a> to find more.</p>
-<h3>black white list</h3>
-<p>black white list is a part of condition route and store with condition route together, you can set black list or white list, in either service scope or application scope:
-<img src="sources/images/blackList.jpg" alt="blackList"></p>
-<h3>dynamic configuration</h3>
-<p>dynamic configuration has the same level with routing rule, it can change the RPC behaviour dynamically without restart service. It supports application scope since Dubbo 2,7, in Dubbo format, the screen shot shows in below:
-<img src="sources/images/config.jpg" alt="config">
-to read more, please refer <a href="../user/demos/config-rule.md">here</a></p>
-<h3>weight adjust</h3>
-<p>weigth adjuest is part of dynamic configuration, change the weight of server side to do traffic control dynamically:
-<img src="sources/images/weight.jpg" alt="weight"></p>
-<h3>load balancing</h3>
-<p>load balancing is also poart of dynamic configuration, to specify the route strategy in client side. now we have three strategies: random, least active and round robin, to read more, please refer <a href="../user/demos/loadbalance.md">here</a></p>
-<h2>configuration management</h2>
-<p>configuration management is also a new feaature for Dubbo 2.7. In Dubbo 2.7, we can specify configurations in global scope and application scope(including services in application), you can view, modify and create new configurations in Dubbo Admin.</p>
-<ul>
-<li>global configuration:
-<img src="../../../img/blog/admin/config.jpg" alt="config"><br>
-you can set registry center, metadata center, timeout for provider and consumer in global configurations. If the implementation of registry center and metadata center is zookeeper, you can also check the location of configuration file.</li>
-<li>application and service scope configuration:
-<img src="../../../img/blog/admin/appConfig.jpg" alt="appConfig"><br>
-application configuration can also set service configuration in this application. you need to specify consumer and provider in service scope: <code>dubbo.reference.{serviceName}</code>stands for configuration as consumer side，<code>dubbo.provider.{servcieName}</code>stands for configuration as provider side. the address of registry address and metadata center address can only be configured in global configuration, which is also the recommendation way in Dubbo 2.7</li>
-<li>priority service configuration > application configuration > global configuration</li>
-</ul>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/serviceGovernance.json b/en-us/docs/admin/serviceGovernance.json
deleted file mode 100644
index 2e91d31..0000000
--- a/en-us/docs/admin/serviceGovernance.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "serviceGovernance.md",
- "__html": "<h1>Service governance and configuration management</h1>\n<h2>Service governance</h2>\n<p>服务治理主要作用是改变运行时服务的行为和选址逻辑，达到限流，权重配置等目的，主要有以下几个功能：<br>\nthe basic function of service governance is changing the runtime behaviour and routing logic, to do weight configuration and current limiting:</p>\n<h3>应用级别的服务治理</h3>\n<h3>application level service governance</h3>\n<p>在Dubbo2.6及更早版本中，所有的服务治理规则都只针对服务粒度，如果要把某条规则作用到应用粒度上，需要为应用下的所有服务配合相同的规则，变更，删除的时候也需要对应的操作，这样的操作很不友好，因此Dubbo2.7版本中增加了应用粒度 [...]
- "link": "/en-us/docs/admin/serviceGovernance.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/serviceSearch.html b/en-us/docs/admin/serviceSearch.html
deleted file mode 100644
index 8b102e1..0000000
--- a/en-us/docs/admin/serviceSearch.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="serviceSearch" />
- <meta name="description" content="serviceSearch" />
- <!-- 网页标签标题 -->
- <title>serviceSearch</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>Service search is the basic function of Dubbo OPS, you can search by service name, application name and IP address, the service name and application name support wildcard and autocomplete:
-<img src="sources/images/searchResult.png" alt="searchResult">
-the service detail page display providers, consumers, medata information is supported in Dubbo 2.7 or higher version:
-<img src="sources/images/detail.jpg" alt="detail"></p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/serviceSearch.json b/en-us/docs/admin/serviceSearch.json
deleted file mode 100644
index 9ff0592..0000000
--- a/en-us/docs/admin/serviceSearch.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "serviceSearch.md",
- "__html": "<h1>Service search and service detail</h1>\n<p>Service search is the basic function of Dubbo OPS, you can search by service name, application name and IP address, the service name and application name support wildcard and autocomplete:\n<img src=\"sources/images/searchResult.png\" alt=\"searchResult\">\nthe service detail page display providers, consumers, medata information is supported in Dubbo 2.7 or higher version:\n<img src=\"sources/images/detail.jpg\" alt=\"detail\"></p>\n",
- "link": "/en-us/docs/admin/serviceSearch.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/admin/serviceTest.html b/en-us/docs/admin/serviceTest.html
deleted file mode 100644
index 5d8d1bb..0000000
--- a/en-us/docs/admin/serviceTest.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="serviceTest" />
- <meta name="description" content="serviceTest" />
- <!-- 网页标签标题 -->
- <title>serviceTest</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/admin/serviceTest.json b/en-us/docs/admin/serviceTest.json
deleted file mode 100644
index 44e89a9..0000000
--- a/en-us/docs/admin/serviceTest.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "serviceTest.md",
- "__html": "<p>please refer to this <a href=\"../../../zh-cn/blog/service-test.md\">blog</a></p>\n",
- "link": "/en-us/docs/admin/serviceTest.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/README.html b/en-us/docs/dev/README.html
deleted file mode 100644
index a1a2fb3..0000000
--- a/en-us/docs/dev/README.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="README" />
- <meta name="description" content="README" />
- <!-- 网页标签标题 -->
- <title>README</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>This book dives into the design principles of dubbo, mainly covers the following topics: extension, coding styles, versio, build, etc.</p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/README.json b/en-us/docs/dev/README.json
deleted file mode 100644
index 2dfd479..0000000
--- a/en-us/docs/dev/README.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "README.md",
- "__html": "<h1>dubbo-dev-book</h1>\n<p>This book dives into the design principles of dubbo, mainly covers the following topics: extension, coding styles, versio, build, etc.</p>\n",
- "link": "/en-us/docs/dev/README.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/SPI.html b/en-us/docs/dev/SPI.html
deleted file mode 100644
index e6cb5e7..0000000
--- a/en-us/docs/dev/SPI.html
+++ /dev/null
@@ -1,203 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="SPI" />
- <meta name="description" content="SPI" />
- <!-- 网页标签标题 -->
- <title>SPI</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>SPI Config</h2>
-<h3>Source:</h3>
-<p>Dubbo SPI is inherited from standard JDK SPI(Service Provider Interface) and makes it more powerful.</p>
-<p>Dubbo fixed below issues of the standard JDK SPI:</p>
-<ul>
-<li>The standard JDK SPI will load and instantize all the implementations at once. It will be a waste of resources if one implementation is timecosted, but never be used.</li>
-<li>We can't accquire the SPI name, if loading the SPI implementation is failed.For example: standard JDK ScriptEngine, get script type by invoking method getName(). RubyScriptEngine class will load failed if the depenency jar jruby.jar is missing, and the real error info will be lost. When user executes ruby scripts, the program throws exception that doesn't support ruby, but it is not the real cause.</li>
-<li>Enhance the SPI functionality by supporting IoC and AOP, one SPI can be easily injected by another SPI simply using setter.</li>
-</ul>
-<h3>Appointment:</h3>
-<p>In the jar file containing extension class <sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup>, places a config file <code>META-INF/dubbo/full interface name</code>, file content pattern: <code>SPI name=the fully qualified name for the extension class</code>, use new line seperator for multiple implementation.</p>
-<h3>Example:</h3>
-<p>To extend Dubbo Protocol, placee a text file in the extension jar file: <code>META-INF/dubbo/org.apache.dubbo.rpc.Protocol</code>, content:</p>
-<pre><code class="language-properties"><span class="hljs-attr">xxx</span>=<span class="hljs-string">com.alibaba.xxx.XxxProtocol</span>
-</code></pre>
-<p>content of the implementation <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup>:</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.alibaba.xxx;
-
-<span class="hljs-keyword">import</span> org.apache.dubbo.rpc.Protocol;
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">XxxProtocol</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Protocol</span> </span>{
- <span class="hljs-comment">// ...</span>
-}
-</code></pre>
-<h3>Configuration in config module</h3>
-<p>In Dubbo config module, all SPI points have related attributes or labels, we can choose the specific SPI implementation by using its name. Like:</p>
-<pre><code class="language-xml"><span class="hljs-tag"><<span class="hljs-name">dubbo:protocol</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"xxx"</span> /></span>
-</code></pre>
-<h2>SPI Features</h2>
-<h3>SPI Auto Wrap</h3>
-<p>Auto wrap the SPI's Wrapper class. <code>ExtensionLoader</code> loads the SPI implementation, if the SPI has a copy instructor, it will be regarded as the SPI's Wrapper class.</p>
-<p>Wrapper class content:</p>
-<pre><code class="language-java"><span class="hljs-keyword">package</span> com.alibaba.xxx;
-
-<span class="hljs-keyword">import</span> org.apache.dubbo.rpc.Protocol;
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">XxxProtocolWrapper</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Protocol</span> </span>{
- Protocol impl;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">XxxProtocolWrapper</span><span class="hljs-params">(Protocol protocol)</span> </span>{ impl = protocol; }
-
- <span class="hljs-comment">//after interface method is executed, the method in extension will be executed</span>
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">refer</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-comment">//... some operation</span>
- impl.refer();
- <span class="hljs-comment">// ... some operation</span>
- }
-
- <span class="hljs-comment">// ...</span>
-}
-</code></pre>
-<p>Wrapper class also implements the same SPI interface, but Wrapper is not the real implementation. It is used for wrap the real implementation returned from the <code>ExtensionLoader</code>. The real returned instance by <code>ExtensionLoader</code> is the Wrapper class instance, Wrapper holder the real SPI implementation class.</p>
-<p>There can be many Wrapper for one spi, simply add one if you need.</p>
-<p>With Wrapper class, you will be able to move same logics into Wrapper for all SPIs. Newly added Wrapper class add external logics for all SPIs, looks like AOP, Wrapper acts as a proxy for SPI.</p>
-<h3>SPI Auto Load</h3>
-<p>when loading the SPI, Dubbo will auto load the depency SPI. When one SPI implementation contains attribute which is also an SPI of another type,<code>ExtensionLoader</code> will automatically load the depency SPI. <code>ExtensionLoader</code> knows all the members of the specific SPI by scanning the setter method of all implementation class.</p>
-<p>Demo: two SPI <code>CarMaker</code>（car maker）、<code>WheelMaker</code> (wheel maker)</p>
-<p>Intefaces look like:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">CarMaker</span> </span>{
- <span class="hljs-function">Car <span class="hljs-title">makeCar</span><span class="hljs-params">()</span></span>;
-}
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">WheelMaker</span> </span>{
- <span class="hljs-function">Wheel <span class="hljs-title">makeWheel</span><span class="hljs-params">()</span></span>;
-}
-</code></pre>
-<p><code>CarMaker</code>'s implementation:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">RaceCarMaker</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">CarMaker</span> </span>{
- WheelMaker wheelMaker;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">setWheelMaker</span><span class="hljs-params">(WheelMaker wheelMaker)</span> </span>{
- <span class="hljs-keyword">this</span>.wheelMaker = wheelMaker;
- }
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> Car <span class="hljs-title">makeCar</span><span class="hljs-params">()</span> </span>{
- <span class="hljs-comment">// ...</span>
- Wheel wheel = wheelMaker.makeWheel();
- <span class="hljs-comment">// ...</span>
- <span class="hljs-keyword">return</span> <span class="hljs-keyword">new</span> RaceCar(wheel, ...);
- }
-}
-</code></pre>
-<p>when <code>ExtensionLoader</code> loads <code>CarMaker</code>'s implementation <code>RaceCarMaker</code>, the method <code>setWheelMaker</code> needs paramType <code>WheelMaker</code> which is also a SPI, It will be automatically loaded.</p>
-<p>This brings a new question:How <code>ExtensionLoader</code> determines which implementation to use when load the injected SPI. As for this demo, when existing multi <code>WheelMaker</code> implementation, which one should the <code>ExtensionLoader</code> chooses.</p>
-<p>Good question, we will explain it in the following chapter: SPI Auto Adaptive.</p>
-<h3>SPI Auto Adaptive</h3>
-<p>The depency SPI that <code>ExtensionLoader</code> injects is an instance of <code>Adaptive</code>, the real spi implementation is known until the adaptive instance is executed.</p>
-<p>Dubbo use URL (containing Key-Value) to pass the configuration.</p>
-<p>The SPI method invocation has the URL parameter（Or Entity that has URL attribute）</p>
-<p>In this way depended SPI can get configuration from URL, after config all SPI key needed, configuration information will be passed from outer by URL. URL acts as a bus when passing the config information.</p>
-<p>Demo: two SPI <code>CarMaker</code>、<code>WheelMaker</code></p>
-<p>interface looks like:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">CarMaker</span> </span>{
- <span class="hljs-function">Car <span class="hljs-title">makeCar</span><span class="hljs-params">(URL url)</span></span>;
-}
-
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">WheelMaker</span> </span>{
- <span class="hljs-function">Wheel <span class="hljs-title">makeWheel</span><span class="hljs-params">(URL url)</span></span>;
-}
-</code></pre>
-<p><code>CarMaker</code>'s implementation:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">RaceCarMaker</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">CarMaker</span> </span>{
- WheelMaker wheelMaker;
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">setWheelMaker</span><span class="hljs-params">(WheelMaker wheelMaker)</span> </span>{
- <span class="hljs-keyword">this</span>.wheelMaker = wheelMaker;
- }
-
- <span class="hljs-function"><span class="hljs-keyword">public</span> Car <span class="hljs-title">makeCar</span><span class="hljs-params">(URL url)</span> </span>{
- <span class="hljs-comment">// ...</span>
- Wheel wheel = wheelMaker.makeWheel(url);
- <span class="hljs-comment">// ...</span>
- <span class="hljs-keyword">return</span> <span class="hljs-keyword">new</span> RaceCar(wheel, ...);
- }
-}
-</code></pre>
-<p>when execute the code above</p>
-<pre><code class="language-java"><span class="hljs-comment">// ...</span>
-Wheel wheel = wheelMaker.makeWheel(url);
-<span class="hljs-comment">// ...</span>
-</code></pre>
-<p>, the injected <code>Adaptive</code> object determine which <code>WheelMaker</code>'s <code>makeWheel</code> method will be executed by predefined Key. Such as <code>wheel.type</code>, key <code>url.get("wheel.type")</code> will determine <code>WheelMake</code> implementation. The logic of<code>Adaptive</code> instance of fixed, getting the predefined Key of the URL, dynamically creating the real implementation and execute it.</p>
-<p>For Dubbo, the SPI <code>Adaptive</code> implementation in <code>ExtensionLoader</code> is dynamically created when dubbo is loading the SPI. Get the Key from URL, the Key will be provided through <code>@Adaptive</code> annotation for the interface method definition.</p>
-<p>Below is Dubbo Transporter SPI codes:</p>
-<pre><code class="language-java"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">interface</span> <span class="hljs-title">Transporter</span> </span>{
- <span class="hljs-meta">@Adaptive</span>({<span class="hljs-string">"server"</span>, <span class="hljs-string">"transport"</span>})
- <span class="hljs-function">Server <span class="hljs-title">bind</span><span class="hljs-params">(URL url, ChannelHandler handler)</span> <span class="hljs-keyword">throws</span> RemotingException</span>;
-
- <span class="hljs-meta">@Adaptive</span>({<span class="hljs-string">"client"</span>, <span class="hljs-string">"transport"</span>})
- <span class="hljs-function">Client <span class="hljs-title">connect</span><span class="hljs-params">(URL url, ChannelHandler handler)</span> <span class="hljs-keyword">throws</span> RemotingException</span>;
-}
-</code></pre>
-<p>for the method bind(), Adaptive will firstly search <code>server</code> key, if no Key were founded then will search <code>transport</code> key, to determine the implementation that the proxy represent for.</p>
-<h3>SPI Auto Activation</h3>
-<p>As for Collections SPI, such as: <code>Filter</code>, <code>InvokerListener</code>, <code>ExportListener</code>, <code>TelnetHandler</code>, <code>StatusChecker</code> etc, multi implementations can be loaded at one time. User can simplify configuration by using auto activation, Like:</p>
-<pre><code class="language-java"><span class="hljs-keyword">import</span> org.apache.dubbo.common.extension.Activate;
-<span class="hljs-keyword">import</span> org.apache.dubbo.rpc.Filter;
-
-<span class="hljs-meta">@Activate</span> <span class="hljs-comment">// Active for any condition</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">XxxFilter</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Filter</span> </span>{
- <span class="hljs-comment">// ...</span>
-}
-</code></pre>
-<p>Or:</p>
-<pre><code class="language-java"><span class="hljs-keyword">import</span> org.apache.dubbo.common.extension.Activate;
-<span class="hljs-keyword">import</span> org.apache.dubbo.rpc.Filter;
-
-<span class="hljs-meta">@Activate</span>(<span class="hljs-string">"xxx"</span>) <span class="hljs-comment">// when configed xxx parameter and the parameter has a valid value,the SPI is activated, for example configed cache="lru", auto acitivate CacheFilter.</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">XxxFilter</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Filter</span> </span>{
- <span class="hljs-comment">// ...</span>
-}
-</code></pre>
-<p>Or:</p>
-<pre><code class="language-java"><span class="hljs-keyword">import</span> org.apache.dubbo.common.extension.Activate;
-<span class="hljs-keyword">import</span> org.apache.dubbo.rpc.Filter;
-
-<span class="hljs-meta">@Activate</span>(group = <span class="hljs-string">"provider"</span>, value = <span class="hljs-string">"xxx"</span>) <span class="hljs-comment">// only activate for provider, group can be "provider" or "consumer"</span>
-<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">XxxFilter</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Filter</span> </span>{
- <span class="hljs-comment">// ...</span>
-}
-</code></pre>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1" class="footnote-item"><p>Note: The config file here is in you own jar file, not in dubbo release jar file, Dubbo will scan all jar files with the same filename in classpath and then merge them together <a href="#fnref1" class="footnote-backref">↩︎</a></p>
-</li>
-<li id="fn2" class="footnote-item"><p>Note: SPI will be loaded in singleton pattern(Please ensure thread safety), cached in <code>ExtensionLoader</code> <a href="#fnref2" class="footnote-backref">↩︎</a></p>
-</li>
-</ol>
-</section>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/SPI.json b/en-us/docs/dev/SPI.json
deleted file mode 100644
index 52602db..0000000
--- a/en-us/docs/dev/SPI.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "SPI.md",
- "__html": "<h1>SPI Loading</h1>\n<h2>SPI Config</h2>\n<h3>Source:</h3>\n<p>Dubbo SPI is inherited from standard JDK SPI(Service Provider Interface) and makes it more powerful.</p>\n<p>Dubbo fixed below issues of the standard JDK SPI:</p>\n<ul>\n<li>The standard JDK SPI will load and instantize all the implementations at once. It will be a waste of resources if one implementation is timecosted, but never be used.</li>\n<li>We can't accquire the SPI name, if loading the SPI implementatio [...]
- "link": "/en-us/docs/dev/SPI.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/SUMMARY.html b/en-us/docs/dev/SUMMARY.html
deleted file mode 100644
index 8f0950b..0000000
--- a/en-us/docs/dev/SUMMARY.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="SUMMARY" />
- <meta name="description" content="SUMMARY" />
- <!-- 网页标签标题 -->
- <title>SUMMARY</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<ul>
-<li><a href="./build.md">1 How To Build</a></li>
-<li><a href="./design.md">2 Architecture</a></li>
-<li><a href="./SPI.md">3 How SPI Works</a></li>
-<li><a href="./implementation.md">4 Init, Process, Protocols</a></li>
-<li><a href="./impls/introduction.md">5 SPI Extensions</a>
-<ul>
-<li><a href="./impls/protocol.md">5.1 Protocol</a></li>
-<li><a href="./impls/filter.md">5.2 Filter</a></li>
-<li><a href="./impls/invoker-listener.md">5.3 InvokerListener</a></li>
-<li><a href="./impls/exporter-listener.md">5.4 ExporterListener</a></li>
-<li><a href="./impls/cluster.md">5.5 Cluster</a></li>
-<li><a href="./impls/router.md">5.6 Router</a></li>
-<li><a href="./impls/load-balance.md">5.7 LoadBalance</a></li>
-<li><a href="./impls/merger.md">5.8 Merger</a></li>
-<li><a href="./impls/registry.md">5.9 Registry</a></li>
-<li><a href="./impls/monitor.md">5.10 Monitor</a></li>
-<li><a href="./impls/extension-factory.md">5.11 ExtensionFactory</a></li>
-<li><a href="./impls/proxy-factory.md">5.12 ProxyFactory</a></li>
-<li><a href="./impls/compiler.md">5.13 Compiler</a></li>
-<li><a href="./impls/dispatcher.md">5.14 Dispatcher</a></li>
-<li><a href="./impls/threadpool.md">5.15 Threadpool</a></li>
-<li><a href="./impls/serialize.md">5.16 Serialization</a></li>
-<li><a href="./impls/remoting.md">5.17 Remoting</a></li>
-<li><a href="./impls/exchanger.md">5.18 Exchanger</a></li>
-<li><a href="./impls/networker.md">5.19 Networker</a></li>
-<li><a href="./impls/telnet-handler.md">5.20 TelnetHandler</a></li>
-<li><a href="./impls/status-checker.md">5.21 StatusChecker</a></li>
-<li><a href="./impls/container.md">5.22 Container</a></li>
-<li><a href="./impls/page.md">5.23 PageHandler</a></li>
-<li><a href="./impls/cache.md">5.24 Cache</a></li>
-<li><a href="./impls/validation.md">5.25 Validation</a></li>
-<li><a href="./impls/logger-adapter.md">5.26 LoggerAdapter</a></li>
-</ul>
-</li>
-<li><a href="./contract.md">6 Contract</a></li>
-<li><a href="./coding.md">7 Code Style</a></li>
-<li><a href="./release.md">9 Versions</a></li>
-<li><a href="./contribution.md">10 Contribution</a></li>
-<li><a href="./checklist.md">11 Checklist</a></li>
-<li><a href="./code-smell.md">12 Code Smell</a></li>
-<li><a href="./TCK.md">13 TCK</a></li>
-</ul>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/SUMMARY.json b/en-us/docs/dev/SUMMARY.json
deleted file mode 100644
index 9978b5d..0000000
--- a/en-us/docs/dev/SUMMARY.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "SUMMARY.md",
- "__html": "<h1>Summary</h1>\n<ul>\n<li><a href=\"./build.md\">1 How To Build</a></li>\n<li><a href=\"./design.md\">2 Architecture</a></li>\n<li><a href=\"./SPI.md\">3 How SPI Works</a></li>\n<li><a href=\"./implementation.md\">4 Init, Process, Protocols</a></li>\n<li><a href=\"./impls/introduction.md\">5 SPI Extensions</a>\n<ul>\n<li><a href=\"./impls/protocol.md\">5.1 Protocol</a></li>\n<li><a href=\"./impls/filter.md\">5.2 Filter</a></li>\n<li><a href=\"./impls/invoker-listener.md\"> [...]
- "link": "/en-us/docs/dev/SUMMARY.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/TCK.html b/en-us/docs/dev/TCK.html
deleted file mode 100644
index 949e31a..0000000
--- a/en-us/docs/dev/TCK.html
+++ /dev/null
@@ -1,46 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="TCK" />
- <meta name="description" content="TCK" />
- <!-- 网页标签标题 -->
- <title>TCK</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>Dubbo's protocol, communication, serialization, registry, load balancing and other SPI all offer alternative strategies for different application scenarios while our test cases are very scattered. Ours is always uncertain whether it can satisfy the complete contract of the extension point when users need to add a new implementation.</p>
-<p>Thus we need to use TCK (Technology Compatibility Kit) for the core extension points. When users add a new implementaion, compatibility with the rest of the framework can be ensured with TCK. This can effectively improve the overall health and also facilitate the access of the third party extenders, which accelerates the maturity of the open source community.</p>
-<p>Xingzhi from the open source community is already working on this part. His preliminary idea is to build a TCK framework for Dubbo drawing on the CDI-TCK of JBoss first, then realize the TCK implementing case of Dubbo.</p>
-<p>Reference：<a href="http://docs.jboss.org/cdi/tck/reference/1.0.1-Final/html/introduction.html">http://docs.jboss.org/cdi/tck/reference/1.0.1-Final/html/introduction.html</a></p>
-<p>Anyone interested is welcomed to work on this together.</p>
-<h4>Protocol TCK</h4>
-<blockquote>
-<p>TODO</p>
-</blockquote>
-<h4>Registry TCK</h4>
-<blockquote>
-<p>TODO</p>
-</blockquote>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/TCK.json b/en-us/docs/dev/TCK.json
deleted file mode 100644
index c2e0699..0000000
--- a/en-us/docs/dev/TCK.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "TCK.md",
- "__html": "<h1>Compatibility test</h1>\n<p>Dubbo's protocol, communication, serialization, registry, load balancing and other SPI all offer alternative strategies for different application scenarios while our test cases are very scattered. Ours is always uncertain whether it can satisfy the complete contract of the extension point when users need to add a new implementation.</p>\n<p>Thus we need to use TCK (Technology Compatibility Kit) for the core extension points. When users add a [...]
- "link": "/en-us/docs/dev/TCK.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/build.html b/en-us/docs/dev/build.html
deleted file mode 100644
index f55bb78..0000000
--- a/en-us/docs/dev/build.html
+++ /dev/null
@@ -1,74 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="build" />
- <meta name="description" content="build" />
- <!-- 网页标签标题 -->
- <title>build</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>Checkout</h2>
-<p>checkout the lastest project source code with commands blow:</p>
-<pre><code class="language-sh">git <span class="hljs-built_in">clone</span> https://github.com/apache/dubbo.git dubbo
-</code></pre>
-<h2>Branches</h2>
-<p>We use <code>master</code> as the major branch for new feature development, and use other branches for maintenance. Tags for all versions can be checked via <a href="https://github.com/apache/dubbo/tags">https://github.com/apache/dubbo/tags</a>.</p>
-<h2>Building</h2>
-<p>Dubbo relies on <a href="http://maven.apache.org">maven</a> as the building tool.</p>
-<p>Requirements:</p>
-<ul>
-<li>Java above 1.5 version</li>
-<li>Maven version 2.2.1 or above</li>
-</ul>
-<p>The following <code>MAVEN_OPTS</code>should be configured before building:</p>
-<pre><code class="language-sh"><span class="hljs-built_in">export</span> MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
-</code></pre>
-<p>build with below command:</p>
-<pre><code class="language-sh">mvn clean install
-</code></pre>
-<p>skip testing using below building command:</p>
-<pre><code class="language-sh">mvn install -Dmaven.test.skip
-</code></pre>
-<h2>Building jar package of source code</h2>
-<p>build Dubbo source code jar package with below command, which can debug Dubbo source code.</p>
-<pre><code class="language-sh">mvn clean <span class="hljs-built_in">source</span>:jar install -Dmaven.test.skip
-</code></pre>
-<h2>IDE support</h2>
-<p>use below command to generate IDE.</p>
-<h3>Intellij Idea</h3>
-<pre><code class="language-sh">mvn idea:idea
-</code></pre>
-<h3>Eclipse</h3>
-<pre><code class="language-sh">mvn eclipse:eclipse
-</code></pre>
-<p>Importing into eclipse</p>
-<p>Firstly, a maven repository needs to be configured in eclipse. Define <code>M2_REPO</code> and point it to the local maven repository by clicking <code>Preferences -> Java -> Build Path -> Classpath</code>.</p>
-<p>Use the following maven command as well:</p>
-<pre><code class="language-sh">mvn eclipse:configure-workspace -Declipse.workspace=/path/to/the/workspace/
-</code></pre>
-<p>1: view the source code through <a href="https://github.com/apache/dubbo">https://github.com/apache/dubbo</a>
-2: path under UNIX is ${HOME}/.m2/repository, path under Windows is C:\Documents and Settings<user>.m2\repository</p>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/build.json b/en-us/docs/dev/build.json
deleted file mode 100644
index 7acbfc8..0000000
--- a/en-us/docs/dev/build.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "build.md",
- "__html": "<h1>Source Code Build</h1>\n<h2>Checkout</h2>\n<p>checkout the lastest project source code with commands blow:</p>\n<pre><code class=\"language-sh\">git <span class=\"hljs-built_in\">clone</span> https://github.com/apache/dubbo.git dubbo\n</code></pre>\n<h2>Branches</h2>\n<p>We use <code>master</code> as the major branch for new feature development, and use other branches for maintenance. Tags for all versions can be checked via <a href=\"https://github.com/apache/dubbo/tags [...]
- "link": "/en-us/docs/dev/build.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/checklist.html b/en-us/docs/dev/checklist.html
deleted file mode 100644
index 29bac72..0000000
--- a/en-us/docs/dev/checklist.html
+++ /dev/null
@@ -1,51 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="checklist" />
- <meta name="description" content="checklist" />
- <!-- 网页标签标题 -->
- <title>checklist</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<h2>Checklist before release</h2>
-<ul>
-<li>github milestones</li>
-<li>github change lists</li>
-<li>Travis CI</li>
-<li>test code</li>
-<li>find bugs</li>
-</ul>
-<h2>Checklist for bigfix versions</h2>
-<ul>
-<li>Create a <em>github issue</em> before coding</li>
-<li>Create <em>unit test</em> before bugfix</li>
-<li>Review</li>
-<li>Test your code (Normal process / Abnormal process)</li>
-<li>Record your design on <em>github issue</em></li>
-<li>Complete javadoc and comment in code</li>
-<li>Manager for every version, responsible for scope and check</li>
-</ul>
-</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/dubbo_gray.png"/><img class="apache" src="/img/apache_logo.png"/><div class="cols-container"><div class="col col-12"><h3></h3><p></p></div><div class="col col-4"><dl><dt>ASF</dt><dd><a href="http://www.apache.org" target="_self">Foundation</a></dd><dd><a href="http://www.apache.org/licenses/" target="_self">License</a></dd><dd><a href="http://www.apache.org/events/current-event" target="_self">Events [...]
- <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
- <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
- <script>
- window.rootPath = '';
- </script>
- <script src="/build/documentation.js"></script>
- <!-- Global site tag (gtag.js) - Google Analytics -->
- <script async src="https://www.googletagmanager.com/gtag/js?id=UA-112489517-1"></script>
- <script>
- window.dataLayer = window.dataLayer || [];
- function gtag(){dataLayer.push(arguments);}
- gtag('js', new Date());
-
- gtag('config', 'UA-112489517-1');
- </script>
-</body>
-</html>
\ No newline at end of file
diff --git a/en-us/docs/dev/checklist.json b/en-us/docs/dev/checklist.json
deleted file mode 100644
index d7b93c9..0000000
--- a/en-us/docs/dev/checklist.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "filename": "checklist.md",
- "__html": "<h1>Checklist</h1>\n<h2>Checklist before release</h2>\n<ul>\n<li>github milestones</li>\n<li>github change lists</li>\n<li>Travis CI</li>\n<li>test code</li>\n<li>find bugs</li>\n</ul>\n<h2>Checklist for bigfix versions</h2>\n<ul>\n<li>Create a <em>github issue</em> before coding</li>\n<li>Create <em>unit test</em> before bugfix</li>\n<li>Review</li>\n<li>Test your code (Normal process / Abnormal process)</li>\n<li>Record your design on <em>github issue</em></li>\n<li>Comple [...]
- "link": "/en-us/docs/dev/checklist.html",
- "meta": {}
-}
\ No newline at end of file
diff --git a/en-us/docs/dev/code-smell.html b/en-us/docs/dev/code-smell.html
deleted file mode 100644
index 5ad36bd..0000000
--- a/en-us/docs/dev/code-smell.html
+++ /dev/null
@@ -1,160 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
- <meta charset="UTF-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="code-smell" />
- <meta name="description" content="code-smell" />
- <!-- 网页标签标题 -->
- <title>code-smell</title>
- <link rel="shortcut icon" href="/img/dubbo.ico"/>
- <link rel="stylesheet" href="/build/documentation.css" />
-</head>
-<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">中</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...]
-<p>Ugly Dubbo design or implementation will be record here.</p>
-<h2>URL Convertion</h2>
-<h3>1. Point to Point Service export and refer</h3>
-<p>service directly export：</p>
-<pre><code>EXPORT(dubbo://provider-address/com.xxx.XxxService?version=1.0.0")
-</code></pre>
-<p>service directly refer：</p>
-<pre><code>REFER(dubbo://provider-address/com.xxx.XxxService?version=1.0.0)
-</code></pre>
-<h3>2. Export servie by registry</h3>
-<p>export service to registry：</p>
-<pre><code>EXPORT(registry://registry-address/org.apache.dubbo.registry.RegistrySerevice?registry=dubbo&export=ENCODE(dubbo://provider-address/com.xxx.XxxService?version=1.0.0))
-</code></pre>
-<p>accquire registry：</p>
-<pre><code>url.setProtocol(url.getParameter("registry", "dubbo"))
-GETREGISTRY(dubbo://registry-address/org.apache.dubbo.registry.RegistrySerevice)
-</code></pre>
-<p>registry service address：</p>
-<pre><code>url.getParameterAndDecoded("export"))
-REGISTER(dubbo://provider-address/com.xxx.XxxService?version=1.0.0)
-</code></pre>
-<h3>3. Refer service from registry</h3>
-<p>refer service from registry：</p>
-<pre><code>REFER(registry://registry-address/org.apache.dubbo.registry.RegistrySerevice?registry=dubbo&refer=ENCODE(version=1.0.0))
-</code></pre>
-<p>accquire registry：</p>
-<pre><code>url.setProtocol(url.getParameter("registry", "dubbo"))
-GETREGISTRY(dubbo://registry-address/org.apache.dubbo.registry.RegistrySerevice)
-</code></pre>
-<p>subscribe service address：</p>
-<pre><code>url.addParameters(url.getParameterAndDecoded("refer"))
-SUBSCRIBE(dubbo://registry-address/com.xxx.XxxService?version=1.0.0)
-</code></pre>
-<p>notify service address：</p>
-<pre><code>url.addParameters(url.getParameterAndDecoded("refer"))
-NOTIFY(dubbo://provider-address/com.xxx.XxxService?version=1.0.0)
-</code></pre>
-<h3>4. Registry push route rule</h3>
-<p>registry push route rule：</p>
-<pre><code>NOTIFY(route://registry-address/com.xxx.XxxService?router=script&type=js&rule=ENCODE(function{...}))
-</code></pre>
-<p>accquire routers：</p>
-<pre><code>url.setProtocol(url.getParameter("router", "script"))
-GETROUTE(script://registry-address/com.xxx.XxxService?type=js&rule=ENCODE(function{...}))
-</code></pre>
-<h3>5. Load route rule from file</h3>
-<p>load route rule from file：</p>
-<pre><code>GETROUTE(file://path/file.js?router=script)
-</code></pre>
-<p>accquire routers：</p>
-<pre><code>url.setProtocol(url.getParameter("router", "script")).addParameter("type", SUFFIX(file)).addParameter("rule", READ(file))
-GETROUTE(script://path/file.js?type=js&rule=ENCODE(function{...}))
-</code></pre>
-<h2>Invoke parameters</h2>
-<ul>
-<li>path service path</li>
-<li>group service group</li>
-<li>version service version</li>
-<li>dubbo current dubbo release version</li>
-<li>token verify token</li>
-<li>timeout invocation timeout</li>
-</ul>
-<h2>SPI Loading</h2>
-<h3>1. SPI Auto Adaptive</h3>
-<p>When ExtensionLoader loads SPI, It will check spi attributes(using set method) . If one attribute is SPI, ExtensionLoader will load the SPI implementation. Auto injected object is an adaptive instance（proxy） ,because the real implementation is confirmed only in execution stage.。when adaptive spi is invoked, Dubbo will choose the real implementation and executes it. Dubbo choose the right implementation according to the parameters that the mehod defines.</p>
-<p>All the inner SPIs that Dubbo defines have the URL parameter defined for the method invocation. Adaptive SPI uses URL to determine which implementation is needed. One specific Key and Value in the URL confirms the usage of the specific implementation, All these is done by adding <code>@Adaptive</code> annotation.</p>
... 73341 lines suppressed ...