You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2017/12/25 02:21:43 UTC
[incubator-servicecomb-website] branch asf-site updated: Publish
the website
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a4bd5dc Publish the website
a4bd5dc is described below
commit a4bd5dcdb49ca63663ca1e5d08cabc4ea9d2aa97
Author: Willem Jiang <ji...@huawei.com>
AuthorDate: Mon Dec 25 10:21:25 2017 +0800
Publish the website
---
content/assets/images/local_develop_test_en.png | Bin 0 -> 20494 bytes
content/assets/images/servicecomb_mode_en.png | Bin 0 -> 33217 bytes
content/assets/images/thread-model-en.png | Bin 0 -> 28527 bytes
content/cn/developers/submit-codes/index.html | 20 +-
content/cn/users/run-mode/index.html | 4 +
content/developers/submit-codes/index.html | 20 +-
content/feed.xml | 2 +-
content/users/application-boot-process/index.html | 36 +--
content/users/communicate-protocol/index.html | 279 ++++++++++---------
content/users/customized-tracing/index.html | 76 ++---
content/users/develop-with-jax-rs/index.html | 78 +++---
.../users/develop-with-rest-template/index.html | 42 +--
content/users/develop-with-rpc/index.html | 32 +--
content/users/develop-with-springmvc/index.html | 82 +++---
.../users/develop-with-transparent-rpc/index.html | 74 +++--
content/users/distributed-tracing/index.html | 56 ++--
content/users/edging-service/nginx/index.html | 88 +++---
content/users/edging-service/zuul/index.html | 124 ++++-----
content/users/index.html | 100 +++----
content/users/invoke-control/index.html | 129 ++++-----
content/users/local-develop-test/index.html | 67 +++--
content/users/run-mode/index.html | 66 +++--
content/users/service-configurations/index.html | 305 +++++++++++----------
content/users/service-contract/index.html | 94 +++----
content/users/service-definition/index.html | 106 +++----
content/users/service-heartbeat/index.html | 39 ++-
.../users/service-interface-constraints/index.html | 69 ++---
content/users/setup-environment/index.html | 56 ++--
content/users/use-service-contract/index.html | 71 +++--
.../use-servicecomb-in-spring-boot/index.html | 132 +++++----
content/users/use-tls/index.html | 204 +++++++-------
31 files changed, 1224 insertions(+), 1227 deletions(-)
diff --git a/content/assets/images/local_develop_test_en.png b/content/assets/images/local_develop_test_en.png
new file mode 100644
index 0000000..3e8845f
Binary files /dev/null and b/content/assets/images/local_develop_test_en.png differ
diff --git a/content/assets/images/servicecomb_mode_en.png b/content/assets/images/servicecomb_mode_en.png
new file mode 100644
index 0000000..1ed0525
Binary files /dev/null and b/content/assets/images/servicecomb_mode_en.png differ
diff --git a/content/assets/images/thread-model-en.png b/content/assets/images/thread-model-en.png
new file mode 100644
index 0000000..952899e
Binary files /dev/null and b/content/assets/images/thread-model-en.png differ
diff --git a/content/cn/developers/submit-codes/index.html b/content/cn/developers/submit-codes/index.html
index 1256270..50298db 100644
--- a/content/cn/developers/submit-codes/index.html
+++ b/content/cn/developers/submit-codes/index.html
@@ -351,11 +351,11 @@
<p> 在您提交代码前，请先按照项目README中说明的自动测试部分对代码的功能性和实现上的正确性进行验证。</p>
<h2 id="pr指南">PR指南</h2>
-<p> 在 <a href="https://github.com/ServiceComb">Github</a> 上面可以很方便地提交 <a href="https://help.github.com/articles/about-pull-requests/">Pull Request (PR)</a>，下面将以本网站项目<a href="https://github.com/ServiceComb/ServiceComb.github.io">ServiceComb/ServiceComb.github.io</a> 为例（如果是其他项目，请替换项目名ServiceComb.github.io）。</p>
+<p> 在 <a href="https://github.com/search?q=org%3Aapache+servicecomb">Github</a> 上面可以很方便地提交 <a href="https://help.github.com/articles/about-pull-requests/">Pull Request (PR)</a>，下面将以本网站项目<a href="https://github.com/apache/incubator-servicecomb-website">apache/incubator-servicecomb-website</a> 为例（如果是其他项目，请替换项目名incubator-servicecomb-website）。</p>
<h3 id="fork仓库">Fork仓库</h3>
-<p> 进入 ServiceComb/ServiceComb.github.io 的 <a href="https://github.com/ServiceComb/ServiceComb.github.io">github 页面</a> ，点击右上角按钮 <code class="highlighter-rouge">Fork</code> 进行 Fork。</p>
+<p> 进入 apache/incubator-servicecomb-website 的 <a href="https://github.com/apache/incubator-servicecomb-website">github 页面</a> ，点击右上角按钮 <code class="highlighter-rouge">Fork</code> 进行 Fork。</p>
<p><img src="/assets/images/fork-repo.jpg" alt="体质指数应用运行界面" class="align-center" /></p>
@@ -365,7 +365,7 @@
<li>
<p>将代码克隆到本地：</p>
- <div class="language-shell highlighter-rouge"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/ServiceComb.github.io.git
+ <div class="language-shell highlighter-rouge"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/incubator-servicecomb-website.git
</code></pre>
</div>
@@ -377,10 +377,10 @@
<ul>
<li>
- <p>将 ServiceComb/ServiceComb.github.io 添加为本地仓库的远程分支 upstream：</p>
+ <p>将 apache/incubator-servicecomb-website 添加为本地仓库的远程分支 upstream：</p>
- <div class="language-shell highlighter-rouge"><pre class="highlight"><code><span class="nb">cd </span>ServiceComb.github.io
-git remote add upstream https://github.com/ServiceComb/ServiceComb.github.io.git
+ <div class="language-shell highlighter-rouge"><pre class="highlight"><code><span class="nb">cd </span>incubator-servicecomb-website
+git remote add upstream https://github.com/apache/incubator-servicecomb-website.git
</code></pre>
</div>
</li>
@@ -388,10 +388,10 @@ git remote add upstream https://github.com/ServiceComb/ServiceComb.github.io.git
<p>检查远程仓库设置：</p>
<div class="language-shell highlighter-rouge"><pre class="highlight"><code>git remote -v
-origin https://github.com/<your_github_name>/ServiceComb.github.io.git <span class="o">(</span>fetch<span class="o">)</span>
-origin https://github.com/<your_github_name>/ServiceComb.github.io.git <span class="o">(</span>push<span class="o">)</span>
-upstream https://github.com/ServiceComb/ServiceComb.github.io.git <span class="o">(</span>fetch<span class="o">)</span>
-upstream https://github.com/ServiceComb/ServiceComb.github.io.git <span class="o">(</span>push<span class="o">)</span>
+origin https://github.com/<your_github_name>/incubator-servicecomb-website.git <span class="o">(</span>fetch<span class="o">)</span>
+origin https://github.com/<your_github_name>/incubator-servicecomb-website.git <span class="o">(</span>push<span class="o">)</span>
+upstream https://github.com/apache/incubator-servicecomb-website.git <span class="o">(</span>fetch<span class="o">)</span>
+upstream https://github.com/apache/incubator-servicecomb-website.git <span class="o">(</span>push<span class="o">)</span>
</code></pre>
</div>
</li>
diff --git a/content/cn/users/run-mode/index.html b/content/cn/users/run-mode/index.html
index c52d81f..d77f427 100644
--- a/content/cn/users/run-mode/index.html
+++ b/content/cn/users/run-mode/index.html
@@ -612,6 +612,10 @@
<h3 id="开发示例">开发示例</h3>
+<ul>
+ <li><strong>步骤1 新建servlet工程，修改web.xml文件如下：</strong></li>
+</ul>
+
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><web-app></span>
<span class="nt"><context-param></span>
<span class="nt"><param-name></span>contextConfigLocation<span class="nt"></param-name></span>
diff --git a/content/developers/submit-codes/index.html b/content/developers/submit-codes/index.html
index 33ae1ec..6a8e7b6 100644
--- a/content/developers/submit-codes/index.html
+++ b/content/developers/submit-codes/index.html
@@ -350,11 +350,11 @@
<p> 在您提交代码前，请先按照项目README中说明的自动测试部分对代码的功能性和实现上的正确性进行验证。</p>
<h2 id="pr指南">PR指南</h2>
-<p> 在 <a href="https://github.com/ServiceComb">Github</a> 上面可以很方便地提交 <a href="https://help.github.com/articles/about-pull-requests/">Pull Request (PR)</a>，下面将以本网站项目<a href="https://github.com/ServiceComb/ServiceComb.github.io">ServiceComb/ServiceComb.github.io</a> 为例（如果是其他项目，请替换项目名ServiceComb.github.io）。</p>
+<p> 在 <a href="https://github.com/search?q=org%3Aapache+servicecomb">Github</a> 上面可以很方便地提交 <a href="https://help.github.com/articles/about-pull-requests/">Pull Request (PR)</a>，下面将以本网站项目<a href="https://github.com/apache/incubator-servicecomb-website">apache/incubator-servicecomb-website</a> 为例（如果是其他项目，请替换项目名incubator-servicecomb-website）。</p>
<h3 id="fork仓库">Fork仓库</h3>
-<p> 进入 ServiceComb/ServiceComb.github.io 的 <a href="https://github.com/ServiceComb/ServiceComb.github.io">github 页面</a> ，点击右上角按钮 <code class="highlighter-rouge">Fork</code> 进行 Fork。</p>
+<p> 进入 apache/incubator-servicecomb-website 的 <a href="https://github.com/apache/incubator-servicecomb-website">github 页面</a> ，点击右上角按钮 <code class="highlighter-rouge">Fork</code> 进行 Fork。</p>
<p><img src="/assets/images/fork-repo.jpg" alt="体质指数应用运行界面" class="align-center" /></p>
@@ -364,7 +364,7 @@
<li>
<p>将代码克隆到本地：</p>
- <div class="language-shell highlighter-rouge"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/ServiceComb.github.io.git
+ <div class="language-shell highlighter-rouge"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/incubator-servicecomb-website.git
</code></pre>
</div>
@@ -376,10 +376,10 @@
<ul>
<li>
- <p>将 ServiceComb/ServiceComb.github.io 添加为本地仓库的远程分支 upstream：</p>
+ <p>将 apache/incubator-servicecomb-website 添加为本地仓库的远程分支 upstream：</p>
- <div class="language-shell highlighter-rouge"><pre class="highlight"><code><span class="nb">cd </span>ServiceComb.github.io
-git remote add upstream https://github.com/ServiceComb/ServiceComb.github.io.git
+ <div class="language-shell highlighter-rouge"><pre class="highlight"><code><span class="nb">cd </span>incubator-servicecomb-website
+git remote add upstream https://github.com/apache/incubator-servicecomb-website.git
</code></pre>
</div>
</li>
@@ -387,10 +387,10 @@ git remote add upstream https://github.com/ServiceComb/ServiceComb.github.io.git
<p>检查远程仓库设置：</p>
<div class="language-shell highlighter-rouge"><pre class="highlight"><code>git remote -v
-origin https://github.com/<your_github_name>/ServiceComb.github.io.git <span class="o">(</span>fetch<span class="o">)</span>
-origin https://github.com/<your_github_name>/ServiceComb.github.io.git <span class="o">(</span>push<span class="o">)</span>
-upstream https://github.com/ServiceComb/ServiceComb.github.io.git <span class="o">(</span>fetch<span class="o">)</span>
-upstream https://github.com/ServiceComb/ServiceComb.github.io.git <span class="o">(</span>push<span class="o">)</span>
+origin https://github.com/<your_github_name>/incubator-servicecomb-website.git <span class="o">(</span>fetch<span class="o">)</span>
+origin https://github.com/<your_github_name>/incubator-servicecomb-website.git <span class="o">(</span>push<span class="o">)</span>
+upstream https://github.com/apache/incubator-servicecomb-website.git <span class="o">(</span>fetch<span class="o">)</span>
+upstream https://github.com/apache/incubator-servicecomb-website.git <span class="o">(</span>push<span class="o">)</span>
</code></pre>
</div>
</li>
diff --git a/content/feed.xml b/content/feed.xml
index 1b0b323..8491a88 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.4.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2017-12-22T16:06:24+08:00</updated><id>/</id><title type="html">Apache incubator ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=>&qu [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.4.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2017-12-25T10:18:33+08:00</updated><id>/</id><title type="html">Apache incubator ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=>&qu [...]
<p>The architecture of the <code class="highlighter-rouge">service registry</code> module in Java Chassis is as follows.</p>
diff --git a/content/users/application-boot-process/index.html b/content/users/application-boot-process/index.html
index 36ec06c..03bdefe 100644
--- a/content/users/application-boot-process/index.html
+++ b/content/users/application-boot-process/index.html
@@ -19,12 +19,12 @@
-<title>程序启动逻辑 - Apache incubator ServiceComb</title>
+<title>Application Boot-up Process - Apache incubator ServiceComb</title>
-<meta name="description" content="程序启动逻辑">
+<meta name="description" content="Application Boot-up Process">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="程序启动逻辑">
+<meta property="og:title" content="Application Boot-up Process">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/application-boot-process/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="程序启动逻辑">
+ <meta property="og:description" content="Application Boot-up Process">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="程序启动逻辑">
- <meta name="twitter:description" content="程序启动逻辑">
+ <meta name="twitter:title" content="Application Boot-up Process">
+ <meta name="twitter:description" content="Application Boot-up Process">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="程序启动逻辑">
- <meta itemprop="description" content="程序启动逻辑">
+ <meta itemprop="headline" content="Application Boot-up Process">
+ <meta itemprop="description" content="Application Boot-up Process">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">程序启动逻辑
+ <h1 class="page__title" itemprop="headline">Application Boot-up Process
</h1>
</header>
@@ -560,29 +560,29 @@
<section class="page__content" itemprop="text">
- <p>服务提供者的启动过程分为初始化Log4j、bean加载（包括配置加载）和服务注册三部分。</p>
+ <p>The starup process of a service provider includes initializing Log4j, loading bean(including its parameters), and registering service.</p>
<ul>
<li>
- <p>初始化Log4j</p>
+ <p>Initialize Log4j:</p>
- <p><code class="highlighter-rouge">Log4jUtils</code>默认会从<code class="highlighter-rouge">classpath\*:config/base/log4j.properties</code>和<code class="highlighter-rouge">classpath\*:config/log4j.properties</code>两个路径读取log4j配置并合并，将其传递给Log4j的<code class="highlighter-rouge">PropertyConfigurator</code>方法初始化Log4j。如果优先级最高的配置文件是在磁盘上，且其所在目录有写权限，则将合并的配置输出到该目录，以便于维护时观察生效的参数。</p>
+ <p>By default, <code class="highlighter-rouge">Log4jUtils</code> obtains the configuration of log4j from the <code class="highlighter-rouge">classpath\*:config/base/log4j.properties</code> and <code class="highlighter-rouge">classpath\*:config/log4j.properties</code> files. combines them, and transfer them to PropertyConfigurator of log4j to initialize log4j. If the configuration file having the highest priority is stored on the disk and its directory has write permission, save the c [...]
</li>
<li>
- <p>bean加载</p>
+ <p>Load the bean.</p>
- <p><code class="highlighter-rouge">BeanUtils</code>默认会从<code class="highlighter-rouge">classpath\*:META-INF/spring/\*.bean.xml</code>路径加载配置文件，并将其传递给Spring框架的<code class="highlighter-rouge">ClassPathXmlApplicationContext</code>完成应用上下文加载。在这个过程中会加载foundation-config模块的bean，完成配置加载。</p>
+ <p>By default <code class="highlighter-rouge">BeanUtils</code> loads the configuration file from the <code class="highlighter-rouge">classpath\*:META-INF/spring/\*.bean.xml</code> path and transfer the configuration to <code class="highlighter-rouge">ClassPathXmlApplicationContext</code> of the Spring framework to load the context. In this process, <code class="highlighter-rouge">BeanUtils</code> loads the bean of foundation-config module.</p>
</li>
<li>
- <p>服务注册</p>
+ <p>Register the microservice.</p>
- <p>在Spring context加载完成后，<code class="highlighter-rouge">io.servicecomb.core.CseApplicationListener</code>会加载handler配置、加载provider的schema信息，最后将微服务信息注册到服务中心。</p>
+ <p>After Spring context has been loaded, <code class="highlighter-rouge">io.servicecomb.core.CseApplicationListener</code> will configure the handler, load the information about the provider schema, and the register microservice to service center.</p>
</li>
</ul>
<blockquote>
- <p><strong>说明：</strong>
-ServiceComb的配置项分为三个层次：配置中心、环境变量、本地文件，三者优先级依次递减，高优先级中的配置项覆盖低优先级同名配置项。存放在配置中心的配置项可以在运行时修改。</p>
+ <p><strong>NOTE:</strong>
+The three level of configuration items for ServiceComb are the configuration center, environment variables, and local files, listed in a descending order by priority. If configuration items with the same name exist, the one in the highest level overwrites others. Configuration items stored in the configuration center can be modified during running.</p>
</blockquote>
diff --git a/content/users/communicate-protocol/index.html b/content/users/communicate-protocol/index.html
index cc70135..af4a0a9 100644
--- a/content/users/communicate-protocol/index.html
+++ b/content/users/communicate-protocol/index.html
@@ -19,12 +19,12 @@
-<title>通信协议 - Apache incubator ServiceComb</title>
+<title>Communication Protocol - Apache incubator ServiceComb</title>
-<meta name="description" content="通信协议">
+<meta name="description" content="Communication Protocol">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="通信协议">
+<meta property="og:title" content="Communication Protocol">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/communicate-protocol/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="通信协议">
+ <meta property="og:description" content="Communication Protocol">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="通信协议">
- <meta name="twitter:description" content="通信协议">
+ <meta name="twitter:title" content="Communication Protocol">
+ <meta name="twitter:description" content="Communication Protocol">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="通信协议">
- <meta itemprop="description" content="通信协议">
+ <meta itemprop="headline" content="Communication Protocol">
+ <meta itemprop="description" content="Communication Protocol">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">通信协议
+ <h1 class="page__title" itemprop="headline">Communication Protocol
</h1>
</header>
@@ -564,30 +564,29 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#通信协议" id="markdown-toc-通信协议">通信协议</a> <ul>
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
+ <li><a href="#communication-protocol" id="markdown-toc-communication-protocol">Communication Protocol</a> <ul>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#precautions" id="markdown-toc-precautions">Precautions</a></li>
</ul>
</li>
- <li><a href="#线程模型" id="markdown-toc-线程模型">线程模型</a> <ul>
- <li><a href="#概念阐述-1" id="markdown-toc-概念阐述-1">概念阐述</a></li>
- <li><a href="#完整线程" id="markdown-toc-完整线程">完整线程</a></li>
+ <li><a href="#thread-model" id="markdown-toc-thread-model">Thread Model</a> <ul>
+ <li><a href="#concept-description-1" id="markdown-toc-concept-description-1">Concept Description</a></li>
+ <li><a href="#thread-model-1" id="markdown-toc-thread-model-1">Thread Model</a></li>
</ul>
</li>
<li><a href="#rest-over-servlet" id="markdown-toc-rest-over-servlet">REST over Servlet</a> <ul>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</li>
<li><a href="#rest-over-vertx" id="markdown-toc-rest-over-vertx">REST over Vertx</a> <ul>
- <li><a href="#配置说明-1" id="markdown-toc-配置说明-1">配置说明</a></li>
- <li><a href="#示例代码-1" id="markdown-toc-示例代码-1">示例代码</a></li>
+ <li><a href="#configuration-1" id="markdown-toc-configuration-1">Configuration</a></li>
+ <li><a href="#sample-code-1" id="markdown-toc-sample-code-1">Sample Code</a></li>
</ul>
</li>
- <li><a href="#highway-rpc协议" id="markdown-toc-highway-rpc协议">Highway RPC协议</a> <ul>
- <li><a href="#概念阐述-2" id="markdown-toc-概念阐述-2">概念阐述</a></li>
- <li><a href="#配置说明-2" id="markdown-toc-配置说明-2">配置说明</a></li>
- <li><a href="#示例代码-2" id="markdown-toc-示例代码-2">示例代码</a></li>
+ <li><a href="#highway-rpc-protocol" id="markdown-toc-highway-rpc-protocol">Highway RPC Protocol</a> <ul>
+ <li><a href="#concept-description-2" id="markdown-toc-concept-description-2">Concept Description</a></li>
+ <li><a href="#configuration-2" id="markdown-toc-configuration-2">Configuration</a></li>
</ul>
</li>
</ul>
@@ -595,49 +594,49 @@
</nav>
</aside>
-<h2 id="通信协议">通信协议</h2>
-<h3 id="概念阐述">概念阐述</h3>
+<h2 id="communication-protocol">Communication Protocol</h2>
+<h3 id="concept-description">Concept Description</h3>
-<p>ServiceComb实现了两种网络通道，包括REST和Highway，均支持TLS加密传输。其中，REST网络通道将服务以标准RESTful形式发布，调用端兼容直接使用http client使用标准RESTful形式进行调用。</p>
+<p>ServiceComb uses two network channels, REST and Highway, both supporting encrypted Transport Layer Security (TLS) transmission. The REST channel releases services in the standard RESTful form. The consumer can send requests using http client.</p>
-<h3 id="注意事项">注意事项</h3>
+<h3 id="precautions">Precautions</h3>
-<p>参数和返回值的序列化：</p>
+<p>Serialization of parameters and the returned values:</p>
-<p>当前REST通道的body参数只支持application/json序列化方式，如果要向服务端发送form类型的参数，那么需要在调用端构造好application/json格式的body，不能直接以multipart/form-data格式传递form类型参数。</p>
+<p>Currently, the body parameters of the REST channel support only the application/json serialization. To send form-type parameters to the server, construct a body of the application/json format at the consumer end. Do not send the form type parameters in multipart/form-data format.</p>
-<p>当前REST通道返回值支持application/json和text/plain两种格式，服务提供者通过produces声明可提供序列化能力，服务消费者通过请求的Accept头指明返回值序列化方式，默认返回application/json格式的数据。</p>
+<p>Currently, the REST channel supports the application/json and text/plain serialization. A provider uses produces to declare that it has the serialization capability. The consumer specifies the serialization mode of the returned values by setting parameters regarding the requested Accept header. Data serialized in application/json serialization mode is returned by default.</p>
-<h2 id="线程模型">线程模型</h2>
-<h3 id="概念阐述-1">概念阐述</h3>
+<h2 id="thread-model">Thread Model</h2>
+<h3 id="concept-description-1">Concept Description</h3>
-<p>本小节主要介绍ServiceComb微服务的完整线程模型，介绍IO线程和业务线程之间的关系</p>
+<p>This section describes the thread model for ServiceComb microservices and the relationship between the I/O and service threads.</p>
-<h3 id="完整线程">完整线程</h3>
+<h3 id="thread-model-1">Thread Model</h3>
-<p>ServiceComb微服务的完整线程模型如下图所示：</p>
+<p>The complete thread model of CSE is shown in the following figure.</p>
-<p><img src="/assets/images/thread-model.png" alt="" /></p>
+<p><img src="/assets/images/thread-model-en.png" alt="" /></p>
<blockquote>
<ol>
- <li>业务线程在第一次调用时会绑定某一个网络线程,避免在不同网络线程之间切换,无谓地增加线程冲突的概率</li>
- <li>业务线程绑定网络线程后,会再绑定该网络线程内部的某个连接,同样是为了避免线程冲突</li>
+ <li>When a service thread is called for the first time, it binds to a network thread to avoid thread conflicts caused by switching among different network threads.</li>
+ <li>After the service thread bound to a network thread, it will bind to a connection of the network to avoid thread conflicts.</li>
</ol>
</blockquote>
<ul>
- <li>客户端和服务器都可以配置多个网络线程(eventloop)，默认为CPU核数的两倍，每个网络线程可以配置多个连接，默认为1，支持Rest和Highway两种网络通道，具体配置请查看如下章节：
+ <li>Multiple network threads (eventloop) can be bound to both the client and the server. The number of network threads is two times the quantity of the CPU cores by default. Multiple connections can be configured for each network thread, and the default number is 1. The Rest and Highway network channels are supported. For details about these configurations, see following sections:
<ul>
<li><a href="/users/communicate-protocol#rest-over-servlet">REST over Servlet</a></li>
<li><a href="/users/communicate-protocol/#rest-over-vertx">REST over Vertx</a></li>
- <li><a href="/users/communicate-protocol/#highway-rpc协议">Highway RPC协议</a></li>
+ <li><a href="/users/communicate-protocol/#highway-rpc协议">Highway RPC Protocol</a></li>
</ul>
</li>
- <li>客户端可配置业务线程池executor，线程粒度可细化至schemaId:operation，配置如下：</li>
+ <li>You can configure the service thread pool executor for the client, and the thread granularity can be schemaId: operation.</li>
</ul>
-<p>在microservice.yaml中添加executors配置，为schemaId:operation配置单独的业务线程池：</p>
+<p>Add the executors in the microservice.yaml file and configure an independent service thread pool for schemaId: operation:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">executors</span><span class="pi">:</span>
@@ -647,15 +646,15 @@
</div>
<h2 id="rest-over-servlet">REST over Servlet</h2>
-<h3 id="配置说明">配置说明</h3>
+<h3 id="configuration">Configuration</h3>
-<p> REST over Servlet对应使用web容器模式部署运行，需要新建一个servlet工程将微服务包装起来，加载到web容器中启动运行，包装微服务的方法有两种，一种完全使用web.xml配置文件配置，另一种仅在web.xml文件中配置listener，在microservice.yaml文件中配置urlPattern，两种方式如下所示：</p>
+<p> REST over Servlet is deployed and runs using a web container. You need to create a servlet project to pack the microservice, load it to the web container, and then start it. To pack a microservice, you can either fully configure it in the web.xml, or configure its listener and urlPattern in the web.xml and microservice.yaml files, respectively.</p>
<ul>
<li>
- <p>在web.xml文件中完成全部配置</p>
+ <p>Configure the microservice in the web.xml file.</p>
- <p>web.xml文件配置在项目的src/main/webapp/WEB_INF目录，配置内容如下：</p>
+ <p>The web.xml file is under the src/main/webapp/WEB_INF directory of the project, and its content is as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><web-app</span> <span class="na">xmlns=</span><span class="s">"http://java.sun.com/xml/ns/javaee"</span> <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span> <span class="na">xsi:schemaLocation=</span><span class="s">"http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"</span> <span class="na">version=</span><spa [...]
<span class="nt"><context-param></span>
@@ -680,7 +679,7 @@
</div>
</li>
<li>
- <p>在web.xml文件中仅配置listener，在microservice.yaml文件中配置urlPattern</p>
+ <p>Configure the listener in the web.xml file and urlPattern in the microservice.yaml file.</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><web-app</span> <span class="na">xmlns=</span><span class="s">"http://java.sun.com/xml/ns/javaee"</span> <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span> <span class="na">xsi:schemaLocation=</span><span class="s">"http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"</span> <span class="na">version=</span><spa [...]
<span class="nt"><context-param></span>
@@ -694,7 +693,7 @@
</code></pre>
</div>
- <p>在microservice.yaml文件中需要增加一行配置来指定urlPattern：</p>
+ <p>In the microservice.yaml file, add a row to specify the urlPattern：</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">servicecomb.rest.servlet.urlPattern</span><span class="pi">:</span> <span class="s">/rest/*</span>
</code></pre>
@@ -702,7 +701,7 @@
</li>
</ul>
-<p>以上两种方式是等效的，两种方式都需要在maven pom文件中添加如下依赖：</p>
+<p>The two method are equivalent, and they both require that the following dependencies be added in the pox.xml file:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -711,19 +710,19 @@
</code></pre>
</div>
-<p>REST over Servlet在microservice.yaml文件中的配置项见下表：</p>
+<p>Configuration items that need to be set in the microservice.yaml file are described in Table 1:</p>
-<p>表1 REST over Servlet配置项说明</p>
+<p>Table 1 Configuration items of REST over Servlet</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remark</th>
</tr>
</thead>
<tbody>
@@ -731,48 +730,48 @@
<td style="text-align: left">cse.rest.address</td>
<td style="text-align: left">0.0.0.0:8080</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务监听地址</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the server listening IP address.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.rest.timeout</td>
<td style="text-align: left">3000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">超时时间</td>
- <td style="text-align: left">单位为毫秒</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the timeout duration</td>
+ <td style="text-align: left">The unit is ms.</td>
</tr>
<tr>
<td style="text-align: left">cse.request.timeout</td>
<td style="text-align: left">30000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">请求超时时间</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the request timeout duration.</td>
+ <td style="text-align: left">The configuration of this parameter for REST over Servlet is the same as that for REST over Vertx.</td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].transport</td>
<td style="text-align: left">rest</td>
<td style="text-align: left"> </td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问的transport类型</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the accessed transport type.</td>
+ <td style="text-align: left">The configuration of this parameter for REST over Servlet is the same as that for REST over Vertx.</td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].version-rule</td>
<td style="text-align: left">latest</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问实例的版本号</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the version of the accessed instance.</td>
+ <td style="text-align: left">The configuration of this parameter for REST over Servlet is the same as that for REST over Vertx.</td>
</tr>
</tbody>
</table>
-<h3 id="示例代码">示例代码</h3>
+<h3 id="sample-code">Sample Code</h3>
-<p>microservice.yaml文件中的配置示例如下：</p>
+<p>The following is an example of the configuration in the microservice.yaml file for REST over Servlet:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">rest</span><span class="pi">:</span>
@@ -782,23 +781,23 @@
</div>
<h2 id="rest-over-vertx">REST over Vertx</h2>
-<h3 id="配置说明-1">配置说明</h3>
+<h3 id="configuration-1">Configuration</h3>
-<p>REST over Vertx通信通道对应使用standalone部署运行模式，可直接通过main函数拉起。main函数中需要初始化日志和加载服务配置，代码如下：</p>
+<p>The REST over Vertx communication channel uses the standalone running mode that can be started using the main function. In the main function, you need to initialize logs and load service configuration. The code is as follow:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kn">import</span> <span class="nn">io.servicecomb.foundation.common.utils.BeanUtils</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.servicecomb.foundation.common.utils.Log4jUtils</span><span class="o">;</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">MainServer</span> <span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>
- <span class="err"> </span><span class="n">Log4jUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span><span class="c1">//日志初始化</span>
- <span class="err"> </span><span class="n">BeanUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="c1">// Spring bean初始化</span>
+ <span class="err"> </span><span class="n">Log4jUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span><span class="c1">//Log initialization</span>
+ <span class="err"> </span><span class="n">BeanUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="c1">// Spring bean initialization</span>
<span class="o">}</span>
<span class="o">}</span>
</code></pre>
</div>
-<p>使用REST over Vertx网络通道需要在maven pom文件中添加如下依赖：</p>
+<p>To use the REST over Vertx communication channel, you need to add the following dependencies in the maven pom.xml file:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -807,19 +806,19 @@
</code></pre>
</div>
-<p>REST over Vertx通道在microservice.yaml文件中有以下配置项：</p>
+<p>Configuration items that need to be set in the microservice.yaml file are described as follows:</p>
-<p>表2 REST over Vertx配置项说明</p>
+<p>Table 2 Configuration items of REST over Vertx</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remark</th>
</tr>
</thead>
<tbody>
@@ -827,64 +826,64 @@
<td style="text-align: left">cse.rest.address</td>
<td style="text-align: left">0.0.0.0:8080</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务监听地址</td>
- <td style="text-align: left">仅服务提供者需要配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the server listening IP address.</td>
+ <td style="text-align: left">Only service providers require this parameter.</td>
</tr>
<tr>
<td style="text-align: left">cse.rest.server.thread-count</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务端线程数</td>
- <td style="text-align: left">仅服务提供者需要配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of server threads.</td>
+ <td style="text-align: left">Only service providers require this parameter.</td>
</tr>
<tr>
<td style="text-align: left">cse.rest.client.thread-count</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端网络线程数</td>
- <td style="text-align: left">仅服务消费者需要配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of client network threads.</td>
+ <td style="text-align: left">Only service consumers require this parameter.</td>
</tr>
<tr>
<td style="text-align: left">cse.rest.client.connection-pool-per-thread</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端每个网络线程中的连接池的个数</td>
- <td style="text-align: left">仅服务消费者需要配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of connection pools in each client thread.</td>
+ <td style="text-align: left">Only service consumers require this parameter.</td>
</tr>
<tr>
<td style="text-align: left">cse.request.timeout</td>
<td style="text-align: left">30000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">请求超时时间</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the request timeout duration.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].transport</td>
<td style="text-align: left">rest</td>
<td style="text-align: left"> </td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问的transport类型</td>
- <td style="text-align: left">仅服务消费者需要配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the accessed transport type.</td>
+ <td style="text-align: left">Only service consumers require this parameter.</td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].version-rule</td>
<td style="text-align: left">latest</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问实例的版本号</td>
- <td style="text-align: left">仅服务消费者需要配置支持latest，1.0.0+，1.0.0-2.0.2，精确版本。详细参考服务中心的接口描述。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the version of the accessed instance.</td>
+ <td style="text-align: left">Only service consumers require this parameter. You can set it to latest, a version range such as 1.0.0+ or 1.0.0-2.0.2, or a specific version number. For details, see the API description of the service center.</td>
</tr>
</tbody>
</table>
-<h3 id="示例代码-1">示例代码</h3>
+<h3 id="sample-code-1">Sample Code</h3>
-<p>microservice.yaml文件中的配置示例：</p>
+<p>An example of the configuration in the microservice.yaml file for REST over Vertx is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">rest</span><span class="pi">:</span>
@@ -897,14 +896,14 @@
</code></pre>
</div>
-<h2 id="highway-rpc协议">Highway RPC协议</h2>
-<h3 id="概念阐述-2">概念阐述</h3>
+<h2 id="highway-rpc-protocol">Highway RPC Protocol</h2>
+<h3 id="concept-description-2">Concept Description</h3>
-<p>Highway是ServiceComb的高性能私有协议，用户可在有特殊性能需求的场景下选用。</p>
+<p>Highway is a high-performance proprietary protocol of ServiceComb, and you can use it in scenarios having special performance requirements.</p>
-<h3 id="配置说明-2">配置说明</h3>
+<h3 id="configuration-2">Configuration</h3>
-<p>使用Highway网络通道需要在maven pom文件中添加如下依赖：</p>
+<p>To use the Highway communication channel, you need to add the following dependencies in the maven pom.xml file:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -913,19 +912,19 @@
</code></pre>
</div>
-<p>Highway通道在microservice.yaml文件中的配置项如下表所示：</p>
+<p>Configuration items that need to be set in the microservice.yaml file are described as follows:</p>
-<p>表3 Highway配置项说明</p>
+<p>Table 3 Configuration items of Highway</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remark</th>
</tr>
</thead>
<tbody>
@@ -933,64 +932,64 @@
<td style="text-align: left">cse.highway.address</td>
<td style="text-align: left">0.0.0.0:7070</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务监听地址</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the server listening IP address.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.highway.server.thread-count</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务端网络线程个数</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of server network threads.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.highway.client.thread-count</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端网络线程个数</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of client network threads.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.highway.client.connection-pool-per-thread</td>
<td style="text-align: left">1</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端每个网络线程的连接池个数</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of connection pools in each client thread.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.request.timeout</td>
<td style="text-align: left">30000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">请求超时时间</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the request timeout duration.</td>
+ <td style="text-align: left">The configuration of this parameter for Highway is the same as that for REST over Vertx.</td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].transport</td>
<td style="text-align: left">rest</td>
<td style="text-align: left"> </td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问的transport类型</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the accessed transport type.</td>
+ <td style="text-align: left">The configuration of this parameter for Highway is the same as that for REST over Vertx.</td>
</tr>
<tr>
<td style="text-align: left">cse.references.[服务名].version-rule</td>
<td style="text-align: left">latest</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">访问实例的版本号</td>
- <td style="text-align: left">同REST over Vertx的配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the version of the accessed instance.</td>
+ <td style="text-align: left">The configuration of this parameter for Highway is the same as that for REST over Vertx.</td>
</tr>
</tbody>
</table>
-<h3 id="示例代码-2">示例代码</h3>
+<p>###</p>
-<p>microservice.yaml文件中的配置示例：</p>
+<p>An example of the configuration in the microservice.yaml file for Highway is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">highway</span><span class="pi">:</span>
diff --git a/content/users/customized-tracing/index.html b/content/users/customized-tracing/index.html
index 4809ccd..d28086c 100644
--- a/content/users/customized-tracing/index.html
+++ b/content/users/customized-tracing/index.html
@@ -24,7 +24,7 @@
-<meta name="description" content="自定义调用链打点">
+<meta name="description" content="Dotting for Customized Tracing">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="自定义调用链打点">
+ <meta property="og:description" content="Dotting for Customized Tracing">
<meta name="twitter:site" content="@ServiceComb">
<meta name="twitter:title" content="Customized Tracing">
- <meta name="twitter:description" content="自定义调用链打点">
+ <meta name="twitter:description" content="Dotting for Customized Tracing">
<meta name="twitter:url" content="">
@@ -544,7 +544,7 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
<meta itemprop="headline" content="Customized Tracing">
- <meta itemprop="description" content="自定义调用链打点">
+ <meta itemprop="description" content="Dotting for Customized Tracing">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -564,48 +564,48 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#前提条件" id="markdown-toc-前提条件">前提条件</a></li>
- <li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
- <li><a href="#自定义调用链打点" id="markdown-toc-自定义调用链打点">自定义调用链打点</a></li>
- <li><a href="#使用步骤" id="markdown-toc-使用步骤">使用步骤:</a> <ul>
- <li><a href="#添加依赖" id="markdown-toc-添加依赖">添加依赖</a></li>
- <li><a href="#启用自定义打点功能" id="markdown-toc-启用自定义打点功能">启用自定义打点功能</a></li>
- <li><a href="#定制打点" id="markdown-toc-定制打点">定制打点</a></li>
+ <li><a href="#concept-disctiption" id="markdown-toc-concept-disctiption">Concept Disctiption</a></li>
+ <li><a href="#prerequisites" id="markdown-toc-prerequisites">Prerequisites</a></li>
+ <li><a href="#precautions" id="markdown-toc-precautions">Precautions</a></li>
+ <li><a href="#customized-dotting-call-chain" id="markdown-toc-customized-dotting-call-chain">Customized Dotting Call Chain</a></li>
+ <li><a href="#procedure" id="markdown-toc-procedure">Procedure:</a> <ul>
+ <li><a href="#add-dependency" id="markdown-toc-add-dependency">Add dependency</a></li>
+ <li><a href="#enable-customized-dotting" id="markdown-toc-enable-customized-dotting">Enable customized dotting</a></li>
+ <li><a href="#customize-dotting" id="markdown-toc-customize-dotting">Customize dotting</a></li>
</ul>
</li>
- <li><a href="#定制上报的数据" id="markdown-toc-定制上报的数据">定制上报的数据</a></li>
+ <li><a href="#customize-reported-data" id="markdown-toc-customize-reported-data">Customize reported data</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-disctiption">Concept Disctiption</h2>
-<p>分布式调用链追踪提供了服务间调用的时序信息，但服务内部的链路调用信息对开发者同样重要，如果能将两者合二为一，就能提供更完整的调用链，更容易定位错误和潜在性能问题。</p>
+<p>A distributed call chain tracking records the service calling sequence, but developers also need information about link invocation inside a microservice to describe a complete call chain. In this way, they can locate error and identify potential performance problems more easily.</p>
-<h2 id="前提条件">前提条件</h2>
+<h2 id="prerequisites">Prerequisites</h2>
<ul>
- <li>使用自定义打点功能需要首先配置并启用Java Chassis微服务调用链。</li>
+ <li>To use the customized dotting function, you need to configure and set the Java Chassis microservice call chain.</li>
</ul>
-<h2 id="注意事项">注意事项</h2>
+<h2 id="precautions">Precautions</h2>
<ul>
- <li>使用<code class="highlighter-rouge">@Span</code>注释的自定义打点功能只支持和Java Chassis调用请求同一线程的方法调用。</li>
- <li>添加<code class="highlighter-rouge">@Span</code>注释的方法必须是Spring管理的Bean，否则需要按这里<a href="https://stackoverflow.com/questions/41383941/load-time-weaving-for-non-spring-beans-in-a-spring-application">提到的方法</a>配置。</li>
+ <li>The customized dotting that uses the <code class="highlighter-rouge">@Span</code> annotation can only be called using the thread that calls Java Chassis.</li>
+ <li>To add the <code class="highlighter-rouge">@Span</code> annotation, you must use the Bean method of Spring. Otherwise, you need to configure dotting following the procedure in this section.</li>
</ul>
-<h2 id="自定义调用链打点">自定义调用链打点</h2>
+<h2 id="customized-dotting-call-chain">Customized Dotting Call Chain</h2>
-<p>该功能集成了Zipkin，提供<code class="highlighter-rouge">@Span</code>注释为需要追踪的方法自定义打点。Java Chassis将自动追踪所有添加<code class="highlighter-rouge">@Span</code>注释的方法，把每个方法的本地调用信息与服务间调用信息连接起来。</p>
+<p>This function integrates Zipkin and provides the <code class="highlighter-rouge">@Span</code> annotation to customize dotting for the method you want to track. Java Chassis automatically tracks all the methods that track the <code class="highlighter-rouge">@Span</code> annotation, associating the local method call information with the call information between services.</p>
-<h2 id="使用步骤">使用步骤:</h2>
+<h2 id="procedure">Procedure:</h2>
-<h3 id="添加依赖">添加依赖</h3>
+<h3 id="add-dependency">Add dependency</h3>
-<p>基于 ServiceComb Java Chassis 的微服务只需要添加如下依赖到 pom.xml：</p>
+<p>For microservices based on ServiceComb Java Chassis, add the following content to pom.xml</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -614,9 +614,9 @@
</code></pre>
</div>
-<h3 id="启用自定义打点功能">启用自定义打点功能</h3>
+<h3 id="enable-customized-dotting">Enable customized dotting</h3>
-<p>在应用入口或Spring配置类上添加<code class="highlighter-rouge">@EnableZipkinTracing</code>注释：</p>
+<p>Addthe <code class="highlighter-rouge">@EnableZipkinTracing</code> annotation to the application portal or the Spring configuration class:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="nd">@SpringBootApplication</span>
<span class="nd">@EnableZipkinTracing</span>
@@ -628,9 +628,9 @@
</code></pre>
</div>
-<h3 id="定制打点">定制打点</h3>
+<h3 id="customize-dotting">Customize dotting</h3>
-<p>在需要定制打点的方法上添加<code class="highlighter-rouge">@Span</code>注释：</p>
+<p>Add the <code class="highlighter-rouge">@Span</code> annotation to the method that requires dotting customization:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="nd">@Component</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">SlowRepoImpl</span> <span class="kd">implements</span> <span class="n">SlowRepo</span> <span class="o">{</span>
@@ -649,18 +649,20 @@
</code></pre>
</div>
-<p>就这样，通过使用<code class="highlighter-rouge">@Span</code>注释，我们启动了基于 Zipkin 的自定义打点功能。</p>
+<p>In this way, Zipkin-based customized dotting is enabled using the @Span annotation.</p>
-<h2 id="定制上报的数据">定制上报的数据</h2>
+<h2 id="customize-reported-data">Customize reported data</h2>
-<p>通过自定义打点上报的调用链包含两条数据：</p>
+<p>The call chain reported by customized dotting contains the following pieces of data:</p>
<ul>
- <li><strong>span name</strong> 默认为当前注释的方法全名。</li>
- <li><strong>call.path</strong> 默认为当前注释的方法签名。</li>
-</ul>
+ <li><strong>span name</strong> which is the full name of the annotated method by default.</li>
+ <li>
+ <p><strong>call.path</strong> which is the signature of the annotated method by default.</p>
-<p>例如，上述例子<code class="highlighter-rouge">SlowRepoImp</code>里上报的数据如下：</p>
+ <p>For example, the data reported in SlowRepoImp is as follows:</p>
+ </li>
+</ul>
<table>
<thead>
@@ -681,7 +683,7 @@
</tbody>
</table>
-<p>如果需要定制上报的数据内容，可以传入自定义的参数：</p>
+<p>To customize reported data, you can specify customized parameters:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">static</span> <span class="kd">class</span> <span class="nc">CustomSpanTask</span> <span class="o">{</span>
<span class="nd">@Span</span><span class="o">(</span><span class="n">spanName</span> <span class="o">=</span> <span class="s">"transaction1"</span><span class="o">,</span> <span class="n">callPath</span> <span class="o">=</span> <span class="s">"startA"</span><span class="o">)</span>
diff --git a/content/users/develop-with-jax-rs/index.html b/content/users/develop-with-jax-rs/index.html
index f417335..0f11012 100644
--- a/content/users/develop-with-jax-rs/index.html
+++ b/content/users/develop-with-jax-rs/index.html
@@ -19,12 +19,12 @@
-<title>用JAX-RS开发微服务 - Apache incubator ServiceComb</title>
+<title>Development Style-JAX-RS - Apache incubator ServiceComb</title>
-<meta name="description" content="用JAX-RS开发微服务">
+<meta name="description" content="Development Style-JAX-RS">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="用JAX-RS开发微服务">
+<meta property="og:title" content="Development Style-JAX-RS">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/develop-with-jax-rs/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="用JAX-RS开发微服务">
+ <meta property="og:description" content="Development Style-JAX-RS">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="用JAX-RS开发微服务">
- <meta name="twitter:description" content="用JAX-RS开发微服务">
+ <meta name="twitter:title" content="Development Style-JAX-RS">
+ <meta name="twitter:description" content="Development Style-JAX-RS">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="用JAX-RS开发微服务">
- <meta itemprop="description" content="用JAX-RS开发微服务">
+ <meta itemprop="headline" content="Development Style-JAX-RS">
+ <meta itemprop="description" content="Development Style-JAX-RS">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">用JAX-RS开发微服务
+ <h1 class="page__title" itemprop="headline">Development Style-JAX-RS
</h1>
</header>
@@ -564,25 +564,23 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#开发示例" id="markdown-toc-开发示例">开发示例</a></li>
- <li><a href="#涉及api" id="markdown-toc-涉及api">涉及API</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#development-example" id="markdown-toc-development-example">Development Example</a></li>
+ <li><a href="#involved-apis" id="markdown-toc-involved-apis">Involved APIs</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>ServiceComb支持开发者使用JAX-RS注解，使用JAX-RS模式开发服务。</p>
+<p>ServiceComb supports developers in developing services in JAX-RS mode by using JAX-RS.</p>
-<h2 id="开发示例">开发示例</h2>
+<h2 id="development-example">Development Example</h2>
<ul>
<li>
- <p><strong>步骤 1</strong> 定义服务接口。</p>
-
- <p>根据开发之前定义好的契约，编写Java业务接口，代码如下：</p>
+ <p><strong>Steps 1</strong> Define a service API. Compile the Java API definition based on the API definition defined before development. The code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">interface</span> <span class="nc">Hello</span> <span class="o">{</span>
<span class="err"> </span><span class="n">String</span> <span class="nf">sayHi</span><span class="o">(</span><span class="n">String</span> <span class="n">name</span><span class="o">);</span>
@@ -592,14 +590,12 @@
</div>
<blockquote>
- <p><strong>说明</strong>：
- 该接口的位置需要与契约中x-java-interface所指定的路径一致。</p>
+ <p><strong>NOTE</strong>：
+The location of the API must be the same as the path specified by x-java-interface in the API definition.</p>
</blockquote>
</li>
<li>
- <p><strong>步骤 2</strong> 实现服务。</p>
-
- <p>使用JAX-RS注解开发业务代码，Hello的服务实现如下：</p>
+ <p><strong>Step 2</strong> Implement the service. JAX-RS is used to describe the development of service code. The implementation of the Hello service is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">javax.ws.rs.POST</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">javax.ws.rs.Path</span><span class="o">;</span>
@@ -629,9 +625,7 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 发布服务。</p>
-
- <p>在服务的实现类上打上注解<code class="highlighter-rouge">@RestSchema</code>，指定schemaId，表示该实现作为当前微服务的一个schema发布，代码如下：</p>
+ <p><strong>Step 3</strong> Release the service. Add <code class="highlighter-rouge">@RestSchema</code> as the annotation of the service implementation class and specify schemaID, which indicates that the implementation is released as a schema of the current microservice. The code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">io.servicecomb.provider.rest.common.RestSchema</span><span class="o">;</span>
<span class="c1">// other code omitted</span>
@@ -642,7 +636,7 @@
</code></pre>
</div>
- <p>然后在resources/META-INF/spring目录下创建jaxrsHello.bean.xml文件，配置spring进行服务扫描的base-package，文件内容如下：</p>
+ <p>Create the jaxrsHello.bean.xml file in the resources/META-INF/spring directory and configure base-package that performs scanning. The content of the file is as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
<span class="nt"><beans</span> <span class="na">xmlns=</span><span class="s">" http://www.springframework.org/schema/beans "</span> <span class="na">xmlns:xsi=</span><span class="s">" http://www.w3.org/2001/XMLSchema-instance "</span>
@@ -650,7 +644,7 @@
<span class="na">xmlns:cse=</span><span class="s">" http://www.huawei.com/schema/paas/cse/rpc "</span>
<span class="na">xmlns:context=</span><span class="s">" http://www.springframework.org/schema/context "</span>
<span class="na">xsi:schemaLocation=</span><span class="s">" http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.huawei.com/schema/paas/cse/rpc classpath:META-INF/spring/spring-paas-cse-rpc.xsd"</span><span class="nt">></span>
-
+
<span class="nt"><context:component-scan</span> <span class="na">base-package=</span><span class="s">"io.servicecomb.samples.jaxrs.provider"</span><span class="nt">/></span>
<span class="nt"></beans></span>
</code></pre>
@@ -658,28 +652,28 @@
</li>
</ul>
-<h2 id="涉及api">涉及API</h2>
+<h2 id="involved-apis">Involved APIs</h2>
-<p>JAX-RS开发模式当前支持如下注解，所有注解的使用方法参考<a href="https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html">JAX-RS官方文档</a>。</p>
+<p>Currently, the JAX-RS development mode supports the following annotation. For details about how to use JAX-RS, see <a href="https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html">JAX-RS official documentation</a>。</p>
<table>
<thead>
<tr>
- <th style="text-align: left">注解</th>
- <th style="text-align: left">位置</th>
- <th style="text-align: left">描述</th>
+ <th style="text-align: left">Remarks</th>
+ <th style="text-align: left">Location</th>
+ <th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left">javax.ws.rs.Path</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">URL路径</td>
+ <td style="text-align: left">URL path</td>
</tr>
<tr>
<td style="text-align: left">javax.ws.rs.Produces</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">方法支持的编解码能力</td>
+ <td style="text-align: left">Coding/decoding capability supported by the method</td>
</tr>
<tr>
<td style="text-align: left">javax.ws.rs.DELETE</td>
@@ -704,31 +698,31 @@
<tr>
<td style="text-align: left">javax.ws.rs.QueryParam</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从query string中获取参数</td>
+ <td style="text-align: left">Obtain parameters from query string</td>
</tr>
<tr>
<td style="text-align: left">javax.ws.rs.PathParam</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从path中获取参数，必须在path中定义该参数</td>
+ <td style="text-align: left">Obtain parameters from path, This parameter must be defined in path.</td>
</tr>
<tr>
<td style="text-align: left">javax.ws.rs.HeaderParam</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从header中获取参数</td>
+ <td style="text-align: left">Obtain parameters from header.</td>
</tr>
<tr>
<td style="text-align: left">javax.ws.rs.CookieParam</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从cookie中获取参数</td>
+ <td style="text-align: left">Obtain parameters from cookie.</td>
</tr>
</tbody>
</table>
<blockquote>
- <p><strong>说明</strong>：</p>
+ <p><strong>NOTE</strong>：</p>
<ul>
- <li>当方法参数没有注解，且不为HttpServletRequest类型参数时，默认为body类型参数，一个方法只支持最多一个body类型参数。</li>
- <li>打在参数上面的注解建议显式定义出value值，否则将直接使用契约中的参数名，例如应该使用<code class="highlighter-rouge">@QueryParam\("name"\) String name</code>，而不是<code class="highlighter-rouge">@QueryParam String name</code>。</li>
+ <li>When the method parameter has no annotation and is not an HttpServletRequest parameter, the parameter is of the body type by default. One method supports a maximum of one body-typed parameter.</li>
+ <li>You are advised to explicitly define the value of the parameter. Otherwise, the parameter name in the API definition is used, such as <code class="highlighter-rouge">@QueryParam\("name"\) String name</code> String name instead of <code class="highlighter-rouge">@QueryParam String name</code>.</li>
</ul>
</blockquote>
diff --git a/content/users/develop-with-rest-template/index.html b/content/users/develop-with-rest-template/index.html
index d6ed15d..63bb814 100644
--- a/content/users/develop-with-rest-template/index.html
+++ b/content/users/develop-with-rest-template/index.html
@@ -19,12 +19,12 @@
-<title>使用Rest Template方式开发 - Apache incubator ServiceComb</title>
+<title>Develop with Rest Template - Apache incubator ServiceComb</title>
-<meta name="description" content="使用Rest Template方式开发">
+<meta name="description" content="Develop with Rest Template">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用Rest Template方式开发">
+<meta property="og:title" content="Develop with Rest Template">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/develop-with-rest-template/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用Rest Template方式开发">
+ <meta property="og:description" content="Develop with Rest Template">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用Rest Template方式开发">
- <meta name="twitter:description" content="使用Rest Template方式开发">
+ <meta name="twitter:title" content="Develop with Rest Template">
+ <meta name="twitter:description" content="Develop with Rest Template">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用Rest Template方式开发">
- <meta itemprop="description" content="使用Rest Template方式开发">
+ <meta itemprop="headline" content="Develop with Rest Template">
+ <meta itemprop="description" content="Develop with Rest Template">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用Rest Template方式开发
+ <h1 class="page__title" itemprop="headline">Develop with Rest Template
</h1>
</header>
@@ -564,25 +564,25 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p> Rest Template是Spring提供的RESTful访问接口，ServiceComb提供该接口的实现类用于服务的调用。</p>
+<p> Rest Template is a RESTful API provide by the Spring framework. ServiceComb provides the API for service calling</p>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p> 用户使用ServiceComb提供的Rest Template实例，可以使用自定义的URL进行服务调用，而不用关心服务的具体地址。</p>
+<p> You can call microservices using your customized URL and the RestTemplate instance provided by ServiceComb regardless of the specific address of the service.</p>
-<h2 id="示例代码">示例代码</h2>
+<h2 id="sample-code">Sample Code</h2>
-<p> Rest Template实例通过调用<code class="highlighter-rouge">RestTemplateBuilder.create()</code>方法获取，再使用该实例通过自定义的URL进行服务调用，代码如下：</p>
+<p> Obtain RestTemplate by calling <code class="highlighter-rouge">RestTemplateBuilder.create()</code>. Then, use the instance and the customized URL to call microservices. The code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kn">import</span> <span class="nn">org.springframework.stereotype.Component</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">org.springframework.web.client.RestTemplate</span><span class="o">;</span>
@@ -617,10 +617,10 @@
</div>
<blockquote>
- <p>说明：</p>
+ <p>NOTE:</p>
<ul>
- <li>URL格式为：<code class="highlighter-rouge">cse://microserviceName/path?querystring</code>。以<a href="/users/develop-with-springmvc/">用SpringMVC开发微服务</a>中定义的服务提供者为例，其微服务名称是<code class="highlighter-rouge">springmvc</code>，basePath是<code class="highlighter-rouge">/springmvchello</code>，那么URL中的microserviceName是<code class="highlighter-rouge">springmvc</code>，请求sayhi时的path是<code class="highlighter-rouge">springmvchello/sayhi</code>，所以示例代码中请求sayhi的URL是<code class="highlighter-rouge">cse://s [...]
- <li>使用这种URL格式，ServiceComb框架会在内部进行服务发现、熔断容错等处理并最终将请求发送到服务提供者。</li>
+ <li>The URL must be in format of ServiceComb: <code class="highlighter-rouge">cse://microserviceName/path?querystring</code>. Use the provider defined in <a href="/users/develop-with-springmvc/">Develop Microservice with SpringMVC</a> as an example. The microservice name is <code class="highlighter-rouge">springmvc</code>, and its base path is <code class="highlighter-rouge">/springmvchello</code>, so you should set microserviceName in the URL to <code class="highlighter-rouge">spri [...]
+ <li>During use of this URL format, the ServiceComb framework will perform internal microservice descovery, fallbreak, and fault tolerance and send the requests to the microservice providers.</li>
</ul>
</blockquote>
diff --git a/content/users/develop-with-rpc/index.html b/content/users/develop-with-rpc/index.html
index cf47bfa..18fc1d0 100644
--- a/content/users/develop-with-rpc/index.html
+++ b/content/users/develop-with-rpc/index.html
@@ -19,12 +19,12 @@
-<title>使用RPC方式开发 - Apache incubator ServiceComb</title>
+<title>Develop with RPC - Apache incubator ServiceComb</title>
-<meta name="description" content="使用RPC方式开发">
+<meta name="description" content="Develop with RPC">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用RPC方式开发">
+<meta property="og:title" content="Develop with RPC">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/develop-with-rpc/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用RPC方式开发">
+ <meta property="og:description" content="Develop with RPC">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用RPC方式开发">
- <meta name="twitter:description" content="使用RPC方式开发">
+ <meta name="twitter:title" content="Develop with RPC">
+ <meta name="twitter:description" content="Develop with RPC">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用RPC方式开发">
- <meta itemprop="description" content="使用RPC方式开发">
+ <meta itemprop="headline" content="Develop with RPC">
+ <meta itemprop="description" content="Develop with RPC">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用RPC方式开发
+ <h1 class="page__title" itemprop="headline">Develop with RPC
</h1>
</header>
@@ -564,20 +564,20 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>RPC开发方式允许用户通过在服务接口上标注注解来生成服务提供者代理，从而进行服务的调用。</p>
+<p>The RPC development mode allows you to add annotations on the microservice APIs to generate the service provider agent. In this case, you can call microservices.</p>
-<h2 id="示例代码">示例代码</h2>
+<h2 id="sample-code">Sample Code</h2>
-<p>只需要声明一个服务接口类型的成员，并且使用<code class="highlighter-rouge">@RpcReference</code>标注该成员，声明依赖的微服务及schemaId，即可进行服务调用，示例代码如下：</p>
+<p>To call a microservice, you only need to declare a member of a service API type and add the @RpcReference annotation for the member, the microservice that depends on the declaration, and the schemaID. The sample code is as follows.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kn">import</span> <span class="nn">org.springframework.stereotype.Component</span><span class="o">;</span>
@@ -608,7 +608,7 @@
</code></pre>
</div>
-<p>在以上代码中，服务消费者已经取得了服务提供者的服务接口<code class="highlighter-rouge">Hello</code>，并在代码中声明一个<code class="highlighter-rouge">Hello</code>类型的成员。通过在<code class="highlighter-rouge">hello</code>上使用<code class="highlighter-rouge">@RPCReference</code>注解指明微服务名称和schemaId，ServiceComb框架可以在程序启动时从服务中心获取到对应的服务提供者实例信息，并且生成一个代理注入到hello中，用户可以像调用本地类一样调用远程服务。</p>
+<p>In the preceding code, the microservice consumers have obtained the microservice API Hello of the microservice provider and declared a member of the Hello type. The annotation <code class="highlighter-rouge">@RPCReference</code> on <code class="highlighter-rouge">Hello</code> specifies the microservice name and schemaId, The ServiceComb framework can obtain information about isntances from a certain provider during program startup and generate an agent to insert to Hello. This allows [...]
</section>
diff --git a/content/users/develop-with-springmvc/index.html b/content/users/develop-with-springmvc/index.html
index efe0c11..384bf3e 100644
--- a/content/users/develop-with-springmvc/index.html
+++ b/content/users/develop-with-springmvc/index.html
@@ -19,12 +19,12 @@
-<title>用SpringMVC开发微服务 - Apache incubator ServiceComb</title>
+<title>Development Style-Spring MVC - Apache incubator ServiceComb</title>
-<meta name="description" content="用SpringMVC开发微服务">
+<meta name="description" content="Development Style-Spring MVC">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="用SpringMVC开发微服务">
+<meta property="og:title" content="Development Style-Spring MVC">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/develop-with-springmvc/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="用SpringMVC开发微服务">
+ <meta property="og:description" content="Development Style-Spring MVC">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="用SpringMVC开发微服务">
- <meta name="twitter:description" content="用SpringMVC开发微服务">
+ <meta name="twitter:title" content="Development Style-Spring MVC">
+ <meta name="twitter:description" content="Development Style-Spring MVC">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="用SpringMVC开发微服务">
- <meta itemprop="description" content="用SpringMVC开发微服务">
+ <meta itemprop="headline" content="Development Style-Spring MVC">
+ <meta itemprop="description" content="Development Style-Spring MVC">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">用SpringMVC开发微服务
+ <h1 class="page__title" itemprop="headline">Development Style-Spring MVC
</h1>
</header>
@@ -564,25 +564,23 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#开发示例" id="markdown-toc-开发示例">开发示例</a></li>
- <li><a href="#涉及api" id="markdown-toc-涉及api">涉及API</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#development-example" id="markdown-toc-development-example">Development Example</a></li>
+ <li><a href="#involved-apis" id="markdown-toc-involved-apis">Involved APIs</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>ServiceComb支持SpringMVC注解，允许使用SpringMVC风格开发微服务。</p>
+<p>ServiceComb supports Spring MVC remark and allows you to develop microservices in Spring MVC mode.</p>
-<h2 id="开发示例">开发示例</h2>
+<h2 id="development-example">Development Example</h2>
<ul>
<li>
- <p><strong>步骤 1</strong> 定义服务接口。</p>
-
- <p>根据开发之前定义好的契约，编写Java业务接口，代码如下：</p>
+ <p><strong>Step 1</strong> Define a service API., Compile the Java API definition based on the API definition defined before development. The code is as follow:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">interface</span> <span class="nc">Hello</span> <span class="o">{</span>
<span class="n">String</span> <span class="nf">sayHi</span><span class="o">(</span><span class="n">String</span> <span class="n">name</span><span class="o">);</span>
@@ -591,12 +589,10 @@
</code></pre>
</div>
- <p>该接口的位置需要与契约中x-java-interface所指定的路径一致。</p>
+ <p>The location of the API must be the same as the path specified by x-java-interface in the API definition.</p>
</li>
<li>
- <p><strong>步骤 2</strong> 实现服务。</p>
-
- <p>使用Spring MVC注解开发业务代码，Hello的服务实现如下：</p>
+ <p><strong>Step 2</strong> Implement the services. Spring MVC is used to describe the development of service code. The implementation of the Hello service is as follow:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">javax.ws.rs.core.MediaType</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">org.springframework.web.bind.annotation.RequestBody</span><span class="o">;</span>
@@ -605,7 +601,7 @@
<span class="kn">import</span> <span class="nn">org.springframework.web.bind.annotation.RequestParam</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.servicecomb.samples.common.schema.Hello</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.servicecomb.samples.common.schema.models.Person</span><span class="o">;</span>
-
+
<span class="nd">@RequestMapping</span><span class="o">(</span><span class="n">path</span> <span class="o">=</span> <span class="s">"/springmvchello"</span><span class="o">,</span> <span class="n">produces</span> <span class="o">=</span> <span class="n">MediaType</span><span class="o">.</span><span class="na">APPLICATION_JSON</span><span class="o">)</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">SpringmvcHelloImpl</span> <span class="kd">implements</span> <span class="n">Hello</span> <span class="o">{</span>
<span class="nd">@Override</span>
@@ -624,9 +620,7 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 发布服务</p>
-
- <p>在服务的实现类上打上注解@RestSchema，指定schemaId，表示该实现作为当前微服务的一个schema发布，代码如下：</p>
+ <p><strong>Step 3</strong> Release the service. Add @RestSchema as the annotation of the service implementation class and specify schemaId, which indicates that the implementation is released as a schema of the current microservice. The code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">io.servicecomb.provider.rest.common.RestSchema</span><span class="o">;</span>
<span class="c1">// other code omitted</span>
@@ -637,16 +631,16 @@
</code></pre>
</div>
- <p>然后在<code class="highlighter-rouge">resources/META-INF/spring</code>目录下创建<code class="highlighter-rouge">springmvcHello.bean.xml</code>文件，命名规则为<code class="highlighter-rouge">\*.bean.xml</code>，配置spring进行服务扫描的base-package，文件内容如下：</p>
+ <p>Create the <code class="highlighter-rouge">springmvcHello.bean.xml</code> file(the file name format is *.bean.xml) in the <code class="highlighter-rouge">resources/META-INF/spring</code> directory and configure base-package that performs scanning. The content of the file is as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
-
+
<span class="nt"><beans</span> <span class="na">xmlns=</span><span class="s">"http://www.springframework.org/schema/beans"</span>
<span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
<span class="na">xmlns:context=</span><span class="s">"http://www.springframework.org/schema/context"</span>
<span class="na">xsi:schemaLocation=</span><span class="s">"http://www.springframework.org/schema/beans</span> <span class="err">classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd</span>
<span class="err">http://www.springframework.org/schema/context</span> <span class="err">http://www.springframework.org/schema/context/spring-context-3.0.xsd"</span><span class="nt">></span>
-
+
<span class="nt"><context:component-scan</span> <span class="na">base-package=</span><span class="s">"io.servicecomb.samples.springmvc.provider"</span><span class="nt">/></span>
<span class="nt"></beans></span>
</code></pre>
@@ -654,68 +648,68 @@
</li>
</ul>
-<h2 id="涉及api">涉及API</h2>
+<h2 id="involved-apis">Involved APIs</h2>
-<p>Spring MVC开发模式当前支持org.springframework.web.bind.annotation包下的如下注解，所有注解的使用方法参考<a href="https://docs.spring.io/spring/docs/current/spring-framework-reference/html/mvc.html">Spring MVC官方文档</a>。</p>
+<p>Currently, the Spring MVC development mode supports the following annotations in the org.springframework.web.bind.annotation package. For details about how to use the annotations, see <a href="https://docs.spring.io/spring/docs/current/spring-framework-reference/html/mvc.html">Spring MVC official documentation</a>。</p>
<table>
<thead>
<tr>
- <th style="text-align: left">注解</th>
- <th style="text-align: left">位置</th>
- <th style="text-align: left">描述</th>
+ <th style="text-align: left">Remarks</th>
+ <th style="text-align: left">Location</th>
+ <th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left">RequestMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/method/produces三种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path, method or produces is allowed. By default, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">GetMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/produces两种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path or produces is allowed. By default, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">PutMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/produces两种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path or produces is allowed, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">PostMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/produces两种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path or produces is allowed, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">DeleteMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/produces两种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path or produces is allowed, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">PatchMapping</td>
<td style="text-align: left">schema/operation</td>
- <td style="text-align: left">支持标注path/produces两种数据，operation默认继承schema上的produces</td>
+ <td style="text-align: left">Data of path or produces is allowed, an operation inherits produces from a schema.</td>
</tr>
<tr>
<td style="text-align: left">PathVariable</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从path中获取参数</td>
+ <td style="text-align: left">Obtain parameters from path.</td>
</tr>
<tr>
<td style="text-align: left">RequestParam</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从query中获取参数</td>
+ <td style="text-align: left">Obtain parameters from query.</td>
</tr>
<tr>
<td style="text-align: left">RequestHeader</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从header中获取参数</td>
+ <td style="text-align: left">Obtain parameters from header.</td>
</tr>
<tr>
<td style="text-align: left">RequestBody</td>
<td style="text-align: left">parameter</td>
- <td style="text-align: left">从body中获取参数，每个operation只能有一个body参数</td>
+ <td style="text-align: left">Obtain parameters from body. Each operation can have only one body parameter.</td>
</tr>
</tbody>
</table>
diff --git a/content/users/develop-with-transparent-rpc/index.html b/content/users/develop-with-transparent-rpc/index.html
index f29b189..ee48a7c 100644
--- a/content/users/develop-with-transparent-rpc/index.html
+++ b/content/users/develop-with-transparent-rpc/index.html
@@ -19,12 +19,12 @@
-<title>用透明RPC开发微服务 - Apache incubator ServiceComb</title>
+<title>Development Style-Transparent RPC - Apache incubator ServiceComb</title>
-<meta name="description" content="用透明RPC开发微服务">
+<meta name="description" content="Development Style-RPC">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="用透明RPC开发微服务">
+<meta property="og:title" content="Development Style-Transparent RPC">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/develop-with-transparent-rpc/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="用透明RPC开发微服务">
+ <meta property="og:description" content="Development Style-RPC">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="用透明RPC开发微服务">
- <meta name="twitter:description" content="用透明RPC开发微服务">
+ <meta name="twitter:title" content="Development Style-Transparent RPC">
+ <meta name="twitter:description" content="Development Style-RPC">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="用透明RPC开发微服务">
- <meta itemprop="description" content="用透明RPC开发微服务">
+ <meta itemprop="headline" content="Development Style-Transparent RPC">
+ <meta itemprop="description" content="Development Style-RPC">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">用透明RPC开发微服务
+ <h1 class="page__title" itemprop="headline">Development Style-Transparent RPC
</h1>
</header>
@@ -564,27 +564,25 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#开发示例" id="markdown-toc-开发示例">开发示例</a></li>
- <li><a href="#通过注解配置的开发方式" id="markdown-toc-通过注解配置的开发方式">通过注解配置的开发方式</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#development-example" id="markdown-toc-development-example">Development Example</a></li>
+ <li><a href="#the-develop-method-by-configure-remarks" id="markdown-toc-the-develop-method-by-configure-remarks">The Develop Method by Configure Remarks</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>透明RPC开发模式是一种基于接口和接口实现的开发模式，服务的开发者不需要使用Spring MVC和JAX-RS注解。</p>
+<p>The transparent remote procedure call(RPC) development mode is a development mode based on API and API implementation. The service developer does not need to use the description of Spring MVC and JAX-RS.</p>
-<h2 id="开发示例">开发示例</h2>
+<h2 id="development-example">Development Example</h2>
-<p>透明RPC开发模式支持Spring xml配置和注解配置两种服务发布方式，通过Spring xml配置的方式如下：</p>
+<p>The transparent RPC development mode supports two service release mode: Spring XML configuration and annotation configuration. The Spring XML configuration mode is as follows:</p>
<ul>
<li>
- <p><strong>步骤 1</strong> 定义服务接口。</p>
-
- <p>根据开发之前定义好的契约，编写Java业务接口，代码如下：</p>
+ <p><strong>Step 1</strong> Define a service API. Compile the Java API definition based on the API definition defined before development. The code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">interface</span> <span class="nc">Hello</span> <span class="o">{</span>
<span class="n">String</span> <span class="nf">sayHi</span><span class="o">(</span><span class="n">String</span> <span class="n">name</span><span class="o">);</span>
@@ -594,14 +592,12 @@
</div>
<blockquote>
- <p><strong>说明</strong>：
-该接口的位置需要与契约中x-java-interface所指定的路径一致。</p>
+ <p><strong>NOTE</strong>：
+The location of the API must be the same as the path specified by x-java-interface in the API definition.</p>
</blockquote>
</li>
<li>
- <p><strong>步骤 2</strong> 实现服务</p>
-
- <p>Hello的服务实现如下：</p>
+ <p><strong>Step 2</strong> implement the service. The implementation of the Hello service is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">io.servicecomb.samples.common.schema.Hello</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.servicecomb.samples.common.schema.models.Person</span><span class="o">;</span>
@@ -621,9 +617,7 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 发布服务</p>
-
- <p>在resources/META-INF/spring目录下创建pojoHello.bean.xml文件，在文件中声明schema，文件内容如下：</p>
+ <p><strong>Step 3</strong> Release the service. Create the pojoHello.bean.xml file in the resources/META-INF/spring directory and declare the schema in the file. The content of the file is as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
<span class="nt"><beans</span> <span class="na">xmlns=</span><span class="s">" http://www.springframework.org/schema/beans "</span> <span class="na">xmlns:xsi=</span><span class="s">" http://www.w3.org/2001/XMLSchema-instance "</span>
@@ -631,26 +625,30 @@
<span class="na">xmlns:cse=</span><span class="s">" http://www.huawei.com/schema/paas/cse/rpc "</span>
<span class="na">xmlns:context=</span><span class="s">" http://www.springframework.org/schema/context "</span>
<span class="na">xsi:schemaLocation=</span><span class="s">" http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.huawei.com/schema/paas/cse/rpc classpath:META-INF/spring/spring-paas-cse-rpc.xsd"</span><span class="nt">></span>
-
+
<span class="nt"><cse:rpc-schema</span> <span class="na">schema-id=</span><span class="s">"pojoHello"</span> <span class="na">implementation=</span><span class="s">"io.servicecomb.samples.pojo.provider.PojoHelloImpl"</span><span class="nt">/></span>
<span class="nt"></beans></span>
</code></pre>
</div>
<blockquote>
- <p><strong>说明</strong>：
-每一个服务接口都需要定义一个schema声明。</p>
+ <p><strong>NOTE</strong>：
+A schema statement must be defined for each service API.</p>
</blockquote>
</li>
</ul>
-<h2 id="通过注解配置的开发方式">通过注解配置的开发方式</h2>
+<h2 id="the-develop-method-by-configure-remarks">The Develop Method by Configure Remarks</h2>
<ol>
- <li>定义服务接口，与使用Spring xml的方式相同。</li>
- <li>实现服务，与使用Spring xml的方式相同。</li>
<li>
- <p>发布服务。在接口Hello的实现类上使用@RpcSchema注解定义schema，代码如下：</p>
+ <p>Define a service API, which is the same as the Spring XML mode.</p>
+ </li>
+ <li>
+ <p>Implement the service in the same way as using Spring XML.</p>
+ </li>
+ <li>
+ <p>Release the service. @RpcSchema is used to define schema during the API Hello implementation. The code is as followss:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kn">import</span> <span class="nn">io.servicecomb.provider.pojo.RpcSchema</span><span class="o">;</span>
<span class="c1">// other code omitted</span>
@@ -661,7 +659,7 @@
</code></pre>
</div>
- <p>在resources/META-INF/spring目录下的pojoHello.bean.xml文件中，配置Spring进行服务扫描的base-package，文件内容如下：</p>
+ <p>In the pojoHello.bean.xml file of resources/META-INF/spring directory, configure base-package that performs scanning. The content of the file is as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
<span class="nt"><beans</span> <span class="na">xmlns=</span><span class="s">" http://www.springframework.org/schema/beans "</span> <span class="na">xmlns:xsi=</span><span class="s">" http://www.w3.org/2001/XMLSchema-instance "</span>
@@ -669,7 +667,7 @@
<span class="na">xmlns:cse=</span><span class="s">" http://www.huawei.com/schema/paas/cse/rpc "</span>
<span class="na">xmlns:context=</span><span class="s">" http://www.springframework.org/schema/context "</span>
<span class="na">xsi:schemaLocation=</span><span class="s">" http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.huawei.com/schema/paas/cse/rpc classpath:META-INF/spring/spring-paas-cse-rpc.xsd"</span><span class="nt">></span>
-
+
<span class="nt"><context:component-scan</span> <span class="na">base-package=</span><span class="s">"io.servicecomb.samples.pojo.provider"</span><span class="nt">/></span>
<span class="nt"></beans></span>
</code></pre>
@@ -678,8 +676,8 @@
</ol>
<blockquote>
- <p><strong>说明</strong>：
-与Spring MVC开发模式和JAX-RS开发模式不同的是，透明RPC开发模式使用的注解是<code class="highlighter-rouge">@RpcSchema</code>而非<code class="highlighter-rouge">@RestSchema</code>。</p>
+ <p><strong>NOTE</strong>:
+Different from the Spring MVC and JAX-RS development modes, the transparent RPC development mode used <code class="highlighter-rouge">@RpcSchema</code> instead of <code class="highlighter-rouge">@RestSchema</code>.</p>
</blockquote>
diff --git a/content/users/distributed-tracing/index.html b/content/users/distributed-tracing/index.html
index 0bc6aad..e83336b 100644
--- a/content/users/distributed-tracing/index.html
+++ b/content/users/distributed-tracing/index.html
@@ -19,12 +19,12 @@
-<title>分布式调用链追踪 - Apache incubator ServiceComb</title>
+<title>Distributed Tracing - Apache incubator ServiceComb</title>
-<meta name="description" content="分布式调用链追踪">
+<meta name="description" content="Distributed Tracing">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="分布式调用链追踪">
+<meta property="og:title" content="Distributed Tracing">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/distributed-tracing/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="分布式调用链追踪">
+ <meta property="og:description" content="Distributed Tracing">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="分布式调用链追踪">
- <meta name="twitter:description" content="分布式调用链追踪">
+ <meta name="twitter:title" content="Distributed Tracing">
+ <meta name="twitter:description" content="Distributed Tracing">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="分布式调用链追踪">
- <meta itemprop="description" content="分布式调用链追踪">
+ <meta itemprop="headline" content="Distributed Tracing">
+ <meta itemprop="description" content="Distributed Tracing">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">分布式调用链追踪
+ <h1 class="page__title" itemprop="headline">Distributed Tracing
</h1>
</header>
@@ -564,11 +564,11 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
<li><a href="#zipkin" id="markdown-toc-zipkin">Zipkin</a></li>
- <li><a href="#使用步骤" id="markdown-toc-使用步骤">使用步骤:</a> <ul>
- <li><a href="#添加依赖" id="markdown-toc-添加依赖">添加依赖</a></li>
- <li><a href="#配置追踪处理和数据收集" id="markdown-toc-配置追踪处理和数据收集">配置追踪处理和数据收集</a></li>
+ <li><a href="#procedure" id="markdown-toc-procedure">Procedure</a> <ul>
+ <li><a href="#add-dependency" id="markdown-toc-add-dependency">Add dependency</a></li>
+ <li><a href="#configure-tracing-and-data-collection" id="markdown-toc-configure-tracing-and-data-collection">Configure tracing and data collection</a></li>
</ul>
</li>
</ul>
@@ -576,29 +576,29 @@
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>微服务架构解决了很多单体应用带来的问题，但同时也需要我们付出额外的代价。由于网络的不稳定性带来的请求处理延迟就是代价之一。</p>
+<p>The microservice architecture addresses many problems of single applications but has several drawbacks, for example, network instability may lead to latency.</p>
-<p>在单体应用中，所有模块都在同一个进程中运行，所以并没有模块间互通的问题。但微服务架构中，服务间通过网络沟通，因此我们不得不处理和网络有关的 问题，例如：延迟、超时、网络分区等。</p>
+<p>In a single application, all the modules are running in the same process without interworking. However, in the microservice architecture, services are communicated through network, and we have to address network problems, such as latency, timeout, and segmentation.</p>
-<p>另外，随着业务的扩展服务增多，我们很难洞察数据如何在蛛网般复杂的服务结构中流转。我们如何才能有效的监控网络延迟并且可视化服务中的数据流转呢？</p>
+<p>As services expand, we can hardly monitor how data is transferred in the complex service architecture. How do we efficiently monitor network latency and visualize the data flows of services?</p>
-<p><strong>分布式调用链追踪</strong>用于有效地监控微服务的网络延时并可视化微服务中的数据流转。</p>
+<p>The distributed tracing system efficiently monitor network latency of the microservice and visualize data flow during the service.</p>
<h2 id="zipkin">Zipkin</h2>
<blockquote>
- <p><a href="http://zipkin.io/">Zipkin</a>是一个分布式调用链追踪系统。 它能帮助用户收集时序数据用以定位微服务中的延迟问题，它同时管理追踪数据的收集 和查询。Zipkin 的设计基于 Google <a href="http://research.google.com/pubs/pub36356.html">Dapper paper</a>。</p>
+ <p><a href="http://zipkin.io/">Zipkin</a> is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. Zipkin’s design is based on Google <a href="http://research.google.com/pubs/pub36356.html">Dapper paper</a>。</p>
</blockquote>
-<p>ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用户只需要专注实现其业务需求。</p>
+<p>ServiceComb integrates the automatic call tracing function provided by Zipkin, so that users can focus on service demands.</p>
-<h2 id="使用步骤">使用步骤:</h2>
+<h2 id="procedure">Procedure</h2>
-<h3 id="添加依赖">添加依赖</h3>
+<h3 id="add-dependency">Add dependency</h3>
-<p>基于 ServiceComb Java Chassis 的微服务只需要添加如下依赖到 pom.xml：</p>
+<p>For microservice based on ServiceComb Java Chassis, add the following content to pom.xml</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -607,7 +607,7 @@
</code></pre>
</div>
-<p>如果微服务是基于 Spring Cloud + Zuul 的 API 网关，例如 workshop demo 中的 manager service ，我们还需要加入如下的额外依赖：</p>
+<p>If the microservice is based on the API of Spring Cloud Zuul, such as the manager service of the workshop demo, add the following dependency:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -616,9 +616,9 @@
</code></pre>
</div>
-<h3 id="配置追踪处理和数据收集">配置追踪处理和数据收集</h3>
+<h3 id="configure-tracing-and-data-collection">Configure tracing and data collection</h3>
-<p>在microservice.yaml文件中设置追踪处理器和数据收集服务地址</p>
+<p>Set addresses for the tracing processor and data collection in the microservice.yaml file.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>
@@ -634,9 +634,9 @@
</code></pre>
</div>
-<p>就这样，在加了两个配置项，没改动一行代码的情况下，我们启动了基于 Zipkin 和 Java chassis 的分布式调用链追踪的功能。</p>
+<p>In this way, we enable the Zipkin-and-Java-based chassis distributed tracing system without changing any code.</p>
-<p class="notice--warning"><strong>注意：</strong> 如果项目中的其他依赖也引入了 zipkin （例如 Spring Cloud），可能导致 zipkin 版本不一致而运行出错，这时需要在项目 pom 中声明 zipkin 版本。</p>
+<p class="notice--warning"><strong>NOTE:</strong> If other dependencies introduce the Zipkin system, such as Spring Cloud, running errors may occur due to version inconsistency. In this case, you need to specify the Zipkin version in the pom project.</p>
</section>
diff --git a/content/users/edging-service/nginx/index.html b/content/users/edging-service/nginx/index.html
index 772b632..c7d5ca0 100644
--- a/content/users/edging-service/nginx/index.html
+++ b/content/users/edging-service/nginx/index.html
@@ -19,12 +19,12 @@
-<title>使用confd和Nginx做边缘服务 - Apache incubator ServiceComb</title>
+<title>Using Confd and Nginx for Edge Service - Apache incubator ServiceComb</title>
-<meta name="description" content="使用confd和Nginx做边缘服务">
+<meta name="description" content="Using Confd and Nginx for Edge Service">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用confd和Nginx做边缘服务">
+<meta property="og:title" content="Using Confd and Nginx for Edge Service">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/edging-service/nginx/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用confd和Nginx做边缘服务">
+ <meta property="og:description" content="Using Confd and Nginx for Edge Service">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用confd和Nginx做边缘服务">
- <meta name="twitter:description" content="使用confd和Nginx做边缘服务">
+ <meta name="twitter:title" content="Using Confd and Nginx for Edge Service">
+ <meta name="twitter:description" content="Using Confd and Nginx for Edge Service">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用confd和Nginx做边缘服务">
- <meta itemprop="description" content="使用confd和Nginx做边缘服务">
+ <meta itemprop="headline" content="Using Confd and Nginx for Edge Service">
+ <meta itemprop="description" content="Using Confd and Nginx for Edge Service">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用confd和Nginx做边缘服务
+ <h1 class="page__title" itemprop="headline">Using Confd and Nginx for Edge Service
</h1>
</header>
@@ -564,15 +564,15 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a> <ul>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a> <ul>
<li><a href="#confd" id="markdown-toc-confd"><strong>confd</strong></a></li>
<li><a href="#nginx" id="markdown-toc-nginx"><strong>Nginx</strong></a></li>
</ul>
</li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#对接服务中心" id="markdown-toc-对接服务中心">对接服务中心</a> <ul>
- <li><a href="#方法一http调用" id="markdown-toc-方法一http调用"><strong>方法一：http调用</strong></a></li>
- <li><a href="#方法二使用servicecomb开源代码接口" id="markdown-toc-方法二使用servicecomb开源代码接口"><strong>方法二：使用servicecomb开源代码接口</strong></a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#interconnecting-with-the-service-center" id="markdown-toc-interconnecting-with-the-service-center">Interconnecting with the Service Center</a> <ul>
+ <li><a href="#method-1-http-call" id="markdown-toc-method-1-http-call"><strong>Method 1: HTTP call</strong></a></li>
+ <li><a href="#method-2-using-the-open-source-code-api" id="markdown-toc-method-2-using-the-open-source-code-api"><strong>Method 2: Using the open-source code API</strong></a></li>
</ul>
</li>
</ul>
@@ -580,61 +580,61 @@
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
<h3 id="confd"><strong>confd</strong></h3>
-<p>confd是一个轻量级的配置管理工具，源码地址：<a href="https://github.com/kelseyhightower/confd">https://github.com/kelseyhightower/confd</a>，它可以将配置信息存储在etcd、consul、dynamodb、redis以及zookeeper等。confd定期会从这些存储节点pull最新的配置，然后重新加载服务，完成配置文件的更新。</p>
+<p>confd is a lightweight configuration management tool. The source code address is: https://github.com/kelseyhightower/confd](https://github.com/kelseyhightower/confd), It can store configuration information in etcd, consul, dynamodb, redis, and zookeeper. confd regularly pulls the latest configuration from storage nodes and then reloads services to complete updating the configuration file.</p>
<h3 id="nginx"><strong>Nginx</strong></h3>
-<p>Nginx (engine x)是一个高性能的HTTP和反向代理服务器，具有负载均衡的功能。详情请参考<a href="http://www.nginx.cn/doc/">http://www.nginx.cn/doc/</a>。本小节介绍的服务主要使用到的是Nginx的http代理功能。</p>
+<p>Nginx (engine x) is a high-performance HTTP and reverse proxy server that has the load balancing function. For details, see <a href="http://www.nginx.cn/doc/">http://www.nginx.cn/doc/</a>. This secton describes the HTTP proxy function of Nginx.</p>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>本小节介绍的技术是使用nginx+confd做边缘服务，同时可以对接ServiceComb微服务框架中的服务中心，从服务中心中拉去服务信息通过confd动态更新nginx的配置。</p>
+<p>This section describes how to use Nginx and confd to serve as edge services. Also, you can connect Nginx and confd to service center in the Java Chassis microservice framework and dynamically update configuration of Nginx using confd.</p>
-<p>使用nginx+confd动态反向代理的实现步骤可参考文章<a href="http://www.cnblogs.com/Anker/p/6112022.html">http://www.cnblogs.com/Anker/p/6112022.html</a>，本节主要介绍confd如何对接ServiceComb框架的服务中心。</p>
+<p>For details about how to use the dynamic reverse proxy of Nginx and confd, see <a href="http://www.cnblogs.com/Anker/p/6112022.html">http://www.cnblogs.com/Anker/p/6112022.html</a>, This section describes how to interconnect Confd with the service center of the Java Chassis framework.</p>
-<h2 id="对接服务中心">对接服务中心</h2>
+<h2 id="interconnecting-with-the-service-center">Interconnecting with the Service Center</h2>
-<p>本节介绍的技术核心在于如何使得confd获取到服务中心的服务信息，服务中心开放了以下接口供外部调用：</p>
+<p>This section describes how to enable confd to obtain service information from the service center. The service center provides the following APIs for external calls:</p>
-<h3 id="方法一http调用"><strong>方法一：http调用</strong></h3>
+<h3 id="method-1-http-call"><strong>Method 1: HTTP call</strong></h3>
-<p>服务中心开放http接口均需要添加租户头部信息：“X-Tenant-Name:tenantName”，tenameName为租户名，默认为default，例如”X-Tenant-Name:default”。</p>
+<p>The tenant header information of “X-Tenant-Name:tenantName” needs to be added to the HTTP API in the Service Center. tenameName is the tenant name. The default value is default, such as X-Tenant-Name:default.</p>
<ul>
<li>
- <p>检查服务中心健康状态</p>
+ <p>Check the health status of the service center</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err"> GET 127.0.0.1:9980/health
</span></code></pre>
</div>
</li>
<li>
- <p>获取所有微服务信息</p>
+ <p>Obtain all microservice information</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err"> GET 127.0.0.1:9980/registry/v3/microservices
</span></code></pre>
</div>
</li>
<li>
- <p>获取指定id的微服务信息</p>
+ <p>Obtain the microservice information with a specified ID</p>
</li>
</ul>
<blockquote>
<ol>
<li>
- <p>首先根据微服务信息获取serviceId</p>
+ <p>Obtain the service ID based on the microservice information</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err">GET 127.0.0.1:9980/registry/v3/existence?type=microservice&appId={appId}&serviceName={serviceName}&version={version}
</span></code></pre>
</div>
</li>
<li>
- <p>根据上述接口返回的serviceId获取微服务完整信息</p>
+ <p>Obtain complete microservice information based on the service ID returned by API</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err">GET 127.0.0.1:9980/registry/v3/microservices/{serviceId}
</span></code></pre>
@@ -645,58 +645,62 @@
<ul>
<li>
- <p>获取指定微服务的所有实例信息</p>
+ <p>Obtain all instance information from specified microservice</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err"> GET 127.0.0.1:9980/registry/v3/microservices/{serviceId}/instances
</span></code></pre>
</div>
- <p>需要在header中添加：”X-ConsumerId:{serviceId}”。</p>
+ <p>Add the following information to the header file:</p>
+
+ <p>“X-ConsumerId:{serviceId}”</p>
</li>
<li>
- <p>查找微服务实例信息</p>
+ <p>Searching microservice instance information</p>
<div class="language-http highlighter-rouge"><pre class="highlight"><code><span class="err"> GET 127.0.0.1:9980/registry/v3/instances?appId={appId}&serviceName={serviceName}&version={version}
</span></code></pre>
</div>
- <p>需要在header中添加”X-ConsumerId:{serviceId}”。</p>
+ <p>Add the following information to the header file:</p>
+
+ <p>“X-ConsumerId:{serviceId}”</p>
</li>
</ul>
-<p>注意：在实际开发中请访问实际的service-center访问地址，并将上述url中{}的变量替换成具体值，http返回的数据均为json格式</p>
+<p>NOTE: The preceding service center address is provides as example only. Set the variables enclosed in curly brackets ({}) as needed. The data returned via HTTP is in JSON format.</p>
-<h3 id="方法二使用servicecomb开源代码接口"><strong>方法二：使用servicecomb开源代码接口</strong></h3>
+<h3 id="method-2-using-the-open-source-code-api"><strong>Method 2: Using the open-source code API</strong></h3>
-<p>在开发微服务应用，只需要调用servicecomb框架代码中的工具类RegistryUtil.java中提供的接口，即可获取服务中心的信息，接口描述如下：</p>
+<p>During the development of the microservice application, you only need to call the API provided by the tool RegistryUtil.java in the ServiceComb framework code to obtain the information in the Service Center. The API is described as follows:</p>
<ul>
- <li>获取所有微服务信息
+ <li>Obtain all microservice information
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="n">List</span><span class="o"><</span><span class="n">Microservice</span><span class="o">></span> <span class="nf">getAllMicroservices</span><span class="o">();</span>
</code></pre>
</div>
</li>
- <li>获取微服务唯一标识
+ <li>Obtain the unique ID of the microservice.
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="n">String</span> <span class="nf">getMicroserviceId</span><span class="o">(</span><span class="n">String</span> <span class="n">appId</span><span class="o">,</span> <span class="n">String</span> <span class="n">microserviceName</span><span class="o">,</span> <span class="n">String</span> <span class="n">versionRule</span><span class="o">);</span>
</code></pre>
</div>
</li>
- <li>根据微服务唯一标识查询微服务静态信息
+ <li>Query the microservice static information based on the unique ID of the microservice.
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="n">Microservice</span> <span class="nf">getMicroservice</span><span class="o">(</span><span class="n">String</span> <span class="n">microserviceId</span><span class="o">);</span>
</code></pre>
</div>
</li>
- <li>根据多个微服务唯一标识查询所有微服务实例信息
+ <li>Query all the microservice instance information based on the unique IDs of the microservices.
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="n">List</span><span class="o"><</span><span class="n">MicroserviceInstance</span><span class="o">></span> <span class="nf">getMicroserviceInstance</span><span class="o">(</span><span class="n">String</span> <span class="n">consumerId</span><span class="o">,</span> <span class="n">String</span> <span class="n">providerId</span><span class="o">);</span>
</code></pre>
</div>
</li>
- <li>按照app+interface+version查询实例endpoints信息
+ <li>Query the instance end points information based on the application, interface, and version.
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="n">List</span><span class="o"><</span><span class="n">MicroserviceInstance</span><span class="o">></span> <span class="nf">findServiceInstance</span><span class="o">(</span><span class="n">String</span> <span class="n">consumerId</span><span class="o">,</span> <span class="n">String</span> <span class="n">appId</span><span class="o">,</span> <span class="n">String</span> <span class="n">serv [...]
</code></pre>
</div>
</li>
</ul>
-<p>通过上述http接口可获取到服务中心的微服务和其实例的信息，从而通过confd动态更新nginx配置。</p>
+<p>You can obtain information about the microservice and instance of the Service Center using the HTTP API to dynamically update the Nginx configuration using confd.</p>
</section>
diff --git a/content/users/edging-service/zuul/index.html b/content/users/edging-service/zuul/index.html
index a99f8d5..22dd975 100644
--- a/content/users/edging-service/zuul/index.html
+++ b/content/users/edging-service/zuul/index.html
@@ -19,12 +19,12 @@
-<title>使用Zuul做边缘服务 - Apache incubator ServiceComb</title>
+<title>Using Zuul for Edge Service - Apache incubator ServiceComb</title>
-<meta name="description" content="使用Zuul做边缘服务">
+<meta name="description" content="Using Zuul for Edge Service">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用Zuul做边缘服务">
+<meta property="og:title" content="Using Zuul for Edge Service">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/edging-service/zuul/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用Zuul做边缘服务">
+ <meta property="og:description" content="Using Zuul for Edge Service">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用Zuul做边缘服务">
- <meta name="twitter:description" content="使用Zuul做边缘服务">
+ <meta name="twitter:title" content="Using Zuul for Edge Service">
+ <meta name="twitter:description" content="Using Zuul for Edge Service">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用Zuul做边缘服务">
- <meta itemprop="description" content="使用Zuul做边缘服务">
+ <meta itemprop="headline" content="Using Zuul for Edge Service">
+ <meta itemprop="description" content="Using Zuul for Edge Service">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用Zuul做边缘服务
+ <h1 class="page__title" itemprop="headline">Using Zuul for Edge Service
</h1>
</header>
@@ -564,60 +564,60 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a> <ul>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a> <ul>
<li><a href="#api-gateway" id="markdown-toc-api-gateway">API Gateway：</a></li>
<li><a href="#zuul" id="markdown-toc-zuul">Zuul</a></li>
</ul>
</li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
- <li><a href="#启动zuul-proxy" id="markdown-toc-启动zuul-proxy">启动Zuul Proxy</a></li>
- <li><a href="#使用zuul-proxy" id="markdown-toc-使用zuul-proxy">使用Zuul Proxy</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#precautions" id="markdown-toc-precautions">Precautions</a></li>
+ <li><a href="#starting-zuul-proxy" id="markdown-toc-starting-zuul-proxy">Starting Zuul Proxy</a></li>
+ <li><a href="#using-zuul-proxy" id="markdown-toc-using-zuul-proxy">Using Zuul Proxy</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
<h3 id="api-gateway">API Gateway：</h3>
-<p>API Gateway是一个服务器，也可以说是进入系统的唯一节点。API Gateway封装内部系统的架构，并且提供API给各个客户端。</p>
+<p>An API Gateway is a server and the only node through which you can access the system. API Gateway encapsulates the internal system architecture and provides APIs for clients.</p>
<h3 id="zuul">Zuul</h3>
-<p>Zuul是Netflix的基于JVM的路由器和服务器端负载均衡器，可以使用Zuul进行以下操作：</p>
+<p>Zuul is a JVM-based router and server load balancer of Netflix. You can use Zuul to perform the following operations:</p>
<ul>
- <li>认证</li>
- <li>洞察</li>
- <li>压力测试</li>
- <li>金丝雀测试</li>
- <li>动态路由</li>
- <li>服务迁移</li>
- <li>负载脱落</li>
- <li>安全</li>
- <li>静态相响应处理</li>
- <li>主动/被动流量管理</li>
+ <li>Certification</li>
+ <li>Insight</li>
+ <li>Stress test</li>
+ <li>Canary test</li>
+ <li>Dynamic route</li>
+ <li>Service migration</li>
+ <li>Offload</li>
+ <li>Security</li>
+ <li>Static phase response processing</li>
+ <li>Proactive/passive traffic management</li>
</ul>
-<p>本小节主要介绍在SpringBoot应用中使用Zuul做API Gateway。关于Zuul的详细功能介绍请参考文档<a href="https://springcloud.cc/spring-cloud-dalston.html#_router_and_filter_zuul">路由器和过滤器：Zuul</a>。</p>
+<p>This section describes how to use Zuul as the API Gateway in the Spring Boot application. For details about Zuul, see <a href="https://springcloud.cc/spring-cloud-dalston.html#_router_and_filter_zuul">Router and Filter: Zuul</a>.</p>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>Zuul做API Gateway，即建立一个Zuul Proxy应用，在该Proxy应用中统一定义所有的微服务访问入口，通过使用不同的前缀(stripped)来区分各个微服务。本小节通过建立一个ZuulProxy SpringBoot应用来演示Zuul的API Gateway功能。</p>
+<p>Use Zuul as the API Gateway, that is, establishes a Zuul Proxy application. In this proxy application, a unified access of all the microservices is defined, and each microservice is distinguished using a prefix (stipped). This section establishes the ZuulProxy Spring Boot application to demonstrate the API Gateway function.</p>
-<h2 id="注意事项">注意事项</h2>
+<h2 id="precautions">Precautions</h2>
-<p>本小节介绍的ZuulProxy和ZuulServer等demo都是基于SpringBoot和ServiceComb框架的应用，具体请参考<a href="/users/use-servicecomb-in-spring-boot/">在ServiceComb框架中集成SpringBoot框架</a>。</p>
+<p>In this section, demos, such as ZuulProxy and ZuulServer, are based on Spring Boot and the Java Chassis framework. For detals, see <a href="/users/use-servicecomb-in-spring-boot/">Integrating Spring Boot into Java Chassis</a>.</p>
-<h2 id="启动zuul-proxy">启动Zuul Proxy</h2>
+<h2 id="starting-zuul-proxy">Starting Zuul Proxy</h2>
-<p>本节介绍如何启动一个zuul proxy应用作为API Gateway。步骤如下：</p>
+<p>This topic describes how to start a ZuulProxy application as the API Gateway. Perform the following steps:</p>
<ul>
<li>
- <p><strong>步骤 1</strong>在pom文件中添加依赖：</p>
+ <p><strong>Step 1</strong> Add the following dependency to the POM file.</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.springframework.cloud<span class="nt"></groupId></span>
@@ -638,11 +638,11 @@
</div>
</li>
<li>
- <p><strong>步骤 2</strong>在SpringBoot主类添加注解：</p>
+ <p><strong>Step 2</strong> Add annotations to the main Spring Boot category:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="nd">@SpringBootApplication</span>
<span class="nd">@EnableServiceComb</span>
- <span class="nd">@EnableZuulProxy</span><span class="c1">//新增注解</span>
+ <span class="nd">@EnableZuulProxy</span><span class="c1">//new Annotation</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">ZuulMain</span><span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">Exception</span><span class="o">{</span>
<span class="n">SpringApplication</span><span class="o">.</span><span class="na">run</span><span class="o">(</span><span class="n">ZuulMain</span><span class="o">.</span><span class="na">class</span><span class="o">,</span> <span class="n">args</span><span class="o">);</span>
@@ -652,80 +652,80 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong>在application.yml文件中定义路由策略：</p>
+ <p><strong>Step 3</strong> Define a routing policy in the application.yaml file</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">server</span><span class="pi">:</span>
- <span class="s">port</span><span class="pi">:</span> <span class="s">8754</span> <span class="c1">#api gateway服务端口</span>
+ <span class="s">port</span><span class="pi">:</span> <span class="s">8754</span> <span class="c1">#api gateway service port number</span>
<span class="s">zuul</span><span class="pi">:</span>
- <span class="s">routes</span><span class="pi">:</span> <span class="c1">#路由策略</span>
- <span class="s">discoveryServer</span><span class="pi">:</span> <span class="s">/myServer/**</span> <span class="c1">#路由规则</span>
+ <span class="s">routes</span><span class="pi">:</span> <span class="c1">#Routing policy</span>
+ <span class="s">discoveryServer</span><span class="pi">:</span> <span class="s">/myServer/**</span> <span class="c1">#Routing rule</span>
</code></pre>
</div>
- <p>上述的配置项可以根据实际开发环境进行配置。关于zuul.routers的路由策略的详细定义规则，请参考官方文献：<a href="https://springcloud.cc/spring-cloud-dalston.html#_router_and_filter_zuul">路由器和过滤器：Zuul</a>，可更细粒度地对路由进行控制。</p>
+ <p>The configuration item in ted indicates that the configuration can be performed based on the actual development environment. For details about the rules for defining routing policies of zuul.routers, see：<a href="https://springcloud.cc/spring-cloud-dalston.html#_router_and_filter_zuul">Router and Fillter: Zuul</a> to control routes in a finer granularity.</p>
</li>
<li>
- <p><strong>步骤 4</strong>在microservice.yaml定义微服务属性：</p>
+ <p><strong>Step 4</strong> Define the microservice attributes in the microservice.yaml fiel.</p>
- <div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">discoverytest</span> <span class="c1">#服务ID</span>
+ <div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">discoverytest</span> <span class="c1">#Service ID</span>
<span class="s">service_description</span><span class="pi">:</span>
- <span class="s">name</span><span class="pi">:</span> <span class="s">discoveryGateway</span> <span class="c1">#服务名称</span>
- <span class="s">version</span><span class="pi">:</span> <span class="s">0.0.2</span> <span class="c1">#服务版本号</span>
+ <span class="s">name</span><span class="pi">:</span> <span class="s">discoveryGateway</span> <span class="c1">#Service Name</span>
+ <span class="s">version</span><span class="pi">:</span> <span class="s">0.0.2</span> <span class="c1">#Service Version</span>
<span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
<span class="s">registry</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#服务注册中心地址</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#Service Center registration</span>
<span class="s">rest</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">0.0.0.0:8082</span> <span class="c1">#微服务端口，可不写</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">0.0.0.0:8082</span> <span class="c1">#(Optional) microservice port number</span>
</code></pre>
</div>
</li>
</ul>
-<p>本小节所有服务使用的都是本地的服务中心，具体的服务中心启动流程请参考<a href="/users/setup-environment/#运行service-center">启动本地服务中心</a>。</p>
+<p>All the services used in this section use the local service center. For details, see <a href="/users/setup-environment/#运行service-center">Starting the Local Service Center</a>。</p>
<ul>
- <li><strong>步骤 5 </strong>运行ZuulMain 应用</li>
+ <li><strong>Step 5 </strong> Run ZuulMain Application</li>
</ul>
-<h2 id="使用zuul-proxy">使用Zuul Proxy</h2>
+<h2 id="using-zuul-proxy">Using Zuul Proxy</h2>
-<p>在使用zuul做的API Gateway前，首先要启动在zuul.routers中定义的微服务提供者。</p>
+<p>Before using the API Gateway provided by Zuul, start the microservice provider defined in zuul.routers.</p>
-<p>开发服务提供者，开发流程请参考<a href="/users/service-definition/">开发服务提供者</a>。在微服务microservice.yaml文件中需注意以下两点：</p>
+<p>Pay attention to the following points in the microservice.yaml file:</p>
<ul>
<li>
- <p>APPLICATION_ID需要于zuul proxy中定义的保持一致。</p>
+ <p>APPLICATION_ID must be the same as that defined in ZuulProxy.</p>
</li>
<li>
- <p>service_description.name需要于zuul.routers中相对应。</p>
+ <p>The value of service_description.name must be the same as that of zuul.routers</p>
</li>
</ul>
-<p>示例如下：</p>
+<p>An example is as follows:</p>
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">discoverytest</span> <span class="c1">#与zuul proxy一致</span>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">discoverytest</span> <span class="c1">#same as ZuulProxy</span>
<span class="s">service_description</span><span class="pi">:</span>
- <span class="s">name</span><span class="pi">:</span> <span class="s">discoveryServer</span> <span class="c1">#服务名称，与zuul.routers对应</span>
+ <span class="s">name</span><span class="pi">:</span> <span class="s">discoveryServer</span> <span class="c1">#Service name, which corresponds to that of zuul.routers</span>
<span class="s">version</span><span class="pi">:</span> <span class="s">0.0.2</span>
<span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
<span class="s">registry</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#服务注册中心地址</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#Service Center registration</span>
<span class="s">rest</span><span class="pi">:</span>
<span class="s">address</span><span class="pi">:</span> <span class="s">0.0.0.0:8080</span>
</code></pre>
</div>
-<p>API Gateway的访问入口为：<a href="http://127.0.0.1:8754">http://127.0.0.1:8754</a>，所有在zuul.routers中定义的服务都可通过这个访问入口进行代理访问，访问规则如下：</p>
+<p>The portal for API Gateway is: <a href="http://127.0.0.1:8754">http://127.0.0.1:8754</a>. All services defined in zuul.routers can be accessed through this portal. The access rule are as follows:</p>
<p>http://127.0.0.1:8754/myServer/***](http://127.0.0.1:8754/myServer/***)</p>
-<p>这表示，Http调用<a href="http://127.0.0.1:8754/myServer/***">http://127.0.0.1:8754/myServer/***</a>，会转到discoveryServer服务（例如：”/myServer/101”跳转到discoveryServer 服务下的”/101”）</p>
+<p>This indicates that HTTP calls [http://127.0.0.1:8754/myServer/*** to switch to the discoveryServer service. For example: “/myServer/101” switches to “/101” of discoveryServer service.</p>
<blockquote>
- <p>如果在服务中心同时存在多个discoveryServer服务(版本不同),zuul默认采用Ribbon策略对请求进行转发。</p>
+ <p>If multiple discoveryServer service (in different versions) exist in the Service Center, Zuul uses the Ribbon policy to transfer the request by default.</p>
</blockquote>
diff --git a/content/users/index.html b/content/users/index.html
index 0bf1725..4aa4f6b 100644
--- a/content/users/index.html
+++ b/content/users/index.html
@@ -19,12 +19,12 @@
-<title>Java Chassis系统架构 - Apache incubator ServiceComb</title>
+<title>Java Chassis Architecture - Apache incubator ServiceComb</title>
-<meta name="description" content="Java Chassis系统架构">
+<meta name="description" content="Java Chassis Architecture">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="Java Chassis系统架构">
+<meta property="og:title" content="Java Chassis Architecture">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="Java Chassis系统架构">
+ <meta property="og:description" content="Java Chassis Architecture">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="Java Chassis系统架构">
- <meta name="twitter:description" content="Java Chassis系统架构">
+ <meta name="twitter:title" content="Java Chassis Architecture">
+ <meta name="twitter:description" content="Java Chassis Architecture">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="Java Chassis系统架构">
- <meta itemprop="description" content="Java Chassis系统架构">
+ <meta itemprop="headline" content="Java Chassis Architecture">
+ <meta itemprop="description" content="Java Chassis Architecture">
<meta itemprop="dateModified" content="June 14, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">Java Chassis系统架构
+ <h1 class="page__title" itemprop="headline">Java Chassis Architecture
</h1>
</header>
@@ -564,92 +564,92 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#框架概述" id="markdown-toc-框架概述">框架概述</a></li>
- <li><a href="#主要设计意图" id="markdown-toc-主要设计意图">主要设计意图</a></li>
- <li><a href="#模块说明" id="markdown-toc-模块说明">模块说明</a></li>
+ <li><a href="#basic-framework" id="markdown-toc-basic-framework">Basic Framework</a></li>
+ <li><a href="#purpose" id="markdown-toc-purpose">Purpose</a></li>
+ <li><a href="#modules" id="markdown-toc-modules">Modules</a></li>
</ul>
</nav>
</aside>
-<h2 id="框架概述">框架概述</h2>
-<p><img src="/assets/images/servicecomb-models.png" alt="ServiceComb Model" class="align-center" /></p>
+<h2 id="basic-framework">Basic Framework</h2>
+<p><img src="/assets/images/servicecomb_mode_en.png" alt="ServiceComb Model" class="align-center" /></p>
-<h2 id="主要设计意图">主要设计意图</h2>
+<h2 id="purpose">Purpose</h2>
-<p>1.编程模型和通信模型分离，不同的编程模型可以灵活组合不同的通信模型。应用开发者在开发阶段只关注接口开发，部署阶段灵活切换通信方式；支持legacy系统的切换，legacy系统只需要修改服务发布的配置文件（或者annotation），而不需要修改代码。</p>
+<p>1.To decouple the programming and communication models, so that a programming model can be combined with any communication models as needed. Application developers only need to focus on APIs during development and can flexibly switch communication models during deployment. Services can also be switched over to a legacy system. The developers simply need to modify the configuration file(or annotation) released by the service.</p>
-<p>现阶段支持SpringMVC、JAX-RS和透明RPC三种开发方式。</p>
+<p>Currently, applications can be developed in Spring MVC, JAX-RS, or transparent RPC mode.</p>
-<p>2.内建API-first支持。通过契约规范化微服务开发，实现跨语言的通信，并支持配套的软件工具链（契约生成代码、代码生成契约等）开发，构建完整的开发生态。</p>
+<p>2.To introduce the code-first approach. This allows cross-language communication through API definition-based microservice development and supports the development of software tool chains(such as code generated based on API definitions and API definitions generated based on code) to build a complete development ecosystem.</p>
-<p>3.定义了常用的微服务运行模型，将微服务从发现到交互过程中的各种容错手段都封装起来。该运行模型支持自定义和扩展。</p>
+<p>3.To define common microservice running model, encapsulating fault tolerance methods of microservices used from discovery to interaction, The running model can be customized or extended.</p>
-<h2 id="模块说明">模块说明</h2>
+<h2 id="modules">Modules</h2>
<table>
<thead>
<tr>
- <th style="text-align: left">类型</th>
+ <th style="text-align: left">Type</th>
<th style="text-align: left">artifact id</th>
- <th style="text-align: left">是否可选</th>
- <th style="text-align: left">功能说明</th>
+ <th style="text-align: left">Available or NOT</th>
+ <th style="text-align: left">Function</th>
</tr>
</thead>
<tbody>
<tr>
- <td style="text-align: left">编程模型</td>
+ <td style="text-align: left">Programming model</td>
<td style="text-align: left">provider-pojo</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">提供RPC开发模式</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides the RPC development mode.</td>
</tr>
<tr>
- <td style="text-align: left">编程模型</td>
+ <td style="text-align: left">Programming model</td>
<td style="text-align: left">provider-jaxrs</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">提供JAX RS开发模式</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides the JAX-RS development mode.</td>
</tr>
<tr>
- <td style="text-align: left">编程模型</td>
+ <td style="text-align: left">Programming model</td>
<td style="text-align: left">provider-springmvc</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">提供Spring MVC开发模式</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides the Spring MVC development mode.</td>
</tr>
<tr>
- <td style="text-align: left">通信模型</td>
+ <td style="text-align: left">Communication on model</td>
<td style="text-align: left">transport-rest-vertx</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">运行于HTTP之上的开发框架，不依赖WEB容器，应用打包为可执行jar</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">A development framework running over HTTP, it does not depend on Web containers. Applications are packaged as executable .jar files.</td>
</tr>
<tr>
- <td style="text-align: left">通信模型</td>
+ <td style="text-align: left">Communication on model</td>
<td style="text-align: left">transport-rest-servlet</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">运行于WEB容器的开发框架，应用打包为war包</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">A development framework running on Web container. Applications are packaged as WAR files.</td>
</tr>
<tr>
- <td style="text-align: left">通信模型</td>
+ <td style="text-align: left">Communication on model</td>
<td style="text-align: left">transport-highway</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">提供高性能的私有通信协议，仅用于java之间互通。</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides high-performance private communication protocols for Java communication.</td>
</tr>
<tr>
- <td style="text-align: left">运行模型</td>
+ <td style="text-align: left">Running model</td>
<td style="text-align: left">handler-loadbalance</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">负载均衡模块。提供各种路由策略和配置方法。一般客户端使用。</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">A load balancing module that provides various routing policies and configurations. It is usually used for clients.</td>
</tr>
<tr>
- <td style="text-align: left">运行模型</td>
+ <td style="text-align: left">Running model</td>
<td style="text-align: left">handler-bizkeeper</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">和服务治理相关的功能，比如隔离、熔断、容错。</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides service governance functions, such as isolation, fallbreak, and fault tolerance.</td>
</tr>
<tr>
- <td style="text-align: left">运行模型</td>
+ <td style="text-align: left">Running model</td>
<td style="text-align: left">handler-tracing</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">调用链跟踪模块，对接监控系统，吐出打点数据。</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Provides the capability of developing and managing TCC transactions.</td>
</tr>
</tbody>
</table>
diff --git a/content/users/invoke-control/index.html b/content/users/invoke-control/index.html
index 28a3858..939c968 100644
--- a/content/users/invoke-control/index.html
+++ b/content/users/invoke-control/index.html
@@ -19,12 +19,12 @@
-<title>调用控制 - Apache incubator ServiceComb</title>
+<title>Invoke Control - Apache incubator ServiceComb</title>
-<meta name="description" content="调用控制">
+<meta name="description" content="Invoke Control">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="调用控制">
+<meta property="og:title" content="Invoke Control">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/invoke-control/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="调用控制">
+ <meta property="og:description" content="Invoke Control">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="调用控制">
- <meta name="twitter:description" content="调用控制">
+ <meta name="twitter:title" content="Invoke Control">
+ <meta name="twitter:description" content="Invoke Control">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="调用控制">
- <meta itemprop="description" content="调用控制">
+ <meta itemprop="headline" content="Invoke Control">
+ <meta itemprop="description" content="Invoke Control">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">调用控制
+ <h1 class="page__title" itemprop="headline">Invoke Control
</h1>
</header>
@@ -564,20 +564,20 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#实例级故障隔离" id="markdown-toc-实例级故障隔离">实例级故障隔离</a> <ul>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
+ <li><a href="#instance-level-fault-isolation" id="markdown-toc-instance-level-fault-isolation">Instance-Level Fault Isolation</a> <ul>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
</ul>
</li>
- <li><a href="#熔断策略" id="markdown-toc-熔断策略">熔断策略</a> <ul>
- <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
- <li><a href="#配置说明-1" id="markdown-toc-配置说明-1">配置说明</a></li>
+ <li><a href="#circuit-break-policy" id="markdown-toc-circuit-break-policy">Circuit Break Policy</a> <ul>
+ <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#configuration-1" id="markdown-toc-configuration-1">Configuration</a></li>
</ul>
</li>
- <li><a href="#限流策略" id="markdown-toc-限流策略">限流策略</a> <ul>
- <li><a href="#场景描述-2" id="markdown-toc-场景描述-2">场景描述</a></li>
- <li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
- <li><a href="#配置说明-2" id="markdown-toc-配置说明-2">配置说明</a></li>
+ <li><a href="#flow-control-policy" id="markdown-toc-flow-control-policy">Flow Control Policy</a> <ul>
+ <li><a href="#scenario-2" id="markdown-toc-scenario-2">Scenario</a></li>
+ <li><a href="#precaution" id="markdown-toc-precaution">Precaution</a></li>
+ <li><a href="#configuration-2" id="markdown-toc-configuration-2">Configuration</a></li>
</ul>
</li>
</ul>
@@ -585,25 +585,25 @@
</nav>
</aside>
-<h2 id="实例级故障隔离">实例级故障隔离</h2>
+<h2 id="instance-level-fault-isolation">Instance-Level Fault Isolation</h2>
-<h3 id="场景描述">场景描述</h3>
+<h3 id="scenario">Scenario</h3>
-<p>实例级故障隔离功能允许在微服务的部分实例调用失败时，停止向故障实例发送请求，从而达到隔离故障实例的功能。</p>
+<p>In the scenario where some instances fail to be called, the instance-level fault isolation function stops the ServiceComb framework from sending requests to the faulty instance.</p>
-<h3 id="配置说明">配置说明</h3>
+<h3 id="configuration">Configuration</h3>
-<p>实例级故障隔离功能集成在负载均衡功能中，负载均衡策略的配置见<a href="/users/service-configurations/#负载均衡策略">负载均衡策略</a>。负载均衡策略中，与实例级故障隔离相关的配置项见下表。</p>
+<p>This instance-level fault isolation function is integrated into the load balancing function. For configuration of the load balancing policy, see <a href="/users/service-configurations/#负载均衡策略">Service Configurations</a>. For parameters associated with instance-level fault isolation in the load balancing policy, see table below:</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remark</th>
</tr>
</thead>
<tbody>
@@ -611,58 +611,58 @@
<td style="text-align: left">cse.loadbalance.isolation.enabled</td>
<td style="text-align: left">false</td>
<td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否开启故障实例隔离功能</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable faulty instance isolation.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.enableRequestThreshold</td>
<td style="text-align: left">20</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">当实例的调用总次数达到该值时开始进入隔离逻辑门槛</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the threshold number of instance calls. If this value is reached, isolation is enabled.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.errorThresholdPercentage</td>
<td style="text-align: left">20</td>
- <td style="text-align: left">Integer，区间为(0,100]</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">实例故障隔离错误百分比</td>
+ <td style="text-align: left">Integer, (0,100]</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the error percentage. Instance fault isolation is enabled when the set value is reached.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.singleTestTime</td>
<td style="text-align: left">10000</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">故障实例单点测试时间</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the duration of a faulty instance test on a single node.</td>
<td style="text-align: left"> </td>
</tr>
</tbody>
</table>
-<h2 id="熔断策略">熔断策略</h2>
-<h3 id="场景描述-1">场景描述</h3>
+<h2 id="circuit-break-policy">Circuit Break Policy</h2>
+<h3 id="scenario-1">Scenario</h3>
-<p>熔断策略是对ServiceComb熔断功能的设置，用户通过配置熔断策略可以指定在何种条件下ServiceComb框架将终止发送请求。</p>
+<p>Circuit brake policy can configure ServiceComb fallback capability, you can configure conditions under which service will stop send request after circuit break policy configured.</p>
-<h3 id="配置说明-1">配置说明</h3>
+<h3 id="configuration-1">Configuration</h3>
-<p>熔断作为异常反应机制是降级策略的一部分，相关概念还有隔离和容错。三者的关系以及配置方式参见<a href="/users/service-configurations/#降级策略">降级策略</a>。</p>
+<p>Circuit break is part of fallback policy when a service request is abnormal, relevant concept such as isolation and fault tolerance please refer to <a href="/users/service-configurations/#降级策略">fallback policy</a>。</p>
-<h2 id="限流策略">限流策略</h2>
-<h3 id="场景描述-2">场景描述</h3>
+<h2 id="flow-control-policy">Flow Control Policy</h2>
+<h3 id="scenario-2">Scenario</h3>
-<p>用户在consumer端使用限流策略，可以限制发往指定微服务的请求的频率。</p>
+<p>You can limit the frequency of request send to specific microservice when flow control was enables in consumer service.</p>
-<h3 id="注意事项">注意事项</h3>
+<h3 id="precaution">Precaution</h3>
-<p>参考服务提供者处<a href="/users/service-configurations/#限流策略">限流策略注意事项</a>。</p>
+<p>See detail info at <a href="/users/service-configurations/#限流策略">Service Configurations</a>。</p>
-<h3 id="配置说明-2">配置说明</h3>
+<h3 id="configuration-2">Configuration</h3>
-<p>限流策略配置在microservice.yaml文件中，相关配置项见下表。要开启服务消费者端的限流策略，还需要在处理链中配置消费端限流handler，配置示例如下：</p>
+<p>Flow control policy configuration is in microservice.yaml file. You need to configure consumer handler in chain of service. See example blow:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>
@@ -672,17 +672,17 @@
</code></pre>
</div>
-<p>QPS流控配置项说明</p>
+<p>Configuration items of QPS:</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remark</th>
</tr>
</thead>
<tbody>
@@ -690,21 +690,22 @@
<td style="text-align: left">cse.flowcontrol.Consumer.qps.enabled</td>
<td style="text-align: left">true</td>
<td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否启用Consumer流控</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether consumers flowcontrol enables.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.flowcontrol.Consumer.qps.limit.[ServiceName].[Schema].[operation]</td>
<td style="text-align: left">2147483647 (max int)</td>
- <td style="text-align: left">(0,2147483647]，整形</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">每秒钟允许的请求数</td>
- <td style="text-align: left">支持microservice、schema、operation三个级别的配置</td>
+ <td style="text-align: left">(0,2147483647], Integer</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies number of requests per second.</td>
+ <td style="text-align: left">Support three level configurations: microservice、schema、operation.</td>
</tr>
</tbody>
</table>
+
</section>
diff --git a/content/users/local-develop-test/index.html b/content/users/local-develop-test/index.html
index e82c46a..1aa9eb2 100644
--- a/content/users/local-develop-test/index.html
+++ b/content/users/local-develop-test/index.html
@@ -19,12 +19,12 @@
-<title>本地开发与测试 - Apache incubator ServiceComb</title>
+<title>Local Development and Test - Apache incubator ServiceComb</title>
-<meta name="description" content="本地开发与测试">
+<meta name="description" content="Local Development and Test">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="本地开发与测试">
+<meta property="og:title" content="Local Development and Test">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/local-develop-test/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="本地开发与测试">
+ <meta property="og:description" content="Local Development and Test">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="本地开发与测试">
- <meta name="twitter:description" content="本地开发与测试">
+ <meta name="twitter:title" content="Local Development and Test">
+ <meta name="twitter:description" content="Local Development and Test">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="本地开发与测试">
- <meta itemprop="description" content="本地开发与测试">
+ <meta itemprop="headline" content="Local Development and Test">
+ <meta itemprop="description" content="Local Development and Test">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">本地开发与测试
+ <h1 class="page__title" itemprop="headline">Local Development and Test
</h1>
</header>
@@ -564,72 +564,72 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#启动本地服务中心" id="markdown-toc-启动本地服务中心">启动本地服务中心</a></li>
- <li><a href="#mock机制启动服务中心" id="markdown-toc-mock机制启动服务中心">Mock机制启动服务中心</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#starting-local-servicecenter" id="markdown-toc-starting-local-servicecenter">Starting Local ServiceCenter</a></li>
+ <li><a href="#enable-local-servicecenter-using-the-mock-mechanism" id="markdown-toc-enable-local-servicecenter-using-the-mock-mechanism">Enable Local ServiceCenter Using the Mock Mechanism</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>本小节介绍如何在开发者本地进行消费者/提供者应用的开发调试。开发服务提供者请参考<a href="/users/service-definition/">开发服务提供者章节</a>，开发服务消费者请参考<a href="/users/develop-with-rest-template/">开发服务消费者章节</a>。服务提供者和消费提供者均需要连接到在远程的服务中心，为了本地微服务的开发和调试，本小节介绍了两种搭建本地服务中心的方法进行本地微服务调试：</p>
+<p>This section describes how developers can locally develop and commission consumer and provider applications. Both service providers and consumers need to connect to the remote service center. Two methods of building Local ServiceCenter for local microservice commissioning are as follows:</p>
<ul>
<li>
- <p><a href="#启动本地服务中心">启动本地服务中心</a>。</p>
+ <p>Starting <a href="#启动本地服务中心">Local Service Center</a>。</p>
</li>
<li>
- <p><a href="#mock机制启动服务中心">通过local file模拟启动服务中心Mock机制</a>。</p>
+ <p>Starting Local Service Center <a href="#mock机制启动服务中心">Mock mechanism</a>。</p>
</li>
</ul>
-<p>服务中心是微服务框架中的重要组件，用于服务元数据以及服务实例元数据的管理和处理注册、发现。服务中心与微服务提供/消费者的逻辑关系下图所示：</p>
+<p>Service center is an important component in the microservice architecture, and is used for managing, registering, and detecting metadata and instance metadata. The logic relationship between the service center and microservice provider/consumer is as follows:</p>
-<p><img src="/assets/images/local_develop_test.png" alt="" /></p>
+<p><img src="/assets/images/local_develop_test_en.png" alt="" /></p>
-<h2 id="启动本地服务中心">启动本地服务中心</h2>
+<h2 id="starting-local-servicecenter">Starting Local ServiceCenter</h2>
<ul>
<li>
- <p><strong>步骤1</strong> 启动本地服务中心，可参考<a href="/users/setup-environment/#运行service-center">运行Service Center指南</a>。</p>
+ <p><strong>Step 1</strong> Starting local service center, please refer to <a href="/users/setup-environment/#运行service-center">Setup Environment</a>,</p>
</li>
<li>
- <p><strong>步骤 2</strong> 启动本地轻量服务中心后，在服务提供/消费者的microservice.yaml文件中配置ServerCenter的地址和端口，示例代码：</p>
+ <p><strong>Step 2</strong> After local service center is started, configure the service center address in the microservice.yaml file that stores SDK configuration information, as shown in the following example:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
<span class="s">registry</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#服务中心地址及端口</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#Indicates the service center address and port number</span>
</code></pre>
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 开发服务提供/消费者，启动微服务进行本地测试。</p>
+ <p><strong>Step 3</strong> Develop service providers and consumers enable the microservice for local tests.</p>
</li>
</ul>
-<h2 id="mock机制启动服务中心">Mock机制启动服务中心</h2>
+<h2 id="enable-local-servicecenter-using-the-mock-mechanism">Enable Local ServiceCenter Using the Mock Mechanism</h2>
<ul>
<li>
- <p><strong>步骤 1</strong>新建本地服务中心定义文件registry.yaml，内容如下：</p>
+ <p><strong>Step 1</strong> Create the registry.yaml file for Local ServiceCenter</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">springmvctest</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">id</span><span class="pi">:</span> <span class="s2">"</span><span class="s">001"</span>
<span class="s">version</span><span class="pi">:</span> <span class="s2">"</span><span class="s">1.0"</span>
- <span class="s">appid</span><span class="pi">:</span> <span class="s">myapp</span> <span class="c1">#调试的服务id</span>
+ <span class="s">appid</span><span class="pi">:</span> <span class="s">myapp</span> <span class="c1">#Commissioning service ID</span>
<span class="s">instances</span><span class="pi">:</span>
<span class="s">endpoints</span><span class="pi">:</span>
<span class="s">rest://127.0.0.1:8080</span>
</code></pre>
</div>
- <p>注意：mock机制需要自己准备契约，并且当前只支持在本地进行服务消费端(consumer)侧的调试，不支持服务提供者(provider)</p>
+ <p>NOTE: The mock mechanism needs an API definition on its own. Currently, only local commissioning for service consumers is supported.</p>
</li>
<li>
- <p><strong>步骤 2</strong>在服务消费者Main函数首末添加如下代码：</p>
+ <p><strong>Step 2</strong> Add the following code to the end of the Main function for service consumers.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">class</span> <span class="nc">xxxClient</span> <span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="o">{</span>
@@ -639,13 +639,12 @@
<span class="o">}</span>
</code></pre>
</div>
- </li>
-</ul>
-<p>setProperty第二个参数填写registry.yaml的系统绝对路径，注意区分在不同系统下使用对应的路径分隔符。</p>
-
-<ul>
- <li><strong>步骤 3</strong>开发服务消费者，启动微服务进行本地测试。</li>
+ <p>NOTE: Set the second parameter of setProperty to the absolute path of registry.yaml file in the disk. The path separator depends on the system it is in.</p>
+ </li>
+ <li>
+ <p><strong>Step 3</strong> Develop service consumers and enable the microservice for local tests.</p>
+ </li>
</ul>
diff --git a/content/users/run-mode/index.html b/content/users/run-mode/index.html
index 2f051a6..33a0be7 100644
--- a/content/users/run-mode/index.html
+++ b/content/users/run-mode/index.html
@@ -19,12 +19,12 @@
-<title>运行模式 - Apache incubator ServiceComb</title>
+<title>Running Mode - Apache incubator ServiceComb</title>
-<meta name="description" content="运行模式">
+<meta name="description" content="Running Mode">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="运行模式">
+<meta property="og:title" content="Running Mode">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/run-mode/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="运行模式">
+ <meta property="og:description" content="Running Mode">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="运行模式">
- <meta name="twitter:description" content="运行模式">
+ <meta name="twitter:title" content="Running Mode">
+ <meta name="twitter:description" content="Running Mode">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="运行模式">
- <meta itemprop="description" content="运行模式">
+ <meta itemprop="headline" content="Running Mode">
+ <meta itemprop="description" content="Running Mode">
<meta itemprop="dateModified" content="June 06, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">运行模式
+ <h1 class="page__title" itemprop="headline">Running Mode
</h1>
</header>
@@ -564,12 +564,12 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#standalone模式" id="markdown-toc-standalone模式">standalone模式</a> <ul>
- <li><a href="#操作步骤" id="markdown-toc-操作步骤">操作步骤</a></li>
+ <li><a href="#standalone-mode" id="markdown-toc-standalone-mode">Standalone Mode</a> <ul>
+ <li><a href="#procedure" id="markdown-toc-procedure">Procedure</a></li>
</ul>
</li>
- <li><a href="#web容器模式" id="markdown-toc-web容器模式">WEB容器模式</a> <ul>
- <li><a href="#开发示例" id="markdown-toc-开发示例">开发示例</a></li>
+ <li><a href="#web-container-mode" id="markdown-toc-web-container-mode">WEB Container Mode</a> <ul>
+ <li><a href="#development-example" id="markdown-toc-development-example">Development Example</a></li>
</ul>
</li>
</ul>
@@ -577,22 +577,26 @@
</nav>
</aside>
-<p>微服务框架当前提供了两种部署运行模式：standalone模式和web容器模式。推荐使用<strong>standalone模式</strong>拉起服务进程。</p>
-<h2 id="standalone模式">standalone模式</h2>
-<p>一个Standalone的容器，以简单的Main加载Spring启动，因为服务通常不需要Tomcat/JBoss等Web容器的特性，没必要用Web容器去加载服务。微框架提供了standalone部署运行模式，服务容器只是一个简单的Main方法，并加载一个简单的Spring容器，用于暴露服务。</p>
+<p>Currently, ServiceComb microservice framework support two kind of deploy mode: standalone mode and web container mode. You are advised to to use standalone to to start your services.</p>
+<h2 id="standalone-mode">Standalone Mode</h2>
+<p>A standalone container is loaded with a simple Main to start Spring. Because the service usually does not need the Web container feature, such as Tomcat/JBoss.</p>
-<h3 id="操作步骤">操作步骤</h3>
+<p>It is not necessary to unload services using the Web container. The microservice framework provides the standalone deployment mode.</p>
+
+<p>The service container is only a simple Main method, and a simple Spring container is loaded to expose services.</p>
+
+<h3 id="procedure">Procedure</h3>
<ul>
<li>
- <p><strong>步骤1</strong> 编写Main函数，初始化日志和加载服务配置，内容如下：</p>
+ <p><strong>Step 1</strong> Compile the Main function to initialize logs and load service configurations. The contents are as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">import</span> <span class="nn">io.servicecomb.foundation.common.utils.BeanUtils</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.servicecomb.foundation.common.utils.Log4jUtils</span><span class="o">;</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">MainServer</span> <span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>
- <span class="err"> </span><span class="n">Log4jUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="err">#日志初始化</span>
- <span class="err"> </span><span class="n">BeanUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="err">#</span> <span class="n">Spring</span> <span class="n">bean</span><span class="err">初始化</span>
+ <span class="err"> </span><span class="n">Log4jUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="err">#</span><span class="n">Log</span> <span class="n">initialization</span>
+ <span class="err"> </span><span class="n">BeanUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span> <span class="err">#</span> <span class="n">Spring</span> <span class="n">bean</span> <span class="n">initialization</span>
<span class="c1">// other codes omitted</span>
<span class="o">}</span>
<span class="o">}</span>
@@ -600,16 +604,18 @@
</div>
</li>
<li>
- <p><strong>步骤2</strong> 运行MainServer即可启动该微服务进程，向外暴露服务。</p>
+ <p><strong>Step 2</strong> Run MainServer to start process and expose services.</p>
- <p>注意：如果使用的是rest网络通道，需要将pom中的transport改为使用cse-transport-rest-vertx包。</p>
+ <p>NOTE: If the rest network is used, change transparent in the POM file to the cse-transport-rest-vertx package.</p>
</li>
</ul>
-<h2 id="web容器模式">WEB容器模式</h2>
-<p>如果需要将该微服务加载到web容器中启动运行时，需要新建一个servlet工程包装一下，该servlet工程，根据需要，可以不写或写少量的引导代码即可。</p>
+<h2 id="web-container-mode">WEB Container Mode</h2>
+<p>If you need to load the microservice to the web container, create a sersvlet project package. You do not need to write or write a small number of boot codes as needed.</p>
+
+<h3 id="development-example">Development Example</h3>
-<h3 id="开发示例">开发示例</h3>
+<p><strong>Step 1</strong> Create a servlet project and modify the web.xml file as follows:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><web-app></span>
<span class="nt"><context-param></span>
@@ -638,7 +644,7 @@
</div>
<ul>
- <li><strong>步骤2 修改pom文件</strong></li>
+ <li><strong>Step 2 Modify the POM file</strong></li>
</ul>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><dependencies></span>
@@ -653,11 +659,11 @@
</code></pre>
</div>
-<p><strong>注意事项:</strong></p>
+<p><strong>NOTICE:</strong></p>
<ol>
- <li>RESTful调用应该与web容器中其他静态资源调用（比如html、js等等）隔离开来，所以webroot后一段应该还有一层关键字，比如上面web.xml中举的例子（/test/rest）中的rest。</li>
- <li>以tomcat为例，默认每个war包都有不同的webroot，这个webroot需要是basePath的前缀，比如webroot为test，则该微服务所有的契约都必须以/test打头。</li>
- <li>当微服务加载在web容器中，并直接使用web容器开的http、https端口时，因为是使用的web容器的通信通道，所以需要满足web容器的规则。</li>
+ <li>The Restful call must be separated from other static resources (such as HTML and js) in the web container. The next segment of webroot should have a keyword, such as rest in this example (/test/rest) in web.xml</li>
+ <li>The Tomcat is used as an example. Each WAR package has unique webroot, which must be a basePath prefix. For example , if webroot is test, all the API definitions of the microservice must start with /test.</li>
+ <li>When the microservice is loaded to the web container and the HTTP and HTTPS ports are opened using the web container, which must meet requirements for the web container rules.</li>
</ol>
diff --git a/content/users/service-configurations/index.html b/content/users/service-configurations/index.html
index 89af7b5..f66b3ba 100644
--- a/content/users/service-configurations/index.html
+++ b/content/users/service-configurations/index.html
@@ -19,12 +19,12 @@
-<title>服务配置 - Apache incubator ServiceComb</title>
+<title>Service Configurations - Apache incubator ServiceComb</title>
-<meta name="description" content="服务配置">
+<meta name="description" content="Service Configurations">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="服务配置">
+<meta property="og:title" content="Service Configurations">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/service-configurations/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="服务配置">
+ <meta property="og:description" content="Service Configurations">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="服务配置">
- <meta name="twitter:description" content="服务配置">
+ <meta name="twitter:title" content="Service Configurations">
+ <meta name="twitter:description" content="Service Configurations">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="服务配置">
- <meta itemprop="description" content="服务配置">
+ <meta itemprop="headline" content="Service Configurations">
+ <meta itemprop="description" content="Service Configurations">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">服务配置
+ <h1 class="page__title" itemprop="headline">Service Configurations
</h1>
</header>
@@ -564,158 +564,158 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#负载均衡策略" id="markdown-toc-负载均衡策略">负载均衡策略</a> <ul>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#load-balancing-policy" id="markdown-toc-load-balancing-policy">Load Balancing Policy</a> <ul>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</li>
- <li><a href="#自定义路由策略" id="markdown-toc-自定义路由策略">自定义路由策略</a></li>
- <li><a href="#限流策略" id="markdown-toc-限流策略">限流策略</a> <ul>
- <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
- <li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
- <li><a href="#配置说明-1" id="markdown-toc-配置说明-1">配置说明</a></li>
+ <li><a href="#customizing-routing-policies" id="markdown-toc-customizing-routing-policies">Customizing Routing Policies</a></li>
+ <li><a href="#rate-limiting-policy" id="markdown-toc-rate-limiting-policy">Rate Limiting Policy</a> <ul>
+ <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#precautions" id="markdown-toc-precautions">Precautions</a></li>
+ <li><a href="#configuration-1" id="markdown-toc-configuration-1">Configuration</a></li>
</ul>
</li>
- <li><a href="#降级策略" id="markdown-toc-降级策略">降级策略</a> <ul>
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述-2" id="markdown-toc-场景描述-2">场景描述</a></li>
- <li><a href="#配置说明-2" id="markdown-toc-配置说明-2">配置说明</a></li>
+ <li><a href="#fallback-policy" id="markdown-toc-fallback-policy">Fallback Policy</a> <ul>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#scenario-2" id="markdown-toc-scenario-2">Scenario</a></li>
+ <li><a href="#configuration-2" id="markdown-toc-configuration-2">Configuration</a></li>
</ul>
</li>
- <li><a href="#示例代码-1" id="markdown-toc-示例代码-1">示例代码</a></li>
+ <li><a href="#sample-code-1" id="markdown-toc-sample-code-1">Sample Code</a></li>
</ul>
</nav>
</aside>
-<h2 id="负载均衡策略">负载均衡策略</h2>
-<h3 id="场景描述">场景描述</h3>
+<h2 id="load-balancing-policy">Load Balancing Policy</h2>
+<h3 id="scenario">Scenario</h3>
-<p> ServiceComb提供了基于Ribbon的负载均衡方案，用户可以通过配置文件配置负载均衡策略，当前支持随机、顺序、基于响应时间的权值等多种负载均衡路由策略。</p>
+<p> ServiceComb provides a Ribbon-based load balancing solution. You can configure a load balancing policy in the configuration file. Currently, a load balancing routing policy can be random, sequential, or based on response time weight.</p>
-<h3 id="配置说明">配置说明</h3>
+<h3 id="configuration">Configuration</h3>
-<p> 负载均衡策略在microservice.yaml文件中配置，配置项为<code class="highlighter-rouge">cse.loadbalance.[MicroServiceName].[property name]</code>，其中若省略MicroServiceName，则为全局配置；若指定MicroServiceName，则为针对特定微服务的配置。</p>
+<p> Load balancing policies are configured by setting the parameter <code class="highlighter-rouge">cse.loadbalance.[MicroServiceName].[property name]</code> in the microservice.yaml fiel. If MicroServiceName is not set, the configuration is set for all microservices. Otherwise, the configuration is set for a specific microservice.</p>
-<p> <strong>表1 配置项说明</strong></p>
+<p> <strong>Table 1 Configuration items of load balancing policy</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Items</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left">cse.loadbalance.NFLoadBalancerRuleClassName</td>
<td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule</td>
- <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule（轮询）com.netflix.loadbalancer.RandomRule（随机）com.netflix.loadbalancer.WeightedResponseTimeRule（服务器响应时间权值）io.servicecomb.loadbalance.SessionStickinessRule（会话保持）</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">负载均衡路由策略</td>
+ <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule（polling）com.netflix.loadbalancer.RandomRule（random）com.netflix.loadbalancer.WeightedResponseTimeRule（server response time weight）io.servicecomb.loadbalance.SessionStickinessRule（session stickiness）</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifiles the load balancing policy</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds</td>
<td style="text-align: left">30</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端闲置时间，超过限制后选择后面的服务器。</td>
- <td style="text-align: left">暂不支持微服务配置。e.g. cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds，不能配置为cse.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the idle time of a client. If the idle time exceeds the set value, ServiceComb will select another server.</td>
+ <td style="text-align: left">Currently, this parameter cannot be set for a certain microservice. For example, cse.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds cannot be set to cse.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.SessionStickinessRule.successiveFailedTimes</td>
<td style="text-align: left">5</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端失败次数，超过后会切换服务器</td>
- <td style="text-align: left">暂不支持微服务配置</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of failed requests from the client. If the number exceeds the set value, ServiceComb will switch to another server</td>
+ <td style="text-align: left">Currently, this parameter cannot be set for a certain microservice.</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.retryEnabled</td>
<td style="text-align: left">FALSE</td>
<td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">负载均衡捕获到服务调用异常，是否进行重试</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to call a service again when a exception is captured by the load balance.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.retryOnNext</td>
<td style="text-align: left">0</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">尝试新的服务器的次数</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of attempts to connect to another server.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.retryOnSame</td>
<td style="text-align: left">0</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">同一个服务器尝试的次数</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of attempts to connect to the same server.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.enabled</td>
<td style="text-align: left">FALSE</td>
<td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否开启故障实例隔离功能</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable faulty instance isolation.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.enableRequestThreshold</td>
<td style="text-align: left">20</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">当实例的调用总次数达到该值时开始进入隔离逻辑门槛</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the threshold number of instance calls. If this value is reached, isolation is enabled.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.errorThresholdPercentage</td>
<td style="text-align: left">20</td>
- <td style="text-align: left">Integer，区间为(0,100]</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">实例故障隔离错误百分比</td>
+ <td style="text-align: left">Integer，(0,100]</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the error percentage. Instance fault isolation is enabled when the set value is reached.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.isolation.singleTestTime</td>
<td style="text-align: left">10000</td>
<td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">故障实例单点测试时间</td>
- <td style="text-align: left">单位为ms</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the duration of a faulty instance test on a single node.</td>
+ <td style="text-align: left">This unit is ms.</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.transactionControl.policy</td>
<td style="text-align: left">io.servicecomb.loadbalance.filter.SimpleTransactionControlFilter</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">动态路由分流策略</td>
- <td style="text-align: left">框架提供了简单的分流机制，开发者也可以实现自定义的分流过滤策略</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the offload policies for dynamic routing.</td>
+ <td style="text-align: left">The framework provides simple offload mechanisms. You can also customize offload policies.</td>
</tr>
<tr>
<td style="text-align: left">cse.loadbalance.transactionControl.options</td>
<td style="text-align: left">-</td>
<td style="text-align: left">key/value pairs</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">针对SimpleTransactionControlFilter分流策略的配置项，可添加任意项过滤标签</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the parameter configured for the SimpleTransactionControlFilter offload policy. You can add any filtration tag for this item.</td>
<td style="text-align: left">-</td>
</tr>
</tbody>
</table>
-<h3 id="示例代码">示例代码</h3>
+<h3 id="sample-code">Sample Code</h3>
-<p> 负载均衡策略配置在src/main/resources/microservice.yaml文件中。</p>
+<p> in the src/main/resources/microservice.yaml file, configure a load balancing policy.</p>
-<p> 配置处理链：</p>
+<p> Configure a processing link：</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="c1"># other configurations omitted</span>
@@ -727,7 +727,7 @@
</code></pre>
</div>
-<p> 增加路由策略：</p>
+<p> Add a routing policy:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse：</span>
<span class="s"># other configurations omitted</span>
@@ -737,39 +737,38 @@
</code></pre>
</div>
-<h2 id="自定义路由策略">自定义路由策略</h2>
+<h2 id="customizing-routing-policies">Customizing Routing Policies</h2>
-<p> 用户可以在ServiceComb提供的路由策略框架下根据业务需要，通过编程的方式来开发路由策略。实施步骤如下：</p>
+<p> Based on the routing policy framework provided by ServiceComb, you can program to customize routing policies as required. Perform the following steps:</p>
<ul>
<li>
- <p>实现接口<code class="highlighter-rouge">com.netflix.loadbalancer.IRule</code>中定义的接口方法。
-路由选择逻辑在public Server choose(Object key)方法中实现。LoadBalancerStats是一个封装了负载均衡器当前运行状态的一个结构。通过获取stats中各个实例的运行指标，在choose方法中，判定将当前请求路由到哪个实例上进行处理。处理风格可以参照<code class="highlighter-rouge">io.servicecomb.loadbalance.SessionStickinessRule</code>。</p>
+ <p>Encode using the API method defined in the <code class="highlighter-rouge">com.netflix.loadbalancer.IRule</code> API. Encode in the public Server choose(Object key) method. LoadBalancerStats is a structure that encapsulates the running state of the load balancer. Determine on which instance the current routing request will be processed based on the running indexes of each instance by using the Server choose(Object key) method. Use method <code class="highlighter-rouge">io.service [...]
</li>
<li>
- <p>编译开发的策略，保证生成的class在classpath下。</p>
+ <p>Compile the developed policy and ensure that the generated class is under classpath.</p>
</li>
<li>
- <p>通过SDK配置该路由策略，假如是<code class="highlighter-rouge">AbcRule</code>。则配置如下： <code class="highlighter-rouge">cse.loadbalance.NFLoadBalancerRuleClassName=io.servicecomb.ribbon.rule.AbcRule</code></p>
+ <p>Use the software development kit(SDK) to configure the routing policy. Use AbcRule as a routing policy example. The configuration is as follows: <code class="highlighter-rouge">cse.loadbalance.NFLoadBalancerRuleClassName=io.servicecomb.ribbon.rule.AbcRule</code></p>
</li>
</ul>
-<h2 id="限流策略">限流策略</h2>
-<h3 id="场景描述-1">场景描述</h3>
+<h2 id="rate-limiting-policy">Rate Limiting Policy</h2>
+<h3 id="scenario-1">Scenario</h3>
-<p>用户在provider端使用限流策略，可以限制指定微服务向其发送请求的频率，达到限制每秒钟最大请求数量的效果。</p>
+<p>Users at the provider end can use the rate limiting policy to limit the maximum number of requests sent from a specified microservice per second.</p>
-<h3 id="注意事项">注意事项</h3>
+<h3 id="precautions">Precautions</h3>
<ol>
- <li>限流策略的控制并不是绝对精确的，可能会有少量误差。</li>
- <li>provider端的流量控制是业务层面的功能，不是安全意义上的流量控制，如需防止DDoS攻击，需要结合其他的一系列措施。</li>
- <li>流量控制是微服务级的，不是进程级的。</li>
+ <li>There may be a small different between the rate limit and actual traffic.</li>
+ <li>The rate limit function at the provider end is for service rather than security purpose. To prevent distributed denial of service(DDos) attacks, you need to take other measures.</li>
+ <li>Traffic control is a microservice-level rather than process-level function.</li>
</ol>
-<h3 id="配置说明-1">配置说明</h3>
+<h3 id="configuration-1">Configuration</h3>
-<p> 限流策略配置在microservice.yaml文件中，相关配置项见下表。要开启服务提供者端的限流策略，还需要在处理链中配置服务端限流handler，配置示例如下：</p>
+<p> Rate limiting policies are configured in the microservice.yaml file. For related configuration items, see Table 2. To enable the rate limiting policy at the provider end, you also need to configure the rate limiting handler on the server in the processing chain and add dependencies in the pom.xml file. An example of microservice.yaml file configuration is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>
@@ -779,17 +778,17 @@
</code></pre>
</div>
-<p> <strong>表2 QPS流控配置项说明</strong></p>
+<p> <strong>Table2 Configuration items of the QPS rate limit</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -797,62 +796,65 @@
<td style="text-align: left">cse.flowcontrol.Provider.qps.enabled</td>
<td style="text-align: left">true</td>
<td style="text-align: left">true/false</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否启用Provider流控</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable traffic control at the provider end.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">cse.flowcontrol.Provider.qps.limit.[ServiceName]</td>
<td style="text-align: left">2147483647（max int）</td>
- <td style="text-align: left">(0,2147483647]，整形</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">每秒钟允许的请求数</td>
- <td style="text-align: left">仅支持microservice一个级别的配置</td>
+ <td style="text-align: left">(0,2147483647]，Integer</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of requests allowed per second.</td>
+ <td style="text-align: left">This parameter can only be configured for microservice</td>
</tr>
<tr>
<td style="text-align: left">cse.flowcontrol.Provider.qps.global.limit</td>
<td style="text-align: left">2147483647（max int）</td>
- <td style="text-align: left">(0,2147483647]，整形</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">provider接受请求流量的全局配置</td>
- <td style="text-align: left">没有具体到微服务的配置时，此配置生效</td>
+ <td style="text-align: left">(0,2147483647]，Integer</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the total number of requests allowed per second at the provider end</td>
+ <td style="text-align: left">If no configuration is set for any specific microservices, this parameter takes effect</td>
</tr>
</tbody>
</table>
-<h2 id="降级策略">降级策略</h2>
-<h3 id="概念阐述">概念阐述</h3>
+<p>##</p>
+<h2 id="fallback-policy">Fallback Policy</h2>
-<p>降级策略是当服务请求异常时，微服务所采用的异常处理策略。降级策略有三个相关的技术概念：“隔离”、“熔断”、“容错”：</p>
+<h3 id="concept-description">Concept Description</h3>
+
+<p>A fallback policy is used when a service request is abnormal.</p>
+
+<p>There are three key concepts in fallback: isolation, fallbreak, and fault tolerance:</p>
-<p>降级策略有三个相关的技术概念：“隔离”、“熔断”、“容错”：</p>
<ul>
- <li>“隔离”是一种异常检测机制，常用的检测方法是请求超时、流量过大等。一般的设置参数包括超时时间、同时并发请求个数等。</li>
- <li>“熔断”是一种异常反应机制，“熔断”依赖于“隔离”。熔断通常基于错误率来实现。一般的设置参数包括统计请求的个数、错误率等。</li>
- <li>“容错”是一种异常处理机制，“容错”依赖于“熔断”。熔断以后，会调用“容错”的方法。一般的设置参数包括调用容错方法的次数等。</li>
+ <li>Isolation is an exception detection mechanism. Two common items that need to be detected are timeout duration and the number of concurrent requests.</li>
+ <li>Fallbreak is an exception response mechanism, and it depends on isolation. Fallbreak is triggered based on the error rate. Two common items need to set are the number of requests to collect and error rate.</li>
+ <li>Fault tolerance is an exception handling mechanism that depends on fallbreak. Fault tolerance is called after a fallbreak. For fault tolerance, you need to set the number of fault tolerance call items.</li>
</ul>
-<p>把这些概念联系起来：当”隔离”措施检测到N次请求中共有M次错误的时候，”熔断”不再发送后续请求，调用”容错”处理函数。这个技术上的定义，是和Netflix Hystrix一致的，通过这个定义，非常容易理解它提供的配置项，参考：<a href="https://github.com/Netflix/Hystrix/wiki/Configuration">https://github.com/Netflix/Hystrix/wiki/Configuration</a>。当前ServiceComb提供两种容错方式，分别为返回null值和抛出异常。</p>
+<p>During fallback, if M(the threshold) errors are detected in N requests, the consumer will no longer send requests and the fault tolerance mechanism will be enabled. The preceding fallback process is accepted in Netflix Hystrix and helps you configure the parameters. Obtain information about the parameter configuration at <a href="https://github.com/Netflix/Hystrix/wiki/Configuration">https://github.com/Netflix/Hystrix/wiki/Configuration</a>. Currently, ServiceComb provides two types [...]
-<h3 id="场景描述-2">场景描述</h3>
+<h3 id="scenario-2">Scenario</h3>
-<p>用户通过配置降级策略，可以设置微服务的异常处理策略。</p>
+<p>By configuring a fallback policy, you can handler microservice exceptions.</p>
-<h3 id="配置说明-2">配置说明</h3>
+<h3 id="configuration-2">Configuration</h3>
-<p> 配置项如表所示。</p>
+<p> Configuration items of fallback policies are as follows:</p>
-<p> <strong>表3 降级策略相关配置项说明</strong></p>
+<p> <strong>Table 3 Configuration items of the fallback policy</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -860,104 +862,104 @@
<td style="text-align: left">cse.isolation.timeout.enabled</td>
<td style="text-align: left">FALSE</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否启用超时检测</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable timeout detection.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.isolation.timeoutInMilliseconds</td>
<td style="text-align: left">30000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">超时时间阈值</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the timeout duration threshold.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.isolation.maxConcurrentRequests</td>
<td style="text-align: left">10</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">最大并发数阈值</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the maximum number of concurrent requests.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.enabled</td>
<td style="text-align: left">TRUE</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否启用熔断措施</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable fallbreak.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.forceOpen</td>
<td style="text-align: left">FALSE</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">不管失败次数，都进行熔断</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies that fallbreak is enable regardless of the number of failed requests or the error rate.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.forceClosed</td>
<td style="text-align: left">FALSE</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">任何时候都不熔断</td>
- <td style="text-align: left">当与forceOpen同时配置时，forceOpen优先。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies that fallbreak can be implemented at any time.</td>
+ <td style="text-align: left">If this parameter and cse.circuitBreaker.forceOpen both need to be configured, cse.circuitBreaker.forceOpen has priority.</td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.sleepWindowInMilliseconds</td>
<td style="text-align: left">15000</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">熔断后，多长时间恢复</td>
- <td style="text-align: left">恢复后，会重新计算失败情况。注意：如果恢复后的调用立即失败，那么会立即重新进入熔断。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the duration needed to recover from fallbreak.</td>
+ <td style="text-align: left">After the recovery, the number of failed requests will be recalculated. Not: If the consumer fails to send a request to the provider after the recovery, fallbreak is enabled again.</td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.requestVolumeThreshold</td>
<td style="text-align: left">20</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">10s内统计错误发生次数阈值，超过阈值则触发熔断</td>
- <td style="text-align: left">由于10秒还会被划分为10个1秒的统计周期，经过1s中后才会开始计算错误率，因此从调用开始至少经过1s，才会发生熔断。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the threshold of failed requests sent within 10 seconds. If the threshold is reached, fallbreak is triggered.</td>
+ <td style="text-align: left">Ten seconds will be divided into ten 1 seconds, and the error rate is calculated 1 second later after an error occurred. Therefore, fallbreak can be implemented at least 1 second after the call.</td>
</tr>
<tr>
<td style="text-align: left">cse.circuitBreaker.errorThresholdPercentage</td>
<td style="text-align: left">50</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">错误率阈值，达到阈值则触发熔断</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the threshold of error rate. If the threshold is reached, fallbreak is triggered.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.fallback.enabled</td>
<td style="text-align: left">TRUE</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否启用出错后的故障处理措施</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether to enable troubleshooting measures after an error occurred.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.fallback.maxConcurrentRequests</td>
<td style="text-align: left">10</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">并发调用容错处理措施（cse.fallbackpolicy.policy）的请求数，超过这个值则不再调用处理措施，直接返回异常</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the number of fault tolerance(cse.fallbackpolicy.policy) requests concurrently called. If the value exceeds 10, the measures will no longer be called, and exception are returned.</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">cse.fallbackpolicy.policy</td>
<td style="text-align: left">throwexception</td>
<td style="text-align: left">returnnulll | throwexception</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">出错后的处理策略</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the error handling policies after an error occurred.</td>
<td style="text-align: left"> </td>
</tr>
</tbody>
</table>
-<p class="notice--warning"><strong>注意：</strong> 谨慎使用cse.isolation.timeout.enabled=true。因为系统处理链都是异步执行，中间处理链的返回，会导致后面处理链的逻辑处理效果丢失。尽可能将cse.isolation.timeout.enabled保持默认值false，并且正确设置网络层超时时间cse.request.timeout=30000。</p>
+<p class="notice--warning"><strong>NOTE:</strong> Be cautions when setting cse.isolation.timeout.enabled to TRUE, All processes are asynchronously processed in the system, and any error value returned by an intermediate process because the set timeout duration is reached can cause failure of the follow-up processes. Therefore, you are advised to keep the default value FALSE for cse.isolation.timeout.enabled. For timeout duration from the network aspect, you are advised to set cse.request [...]
-<h2 id="示例代码-1">示例代码</h2>
+<h2 id="sample-code-1">Sample Code</h2>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>
@@ -979,8 +981,9 @@
</div>
<blockquote>
- <p><strong>说明：</strong>
-降级策略需要启用服务治理能力，对应的服务提供者的handler是<code class="highlighter-rouge">bizkeeper-provider</code>，服务消费者的handler是<code class="highlighter-rouge">bizkeeper-consumer</code>。</p>
+ <p><strong>NOTE:</strong></p>
+
+ <p>You need to enable service governance for fallback, The provider handler is bizkeeper-provider, and the consumer handler is bizkeeper-consumer.</p>
</blockquote>
diff --git a/content/users/service-contract/index.html b/content/users/service-contract/index.html
index 804a6ef..c43015e 100644
--- a/content/users/service-contract/index.html
+++ b/content/users/service-contract/index.html
@@ -19,12 +19,12 @@
-<title>服务契约 - Apache incubator ServiceComb</title>
+<title>Service Contract - Apache incubator ServiceComb</title>
-<meta name="description" content="服务契约">
+<meta name="description" content="Service Contract">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="服务契约">
+<meta property="og:title" content="Service Contract">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/service-contract/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="服务契约">
+ <meta property="og:description" content="Service Contract">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="服务契约">
- <meta name="twitter:description" content="服务契约">
+ <meta name="twitter:title" content="Service Contract">
+ <meta name="twitter:description" content="Service Contract">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="服务契约">
- <meta itemprop="description" content="服务契约">
+ <meta itemprop="headline" content="Service Contract">
+ <meta itemprop="description" content="Service Contract">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">服务契约
+ <h1 class="page__title" itemprop="headline">Service Contract
</h1>
</header>
@@ -564,17 +564,17 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#显式契约" id="markdown-toc-显式契约">显式契约</a> <ul>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#explicit-api-definition" id="markdown-toc-explicit-api-definition">Explicit API Definition</a> <ul>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</li>
- <li><a href="#隐式契约" id="markdown-toc-隐式契约">隐式契约</a> <ul>
- <li><a href="#概念阐述-1" id="markdown-toc-概念阐述-1">概念阐述</a></li>
- <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
- <li><a href="#涉及api" id="markdown-toc-涉及api">涉及API</a></li>
+ <li><a href="#implicit-api-definition" id="markdown-toc-implicit-api-definition">Implicit API Definition</a> <ul>
+ <li><a href="#concept-description-1" id="markdown-toc-concept-description-1">Concept Description</a></li>
+ <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#involved-api" id="markdown-toc-involved-api">Involved API</a></li>
</ul>
</li>
</ul>
@@ -582,33 +582,33 @@
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>服务契约，指基于OpenAPI规范的微服务接口契约，是服务端与消费端对于接口的定义。</p>
+<p>The API of provider and consumer microservice is defined based on OpenAPI regulations.</p>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>服务契约用于服务端和消费端的解耦，服务端围绕契约进行服务的实现，消费端根据契约进行服务的调用，可支持服务端和消费端采用不同的编程语言实现。</p>
+<p>The API definition decouples providers and consumers, which allows the two parties to use different programming languages, Providers provide services and consumers call them based on the API definition.</p>
-<h2 id="显式契约">显式契约</h2>
+<h2 id="explicit-api-definition">Explicit API Definition</h2>
-<h3 id="配置说明">配置说明</h3>
+<h3 id="configuration">Configuration</h3>
-<p>ServiceComb使用yaml文件格式定义服务契约，推荐使用<a href="http://editor.swagger.io/#/">Swagger Editor</a>工具来编写契约，可检查语法格式及自动生成API文档。详细的契约文件格式请参考<a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md">OpenAPI官方文档</a>。</p>
+<p>ServiceComb defines API in a .yaml faile. You are advised to use <a href="http://editor.swagger.io/#/">Swagger Editor</a> to write an API definition. This tool can check syntax and automaticlly generate an API document. For details about the API definition file format, see <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md"> Official OpenAPI documentation</a>。</p>
-<p>契约文件放置在”resources/microservices”或者”resources/applications”目录下，目录结构如下所示。</p>
+<p>The API definition file is located in “resources/microservices” or “resources/applications” directory. The directory structure is as follows:</p>
<pre><code class="language-txt">resources
- microservices
- - serviceName #微服务名
- - schemaId.yaml #schema接口的契约
+ - serviceName #Microservice name
+ - schemaId.yaml #schema API definition
- applications
- - appId #应用ID
- - serviceName #微服务名
- - schemaId.yaml #schema接口的契约
+ - appId #Application ID
+ - serviceName #Service name
+ - schemaId.yaml #Schema API definition
</code></pre>
-<h3 id="示例代码">示例代码</h3>
+<h3 id="sample-code">Sample Code</h3>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">swagger</span><span class="pi">:</span> <span class="s1">'</span><span class="s">2.0'</span>
<span class="s">info</span><span class="pi">:</span>
@@ -630,11 +630,11 @@
<span class="s">type</span><span class="pi">:</span> <span class="s">string</span>
<span class="s">responses</span><span class="pi">:</span>
<span class="s">200</span><span class="pi">:</span>
- <span class="s">description</span><span class="pi">:</span> <span class="s">正确返回</span>
+ <span class="s">description</span><span class="pi">:</span> <span class="s">returned for a correct result</span>
<span class="s">schema</span><span class="pi">:</span>
<span class="s">type</span><span class="pi">:</span> <span class="s">string</span>
<span class="s">default</span><span class="pi">:</span>
- <span class="s">description</span><span class="pi">:</span> <span class="s">默认返回</span>
+ <span class="s">description</span><span class="pi">:</span> <span class="s">returned for a default result</span>
<span class="s">schema</span><span class="pi">:</span>
<span class="s">type</span><span class="pi">:</span> <span class="s">string</span>
<span class="s">/sayhello</span><span class="pi">:</span>
@@ -648,11 +648,11 @@
<span class="s">$ref</span><span class="pi">:</span> <span class="s2">"</span><span class="s">#/definitions/Person"</span>
<span class="s">responses</span><span class="pi">:</span>
<span class="s">200</span><span class="pi">:</span>
- <span class="s">description</span><span class="pi">:</span> <span class="s">正确返回</span>
+ <span class="s">description</span><span class="pi">:</span> <span class="s">returned for a correct result</span>
<span class="s">schema</span><span class="pi">:</span>
<span class="s">type</span><span class="pi">:</span> <span class="s">string</span>
<span class="s">default</span><span class="pi">:</span>
- <span class="s">description</span><span class="pi">:</span> <span class="s">默认返回</span>
+ <span class="s">description</span><span class="pi">:</span> <span class="s">returned for a default result</span>
<span class="s">schema</span><span class="pi">:</span>
<span class="s">type</span><span class="pi">:</span> <span class="s">string</span>
<span class="s">definitions</span><span class="pi">:</span>
@@ -668,27 +668,27 @@
</div>
<blockquote>
- <p><strong>注意</strong>：</p>
+ <p><strong>NOTE</strong>：</p>
<ul>
- <li>根据swagger标准，basePath配置的路径需要包括web server的webroot。</li>
- <li>info.x-java-interface需要标明具体的接口路径，根据项目实际情况而定。</li>
+ <li>According to Swagger specifications, the path specified by basePath should contain the webroot of the web server.</li>
+ <li>info.x-java-interface requires a specific API path. Set it as needed.</li>
</ul>
</blockquote>
-<h2 id="隐式契约">隐式契约</h2>
-<h3 id="概念阐述-1">概念阐述</h3>
+<h2 id="implicit-api-definition">Implicit API Definition</h2>
+<h3 id="concept-description-1">Concept Description</h3>
-<p> 隐式契约是指ServiceComb根据服务实现类自动生成的服务契约。</p>
+<p> The inplicit API definition is automatically generated by ServiceComb based on the service implementation class.</p>
-<h3 id="场景描述-1">场景描述</h3>
+<h3 id="scenario-1">Scenario</h3>
-<p> 用户通过隐式契约功能，可以不预先定义契约和接口，直接定义实现类，在服务启动时，根据实现类自动生成契约，并注册到服务中心。</p>
+<p> By using the implicit API definition you can define the implementation class without pre-defining APIs. When the service is started, an API is automatically generated and registered to the service center.</p>
-<h3 id="涉及api">涉及API</h3>
+<h3 id="involved-api">Involved API</h3>
-<p> 隐式契约可用于Spring MVC、JAX-RS、透明RPC三种开发模式，具体使用参见<a href="/users/develop-with-springmvc/">用SpringMVC开发微服务</a>、<a href="/users/develop-with-jax-rs/">用JAX-RS开发微服务</a>和<a href="/users/develop-with-transparent-rpc/">用透明RPC开发微服务</a>。</p>
+<p> Implicit API definitions can be used for Spring MVC, JAX-RS, and transparent RPC development modes, For details, see <a href="/users/develop-with-springmvc/">Development Style-SpringMVC</a>, <a href="/users/develop-with-jax-rs/">Development Stype-JAX-RS</a> and <a href="/users/develop-with-transparent-rpc/">Development Style-Transparent RPC</a>.</p>
-<p> 使用透明RPC模式开发微服务时，由于从代码上无法分辨微服务开发人员期望如何定义契约，所以生成的契约全是POST方法，所有method的入参被包装为一个class，作为body参数传递，所以建议使用隐式契约开发provider时，选择SpringMVC或JAX-RS开发模式，可以得到完整的RESTful声明。</p>
+<p> When you develop a microservice in transparent RPC mode, the code does not show how you want to define an API, and all generated APIs are POST methods, The input parameters of all the methods will be packaged as a class and transferred as body parameters. Therefore, if you develop providers using implicit APIs, you are advised to choose Spring MVC or JAX-RS mode to obtain complete RESTful statements.</p>
</section>
diff --git a/content/users/service-definition/index.html b/content/users/service-definition/index.html
index 590bd0d..bbec662 100644
--- a/content/users/service-definition/index.html
+++ b/content/users/service-definition/index.html
@@ -19,12 +19,12 @@
-<title>服务定义 - Apache incubator ServiceComb</title>
+<title>Service Definition - Apache incubator ServiceComb</title>
-<meta name="description" content="服务定义">
+<meta name="description" content="Service Definition">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="服务定义">
+<meta property="og:title" content="Service Definition">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/service-definition/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="服务定义">
+ <meta property="og:description" content="Service Definition">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="服务定义">
- <meta name="twitter:description" content="服务定义">
+ <meta name="twitter:title" content="Service Definition">
+ <meta name="twitter:description" content="Service Definition">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="服务定义">
- <meta itemprop="description" content="服务定义">
+ <meta itemprop="headline" content="Service Definition">
+ <meta itemprop="description" content="Service Definition">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">服务定义
+ <h1 class="page__title" itemprop="headline">Service Definition
</h1>
</header>
@@ -564,36 +564,36 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</nav>
</aside>
-<h2 id="概念阐述">概念阐述</h2>
+<h2 id="concept-description">Concept Description</h2>
-<p>服务定义信息是微服务的身份标识，它定义了服务从属于哪个应用，以及名字和版本。服务定义信息中也可以有扩展信息，用于定义服务的属性元数据。</p>
+<p>A service definition identifies a microservice. It defines the service name, version, and the application that the service belongs to. The service definition can also contain extended information defining the attribute metadata of a service.</p>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>当用户定义新的微服务或修改微服务的基本信息时，会涉及到服务定义信息的创建和修改操作。</p>
+<p>To define a new microservice or modify its basic information, you may need to create and modify service definitions.</p>
-<h2 id="配置说明">配置说明</h2>
+<h2 id="configuration">Configuration</h2>
-<p>介绍涉及microservice.yaml文件的以下配置项，文件在项目中的存放路径为src/main/resources/microservice.yaml。</p>
+<p>This section describe the following configration items related to the microservice.yaml file in the src\main\resources\ directory.</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration on Item</th>
+ <th style="text-align: left">Default</th>
+ <th style="text-align: left">Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -601,82 +601,82 @@
<td style="text-align: left">APPLICATION_ID</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">应用名</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Indicates an application name.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">service_description.name</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">微服务名</td>
- <td style="text-align: left">应确保app内部唯一。微服务名支持数字、大小写字母和”-“、”_“、”.”三个特殊字符，但是不能以特殊字符作为首尾字符，命名规范为：^[a-zA-Z0-9]+$|^[a-zA-Z0-9][a-zA-Z0-9_-.]*[a-zA-Z0-9]$。</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Indicates a microservice name</td>
+ <td style="text-align: left">The microservice name should be unique within an application. The name can contain digits, uppercase and lowercase letters, hyphens(-), underscores(_), and periods(.); and can neither start nor end with punctuations. The naming rule is as follows: ^[a-zA-Z0-9]+$|^[a-zA-Z0-9][a-zA-Z0-9_-.]*[a-zA-Z0-9]$.</td>
</tr>
<tr>
<td style="text-align: left">service_description.version</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">是</td>
- <td style="text-align: left">微服务版本号</td>
+ <td style="text-align: left">Yes</td>
+ <td style="text-align: left">Indicates a service version.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">service_description.properties</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">微服务元数据配置（通过microservice.yaml文件进行配置）</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Configures microservice metadata(in the microservice.yaml file).</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">service_description.propertyExtendedClass</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">微服务元数据配置（通过实现接口PropertyExtended进行配置）</td>
- <td style="text-align: left">接口返回的配置会覆盖配置文件中key相同的配置。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Configures microservice metadata(through the PropertyExtended API).</td>
+ <td style="text-align: left">The configurations returned through the API will overwrite those with the same keys in the configuration file.</td>
</tr>
<tr>
<td style="text-align: left">instance_description.properties</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">服务实例元数据配置（通过microservice.yaml文件进行配置）</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Configures instance metadata(in the microservice.yaml file)</td>
<td style="text-align: left"> </td>
</tr>
<tr>
<td style="text-align: left">instance_description.propertyExtendedClass</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">微服务元数据配置（通过实现接口PropertyExtended进行配置）</td>
- <td style="text-align: left">同service_description.propertyExtendedClass</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Configures microservice metadata(through the PropertyExtended API).</td>
+ <td style="text-align: left">The configurations returned through the API will overwrite thos with the same keys in the configuration file.</td>
</tr>
</tbody>
</table>
<blockquote>
- <p>说明：</p>
+ <p>NOTE：</p>
<ul>
- <li>服务的元数据会随服务一同注册到服务中心，如需修改，则要连同服务version一起变更。若想保持服务version不变，则需要通过服务管理中心统一变更元数据。</li>
- <li>默认情况下，微服务只支持同一个app内部的服务调用。可在微服务的properties中配置allowCrossApp=true属性，开启可被跨app访问权限。</li>
+ <li>The metadata of a service is registered to the service center with the service. It is changed together with the service version. Changing metadata in the service center will keep the version unchanged.</li>
+ <li>By default, one microservice can be called by only one APPLICATION_ID. You can set allowCrossApp=true in microservice properties to access a microservice acroos APPLICATION_ID.</li>
</ul>
</blockquote>
-<h2 id="示例代码">示例代码</h2>
+<h2 id="sample-code">Sample Code</h2>
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">helloTest</span> <span class="c1">#应用名</span>
-<span class="s">service_description</span><span class="pi">:</span> <span class="c1">#服务描述</span>
- <span class="s">name</span><span class="pi">:</span> <span class="s">helloServer</span> <span class="c1">#微服务名称</span>
- <span class="s">version</span><span class="pi">:</span> <span class="s">0.0.1</span> <span class="c1">#服务版本号</span>
- <span class="s">properties</span><span class="pi">:</span> <span class="c1">#元数据</span>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">helloTest</span> <span class="c1">#Application name</span>
+<span class="s">service_description</span><span class="pi">:</span> <span class="c1">#Service description</span>
+ <span class="s">name</span><span class="pi">:</span> <span class="s">helloServer</span> <span class="c1">#Microservice name</span>
+ <span class="s">version</span><span class="pi">:</span> <span class="s">0.0.1</span> <span class="c1">#Service version</span>
+ <span class="s">properties</span><span class="pi">:</span> <span class="c1">#Metadata</span>
<span class="err"> </span><span class="s"> allowCrossApp</span><span class="pi">:</span> <span class="s">false</span>
<span class="s"> key1</span><span class="pi">:</span> <span class="s">value1</span>
<span class="s">key2</span><span class="pi">:</span> <span class="s">value2</span>
<span class="s">propertyExtentedClass</span><span class="pi">:</span> <span class="s">io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub</span>
-<span class="s">instance_description</span><span class="pi">:</span> <span class="c1">#实例描述</span>
- <span class="s">properties</span><span class="pi">:</span> <span class="c1">#元数据</span>
+<span class="s">instance_description</span><span class="pi">:</span> <span class="c1">#Instance description</span>
+ <span class="s">properties</span><span class="pi">:</span> <span class="c1">#Metadata</span>
<span class="s">key3</span><span class="pi">:</span> <span class="s">value3</span>
<span class="s">propertyExtentedClass</span><span class="pi">:</span> <span class="s">io.servicecomb.serviceregistry.MicroServicePropertyExtendedStub</span>
</code></pre>
diff --git a/content/users/service-heartbeat/index.html b/content/users/service-heartbeat/index.html
index 25cbb0a..e9fabc4 100644
--- a/content/users/service-heartbeat/index.html
+++ b/content/users/service-heartbeat/index.html
@@ -19,12 +19,12 @@
-<title>服务心跳 - Apache incubator ServiceComb</title>
+<title>Service Heartbeat - Apache incubator ServiceComb</title>
-<meta name="description" content="服务心跳">
+<meta name="description" content="Service Heartbeat">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="服务心跳">
+<meta property="og:title" content="Service Heartbeat">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/service-heartbeat/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="服务心跳">
+ <meta property="og:description" content="Service Heartbeat">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="服务心跳">
- <meta name="twitter:description" content="服务心跳">
+ <meta name="twitter:title" content="Service Heartbeat">
+ <meta name="twitter:description" content="Service Heartbeat">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="服务心跳">
- <meta itemprop="description" content="服务心跳">
+ <meta itemprop="headline" content="Service Heartbeat">
+ <meta itemprop="description" content="Service Heartbeat">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">服务心跳
+ <h1 class="page__title" itemprop="headline">Service Heartbeat
</h1>
</header>
@@ -564,31 +564,28 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#涉及api" id="markdown-toc-涉及api">涉及API</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#involved-apis" id="markdown-toc-involved-apis">Involved APIs</a></li>
</ul>
</nav>
</aside>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>当微服务实例注册到服务中心后，微服务需要定时向服务中心发送心跳。若服务中心在一定时间内没有收到心跳信息，则会注销此实例。</p>
+<p>After a microservice instance is registered in the service center, the microservice need to periodically send heartbeats to the service center. If the service center receives no heartbeat within a specific period, the instance will be registered.</p>
-<h2 id="涉及api">涉及API</h2>
+<h2 id="involved-apis">Involved APIs</h2>
<ul>
- <li><code class="highlighter-rouge">io.servicecomb.serviceregistry.client.ServiceRegistryClient</code>：服务中心客户端</li>
+ <li><code class="highlighter-rouge">io.servicecomb.serviceregistry.client.ServiceRegistryClient</code> is the service client.</li>
</ul>
-<h2 id="配置说明">配置说明</h2>
-
-<p><code class="highlighter-rouge">ServiceRegistryClient</code>提供了发送心跳的方法<code class="highlighter-rouge">heartbeat</code>，用户直接调用即可，示例代码如下：</p>
+<p><code class="highlighter-rouge">ServiceRegistryClient</code> provides heartbeat to send heartbeats. You can call it as required. The sample code is as follows:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>
- <span class="c1">// 首先需要注册微服务和实例</span>
- <span class="c1">// 发送心跳，不然实例会消失</span>
+ <span class="c1">// Register the microservice and the instance first</span>
+ <span class="c1">// Send the heartbeats. Otherwise, the instances will be lost.</span>
<span class="k">while</span> <span class="o">(</span><span class="kc">true</span><span class="o">)</span> <span class="o">{</span>
<span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"heartbeat sended:"</span> <span class="o">+</span> <span class="n">client</span><span class="o">.</span><span class="na">heartbeat</span><span class="o">(</span><span class="n">service2</span><span class="o">.</span><span class="na">getServiceId</span><span class="o">(),</span> <span class="n">instance</span><s [...]
<span class="n">Thread</span><span class="o">.</span><span class="na">sleep</span><span class="o">(</span><span class="mi">3000</span><span class="o">);</span>
diff --git a/content/users/service-interface-constraints/index.html b/content/users/service-interface-constraints/index.html
index 419414d..412904f 100644
--- a/content/users/service-interface-constraints/index.html
+++ b/content/users/service-interface-constraints/index.html
@@ -19,12 +19,12 @@
-<title>服务接口约束 - Apache incubator ServiceComb</title>
+<title>API Constraints - Apache incubator ServiceComb</title>
-<meta name="description" content="服务接口约束">
+<meta name="description" content="API Constraints">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="服务接口约束">
+<meta property="og:title" content="API Constraints">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/service-interface-constraints/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="服务接口约束">
+ <meta property="og:description" content="API Constraints">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="服务接口约束">
- <meta name="twitter:description" content="服务接口约束">
+ <meta name="twitter:title" content="API Constraints">
+ <meta name="twitter:description" content="API Constraints">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="服务接口约束">
- <meta itemprop="description" content="服务接口约束">
+ <meta itemprop="headline" content="API Constraints">
+ <meta itemprop="description" content="API Constraints">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">服务接口约束
+ <h1 class="page__title" itemprop="headline">API Constraints
</h1>
</header>
@@ -564,16 +564,20 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#接口约束说明" id="markdown-toc-接口约束说明">接口约束说明</a></li>
- <li><a href="#详细的约束列表" id="markdown-toc-详细的约束列表">详细的约束列表</a></li>
- <li><a href="#协议上的差异" id="markdown-toc-协议上的差异">协议上的差异</a></li>
+ <li><a href="#api-constraints" id="markdown-toc-api-constraints">API Constraints</a></li>
+ <li><a href="#detailed-constraint-list" id="markdown-toc-detailed-constraint-list">Detailed Constraint List</a></li>
+ <li><a href="#protocol-difference" id="markdown-toc-protocol-difference">Protocol Difference</a></li>
</ul>
</nav>
</aside>
-<h2 id="接口约束说明">接口约束说明</h2>
-<p>Java Chassis对于接口的使用约束建立在一个简单的原则上：接口定义即接口使用说明，不用通过查看代码实现，就能识别如何调用这个接口。举个例子：</p>
+<h2 id="api-constraints">API Constraints</h2>
+<p>A Java Chassis API constraints is that an API definition should describe its usage. You can identify how to call the API without checking the code.</p>
+
+<p>As developers, we aim at making our APIs easy to be called. However, developers have different understanding about this aim.</p>
+
+<p>For example:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kd">public</span> <span class="n">Person</span> <span class="nf">query</span><span class="o">(</span><span class="n">String</span> <span class="n">id</span><span class="o">);</span>
<span class="kd">public</span> <span class="n">Object</span> <span class="nf">query</span><span class="o">(</span><span class="n">String</span> <span class="n">id</span><span class="o">);</span>
@@ -581,9 +585,9 @@
</code></pre>
</div>
-<p>显然如果调用接口一，我们知道要传递一个String类型的id参数，返回值是一个Person类型，Person里面存在String类型的name等参数。如果调用接口二，我们不知道怎么处理返回值，必须参考服务提供者的文档说明。可以看出，我们是站在使用者视角这边的，以更容易被使用作为参考。</p>
+<p>Obviously, if API 1 is called, we know that an ID parameter of String type needs to be transferred. The returned value is of Person type, which contains a string-typed name parameter. If API 2 is called, we do not know how to process the returned value, and need to refer to documents provided by the service provider. API 2 is developed in the perspective of RPC developers.</p>
-<p>当我们要将接口发布为REST接口的时候，可以通过使用swagger文件，指定id使用RequestParam或者PathVariable或者RequestBody进行传递，也可以使用SpringMVC或者JAX RS提供的标签来描述。</p>
+<p>To release an API as a REST API, we can use the swagger file; specify the ID to be transmitted using RequestParam, PathVariable, or RequestBody; or use the label provided by SpringMVC or JAX-RS.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kd">public</span> <span class="n">Person</span> <span class="nf">query</span><span class="o">(</span><span class="nd">@RequestParam</span> <span class="n">String</span> <span class="n">id</span><span class="o">);</span>
<span class="kd">public</span> <span class="n">Person</span> <span class="nf">query</span><span class="o">(</span><span class="nd">@PathVariable</span> <span class="n">String</span> <span class="n">id</span><span class="o">);</span>
@@ -591,52 +595,51 @@
</code></pre>
</div>
-<p>通常，我们会将简单的数据类型，比如String, int等在RequestParam或者PathVariable传递，而把复杂的数据类型使用JSON编码以后在RequestBody传递，以减少HTTP协议限制可能给开发者带来的各种问题。</p>
+<p>Generally , simple data types, such as String and int, are transmitted in RequestParam or PathVariable, and complex data types are transmitted in RequestBody after being coded using JSON, to reduce problems cause by HTTP protocol restrictions on developers.</p>
-<h2 id="详细的约束列表">详细的约束列表</h2>
-<p>开发者不能在接口定义的时候使用如下类型：</p>
+<h2 id="detailed-constraint-list">Detailed Constraint List</h2>
+<p>Developers cannot use the following types to define APIs:</p>
<ul>
- <li>比较抽象的数据结构: java.lang.Object, net.sf.json.JsonObject等</li>
- <li>接口或者抽象类
+ <li>Abstract data structures, such as java.lang.Object, net.sf.json.JsonObject</li>
+ <li>API or abstract class
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">interface</span> <span class="nc">IPerson</span> <span class="o">{...}</span>
<span class="kd">public</span> <span class="kd">abstract</span> <span class="kd">class</span> <span class="nc">AbstractPerson</span> <span class="o">{...}</span>
</code></pre>
</div>
</li>
- <li>泛型
+ <li>Generic type
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">class</span> <span class="nc">PersonHolder</span><span class="o"><</span><span class="n">T</span><span class="o">></span> <span class="o">{...}</span>
</code></pre>
</div>
</li>
<li>
- <p>上述类型的集合类型或者没指定类型的集合，比如：<code class="highlighter-rouge">List<IPerson>, Map<String, PersonHolder<?>>, List, Map</code>等。 <code class="highlighter-rouge">List<String>, List<Person></code>这些具体类型是支持的。</p>
- </li>
- <li>包含上述类型作为属性的类型
+ <p>A collection type of the preceding types or a set without a specified type, such as <code class="highlighter-rouge">List<IPerson>, Map<String, PersonHolder<?>>, List, Map</code>. such as <code class="highlighter-rouge">List<String>, List<Person></code> are supported.</p>
+
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">class</span> <span class="nc">GroupOfPerson</span> <span class="o">{</span><span class="n">IPerson</span> <span class="n">master</span> <span class="o">...}</span>
</code></pre>
</div>
</li>
</ul>
-<p>开发者不用担心记不住这些约束，程序会在启动的时候检查不支持的类型，并给与错误提示。</p>
+<p>Developers do not need to worry about the constraints. The program automatically checks them when it is started, and displays types as properties.</p>
-<h2 id="协议上的差异">协议上的差异</h2>
-<p>尽管ServiceComb-Java-Chassis实现了不同协议之间开发方式的透明，受限于底层协议的限制，不同的协议存在少量差异。</p>
+<h2 id="protocol-difference">Protocol Difference</h2>
+<p>Although ServiceComb-Java-Chassis implements transparent transmission between protocols, there are slight differences between protocols due to the limitations of the underlying protocols:</p>
<ul>
<li>
- <p>map，key只支持string</p>
+ <p>Map, The key supports only string.</p>
</li>
- <li>highway (protobuf限制)
+ <li>highway (protobuf restriction)
<ol>
- <li>不支持在网络上传递null，包括Collection、array中的元素，map的value</li>
- <li>长度为0的数组、list，不会在网络上传递，接收端解码出来就是默认值</li>
+ <li>Null values cannot be transmitted over the network, including elements in Collection and array, and value in map.</li>
+ <li>The array and list with the length of 0 are not transmitted over the network. The receiver obtains the default value after decoding them.</li>
</ol>
</li>
<li>springmvc
<ol>
- <li>不支持Date作为path、query参数。 因为springmvc直接将Date做toString放在path、query中，与swagger的标准不匹配。</li>
+ <li>Date cannot be used for the path or query parameter. Spring MVC stores toString in path and query, which does not match the swagger standard.</li>
</ol>
</li>
</ul>
diff --git a/content/users/setup-environment/index.html b/content/users/setup-environment/index.html
index 8be7250..6a33526 100644
--- a/content/users/setup-environment/index.html
+++ b/content/users/setup-environment/index.html
@@ -19,12 +19,12 @@
-<title>环境配置 - Apache incubator ServiceComb</title>
+<title>Setup Environment - Apache incubator ServiceComb</title>
-<meta name="description" content="环境配置">
+<meta name="description" content="Setup Environment">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="环境配置">
+<meta property="og:title" content="Setup Environment">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/setup-environment/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="环境配置">
+ <meta property="og:description" content="Setup Environment">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="环境配置">
- <meta name="twitter:description" content="环境配置">
+ <meta name="twitter:title" content="Setup Environment">
+ <meta name="twitter:description" content="Setup Environment">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="环境配置">
- <meta itemprop="description" content="环境配置">
+ <meta itemprop="headline" content="Setup Environment">
+ <meta itemprop="description" content="Setup Environment">
<meta itemprop="dateModified" content="September 03, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">环境配置
+ <h1 class="page__title" itemprop="headline">Setup Environment
</h1>
</header>
@@ -564,36 +564,36 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#安装java开发环境" id="markdown-toc-安装java开发环境">安装Java开发环境</a></li>
- <li><a href="#运行service-center" id="markdown-toc-运行service-center">运行<em>Service Center</em></a></li>
+ <li><a href="#setup-local-java-develop-environment" id="markdown-toc-setup-local-java-develop-environment">Setup Local Java Develop Environment</a></li>
+ <li><a href="#starting-local-service-center" id="markdown-toc-starting-local-service-center">Starting Local <em>Service Center</em></a></li>
</ul>
</nav>
</aside>
-<h2 id="安装java开发环境">安装Java开发环境</h2>
+<h2 id="setup-local-java-develop-environment">Setup Local Java Develop Environment</h2>
<ul>
<li>
- <p>安装git，详情可参考<a href="https://git-scm.com/book/zh/v2/%E8%B5%B7%E6%AD%A5-%E5%AE%89%E8%A3%85-Git">git安装教程</a></p>
+ <p>Setup git，Refer to <a href="https://git-scm.com/book/zh/v2/%E8%B5%B7%E6%AD%A5-%E5%AE%89%E8%A3%85-Git">How to setup git</a></p>
</li>
<li>
- <p>安装JDK 1.8，详情可参考<a href="https://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html" target="_blank">JDK安装教程</a>。</p>
+ <p>Setup JDK 1.8，Refer to <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html" target="_blank">How to setup JDK</a>。</p>
</li>
<li>
- <p>安装Maven 3.x，详情可参考<a href="https://maven.apache.org/install.html" target="_blank">Maven安装教程</a>。</p>
+ <p>Setup Maven 3.x，Refer to <a href="https://maven.apache.org/install.html" target="_blank">How to setup Maven</a>。</p>
</li>
<li>
- <p>安装IntelliJ Idea IDE，详情可参考<a href="https://www.jetbrains.com/help/idea/installing-and-launching.html" target="_blank">IntelliJ安装教程</a>。</p>
+ <p>Setup IntelliJ Idea IDE，Refer to <a href="https://www.jetbrains.com/help/idea/installing-and-launching.html" target="_blank">How to setup IntelliJ</a>。</p>
</li>
</ul>
-<h2 id="运行service-center">运行<em>Service Center</em></h2>
-<p>运行Service Center有以下两种方式:</p>
+<h2 id="starting-local-service-center">Starting Local <em>Service Center</em></h2>
+<p>There are two ways to start a service center service:</p>
<ol>
<li>
- <p>以可执行文件的方式运行</p>
+ <p>Start from installation package</p>
<ul class="nav nav-tabs">
<li data-toggle="tab" class="active"><a data-toggle="tab" href="#windows">Windows</a></li>
@@ -603,20 +603,20 @@
<div class="tab-content">
<div id="windows" class="tab-pane active">
<ol>
- <li>下载<a href="https://github.com/ServiceComb/service-center/releases/download/0.5.0/service-center-0.5.0-windows-amd64.zip">服务注册中心可执行文件压缩包</a></li>
- <li>解压缩到当前文件夹</li>
- <li>进入解压缩后的目录，然后双击运行<strong>start</strong>文件</li>
+ <li>Download <a href="https://github.com/ServiceComb/service-center/releases/download/0.5.0/service-center-0.5.0-windows-amd64.zip">the installation package of ServiceCenter</a></li>
+ <li>Decompress the installation package into the installation directory.</li>
+ <li>Start Local ServiceCenter from <strong>start</strong> file</li>
</ol>
</div>
<div id="linux" class="tab-pane fade">
<ol>
- <li>下载服务注册中心可执行文件压缩包并解压缩
+ <li>Download and Decompress command:
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>wget https://github.com/ServiceComb/service-center/releases/download/0.5.0/service-center-0.5.0-linux-amd64.tar.gz
tar xvf service-center-0.5.0-linux-amd64.tar.gz
</code></pre>
</div>
</li>
- <li>运行服务注册中心
+ <li>Start local service center command:
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>bash service-center-0.5.0-linux-amd64/start.sh
</code></pre>
</div>
@@ -625,10 +625,10 @@ tar xvf service-center-0.5.0-linux-amd64.tar.gz
</div>
</div>
- <p class="notice--warning">注意：Window和Linux版本均只支持64位系统。</p>
+ <p class="notice--warning">NOTE：The OS must be 64-bit.</p>
</li>
<li>
- <p>以Docker的方式运行</p>
+ <p>Start from Docker</p>
</li>
</ol>
@@ -637,8 +637,8 @@ docker run -d -p 30100:30100 servicecomb/service-center:latest
</code></pre>
</div>
-<p class="notice--warning"><strong>注意事项：</strong> 服务注册中心运行后绑定的IP为：<em>http://127.0.0.1:30100</em>。<br />
-如使用Docker Toolbox，可通过 <code class="highlighter-rouge">docker-machine ip</code> 获取服务绑定IP地址。</p>
+<p class="notice--warning"><strong>NOTE：</strong> Running Service Center will bind on: <em>http://127.0.0.1:30100</em>。<br />
+If using Docker Toolbox，command <code class="highlighter-rouge">docker-machine ip</code> can be used to get binded IP address.</p>
</section>
diff --git a/content/users/use-service-contract/index.html b/content/users/use-service-contract/index.html
index 6eec113..75b2528 100644
--- a/content/users/use-service-contract/index.html
+++ b/content/users/use-service-contract/index.html
@@ -19,12 +19,12 @@
-<title>使用服务契约 - Apache incubator ServiceComb</title>
+<title>Service Using API Definitions - Apache incubator ServiceComb</title>
-<meta name="description" content="使用服务契约">
+<meta name="description" content="Service Using API Definitions">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用服务契约">
+<meta property="og:title" content="Service Using API Definitions">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/use-service-contract/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用服务契约">
+ <meta property="og:description" content="Service Using API Definitions">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用服务契约">
- <meta name="twitter:description" content="使用服务契约">
+ <meta name="twitter:title" content="Service Using API Definitions">
+ <meta name="twitter:description" content="Service Using API Definitions">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用服务契约">
- <meta itemprop="description" content="使用服务契约">
+ <meta itemprop="headline" content="Service Using API Definitions">
+ <meta itemprop="description" content="Service Using API Definitions">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用服务契约
+ <h1 class="page__title" itemprop="headline">Service Using API Definitions
</h1>
</header>
@@ -564,11 +564,10 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a> <ul>
- <li><a href="#配置依赖服务" id="markdown-toc-配置依赖服务">配置依赖服务</a></li>
- <li><a href="#手工配置服务契约" id="markdown-toc-手工配置服务契约">手工配置服务契约</a></li>
- <li><a href="#从服务中心自动下载契约" id="markdown-toc-从服务中心自动下载契约">从服务中心自动下载契约</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a> <ul>
+ <li><a href="#manually-configuring-service-api-definition" id="markdown-toc-manually-configuring-service-api-definition">Manually Configuring Service API Definition</a></li>
+ <li><a href="#automatically-downloading-api-definition-from-service-center" id="markdown-toc-automatically-downloading-api-definition-from-service-center">Automatically Downloading API Definition from Service Center</a></li>
</ul>
</li>
</ul>
@@ -576,19 +575,17 @@
</nav>
</aside>
-<h2 id="场景描述">场景描述</h2>
+<h2 id="scenario">Scenario</h2>
-<p>当服务消费者调用服务提供者的服务时，需要注册服务契约。消费者有两种方式获取提供者的服务契约，一种是从服务的提供方离线获取契约文件，手工配置到项目中；另一种是从服务中心自动下载契约。</p>
+<p>When a consumer calls a service from a provider, you need to register a service API definition. You can obtain service API definition from your provider for your consumer in two ways. One is to obtain the service API definition from the provider off-line and manually configure the API definition to the project. Another is to automatically download the service API definition from the service center.</p>
-<h2 id="配置说明">配置说明</h2>
+<h2 id="configuration">Configuration</h2>
<blockquote>
- <p>说明：服务契约的获取方式与服务消费者的开发方式是无关的，用户可以任意组合使用。</p>
+ <p>You can obtain service API definition in either way, regardless of the development mode of service consumers.</p>
</blockquote>
-<h3 id="配置依赖服务">配置依赖服务</h3>
-
-<p>服务消费者需要在microservice.yaml文件中配置依赖的provider，示例配置如下：</p>
+<p>In the microservice.yaml file, configure a provider for the consumer. The following is an example of the configuration:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="c1"># other configurations omitted</span>
@@ -599,36 +596,36 @@
</div>
<blockquote>
- <p>version-rule是版本匹配规则，有四种格式：</p>
+ <p>There are four kind of rule for version-rule:</p>
<ul>
- <li>精确版本匹配：例如<code class="highlighter-rouge">version-rule: 0.0.1</code>，表示只匹配版本号为0.0.1的服务提供者</li>
- <li>后续版本匹配：例如<code class="highlighter-rouge">version-rule: 1.0.0+</code>，表示匹配版本号大于或等于1.0.0的服务提供者</li>
- <li>最新版本：<code class="highlighter-rouge">version-rule: latest</code>，表示匹配最新版本的服务提供者</li>
- <li>版本范围：例如<code class="highlighter-rouge">1.0.0-2.0.2</code>，表示匹配版本号在1.0.0至2.0.2之间的服务提供者，包含1.0.0和2.0.2</li>
+ <li>Accurate Matching Rule: such as <code class="highlighter-rouge">version-rule: 0.0.1</code>, it indicates that only those providers whose version is 0.0.1 can be matched.</li>
+ <li>Later Matching Rule: such as <code class="highlighter-rouge">version-rule: 1.0.0+</code>, it indicates that those providers whose version is later that 1.0.0 can be matched.</li>
+ <li>Latest Matching Rule: such as <code class="highlighter-rouge">version-rule: latest</code>, it indicates that only those providers whose version number is latest can be matched.</li>
+ <li>Range Matching Rule: such as<code class="highlighter-rouge">1.0.0-2.0.2</code>, it indicates that those provider whose version number is between 1.0.0 and 2.0.2 can be matched, including 1.0.0 and 2.0.2</li>
</ul>
- <p>此配置项默认为<code class="highlighter-rouge">latest</code></p>
+ <p>The default version rule of version-rule is <code class="highlighter-rouge">latest</code>.</p>
</blockquote>
-<h3 id="手工配置服务契约">手工配置服务契约</h3>
+<h3 id="manually-configuring-service-api-definition">Manually Configuring Service API Definition</h3>
-<p>服务消费者的开发者在线下拿到服务提供者的契约，配置到消费者工程的特定目录下。服务契约在项目中的存放目录与<a href="/users/service-contract/">服务契约</a>的配置说明部分相同。</p>
+<p>After you obtained the API definition of your consumer from the provider, configure it in a specified directory of the consumer project. The directory is the one mentioned in the configuration description <a href="/users/service-contract/">Service Contract</a>.</p>
-<p>microservice目录下的每一个目录代表一个微服务，微服务目录下的每一个yaml文件代表一个schema契约，文件名就是schemaId。applications目录下存放需要指明appId的服务契约，用于跨app调用等场景。目录结构如下所示：</p>
+<p>Each directory under the microservices directory indecates a microservice, and each .yaml file under the jaxrs directory represents a schema API definition. The file name is the schema ID. The service API definitions whose application IDs need to be specified are stored under the applications directory for cross-application calls. The directory structure is as follows:</p>
<pre><code class="language-txt">resources
- microservices
- - serviceName # 微服务名
- - schemaId.yaml # schema接口的契约
+ - serviceName # Microservice name
+ - schemaId.yaml # Schema API definition
- applications
- - appId # 应用ID
- - serviceName # 微服务名
- - schemaId.yaml # schema接口的契约
+ - appId # Application ID
+ - serviceName # Microservice name
+ - schemaId.yaml # Schema API definition
</code></pre>
-<h3 id="从服务中心自动下载契约">从服务中心自动下载契约</h3>
+<h3 id="automatically-downloading-api-definition-from-service-center">Automatically Downloading API Definition from Service Center</h3>
-<p>服务消费者也可以不用显式地将契约存放在项目目录中，当程序启动时，ServiceComb框架会自动根据microservice.yaml文件中配置的服务提供者的微服务名称和版本号，从服务中心自动下载契约信息。</p>
+<p>If a consumer does not explicitly store the API definition in the project directory, when the application is started, the ServiceComb framework automatically downloads the information about the API definition from the service center based on the provider’s microservices name and version configured in microservice.yaml.</p>
</section>
diff --git a/content/users/use-servicecomb-in-spring-boot/index.html b/content/users/use-servicecomb-in-spring-boot/index.html
index 363d63d..5578779 100644
--- a/content/users/use-servicecomb-in-spring-boot/index.html
+++ b/content/users/use-servicecomb-in-spring-boot/index.html
@@ -19,12 +19,12 @@
-<title>在Spring Boot中使用ServiceComb - Apache incubator ServiceComb</title>
+<title>Use ServiceComb in Spring Boot - Apache incubator ServiceComb</title>
-<meta name="description" content="在Spring Boot中使用ServiceComb">
+<meta name="description" content="Use ServiceComb in Spring Boot">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="在Spring Boot中使用ServiceComb">
+<meta property="og:title" content="Use ServiceComb in Spring Boot">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/use-servicecomb-in-spring-boot/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="在Spring Boot中使用ServiceComb">
+ <meta property="og:description" content="Use ServiceComb in Spring Boot">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="在Spring Boot中使用ServiceComb">
- <meta name="twitter:description" content="在Spring Boot中使用ServiceComb">
+ <meta name="twitter:title" content="Use ServiceComb in Spring Boot">
+ <meta name="twitter:description" content="Use ServiceComb in Spring Boot">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="在Spring Boot中使用ServiceComb">
- <meta itemprop="description" content="在Spring Boot中使用ServiceComb">
+ <meta itemprop="headline" content="Use ServiceComb in Spring Boot">
+ <meta itemprop="description" content="Use ServiceComb in Spring Boot">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">在Spring Boot中使用ServiceComb
+ <h1 class="page__title" itemprop="headline">Use ServiceComb in Spring Boot
</h1>
</header>
@@ -564,16 +564,16 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#使用service-center和治理中心管理spring-cloud应用" id="markdown-toc-使用service-center和治理中心管理spring-cloud应用">使用Service Center和治理中心管理Spring Cloud应用</a> <ul>
- <li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
+ <li><a href="#using-the-service-center-and-governance-center-to-manage-the-spring-cloud-application" id="markdown-toc-using-the-service-center-and-governance-center-to-manage-the-spring-cloud-application">Using the Service Center and Governance Center to Manage the Spring Cloud Application</a> <ul>
+ <li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
+ <li><a href="#configuration-description" id="markdown-toc-configuration-description">Configuration Description</a></li>
</ul>
</li>
- <li><a href="#在servicecomb框架中集成spring-boot框架" id="markdown-toc-在servicecomb框架中集成spring-boot框架">在ServiceComb框架中集成Spring Boot框架</a> <ul>
- <li><a href="#概念阐述-1" id="markdown-toc-概念阐述-1">概念阐述</a></li>
- <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
- <li><a href="#servicecomb集成springboot" id="markdown-toc-servicecomb集成springboot">ServiceComb集成SpringBoot</a></li>
+ <li><a href="#integrating-spring-boot-into-java-chassis" id="markdown-toc-integrating-spring-boot-into-java-chassis">Integrating Spring Boot into Java Chassis</a> <ul>
+ <li><a href="#concept-description-1" id="markdown-toc-concept-description-1">Concept Description</a></li>
+ <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#integrating-spring-boot-into-servicecomb" id="markdown-toc-integrating-spring-boot-into-servicecomb">Integrating Spring Boot into ServiceComb</a></li>
</ul>
</li>
</ul>
@@ -581,47 +581,47 @@
</nav>
</aside>
-<h2 id="使用service-center和治理中心管理spring-cloud应用">使用Service Center和治理中心管理Spring Cloud应用</h2>
-<h3 id="概念阐述">概念阐述</h3>
+<h2 id="using-the-service-center-and-governance-center-to-manage-the-spring-cloud-application">Using the Service Center and Governance Center to Manage the Spring Cloud Application</h2>
+<h3 id="concept-description">Concept Description</h3>
-<p>本小节介绍在SpringCloud原生应用中，通过改变相关配置，让SpringCloud应用使用ServiceComb微服务框架中的Service Center和治理中心。</p>
+<p>This section describes how to change configurations in the native Spring Cloud application to allow the Spring Cloud application to use the service center and governance center in the microservice framework.</p>
-<h3 id="场景描述">场景描述</h3>
+<h3 id="scenario">Scenario</h3>
<ul>
<li>
- <p>SpringCloud应用默认情况下由Spring Cloud Eureka提供在分布式环境下的服务发现和服务注册的功能。</p>
+ <p>The Spring Cloud Eureka client provides the service discovery and service registration function in the distributed environment by default.</p>
<p><img src="/assets/images/manage_springcloud_application_using_sc_and_gs.png" alt="" /></p>
</li>
<li>
- <p>ServiceComb微服务框架中的Service Center用于服务元数据以及服务实例元数据的管理和处理注册、发现，同时还支持以下功能：</p>
+ <p>The service center in microservice framework is used to manage and process registration and discovery of service metadata and service instance metadata, and also supports the following functions:</p>
</li>
</ul>
<blockquote>
<ul>
<li>
- <p>支持pull/push两种模式监控实例变化</p>
+ <p>The pull and push modes used to monitor instance changes</p>
</li>
<li>
- <p>实例动态扩容，海量的长连接或者短连接</p>
+ <p>Dynamic instance scale-out, massive persistent connections, or short connections.</p>
</li>
<li>
- <p>支持灰度发布、服务分组等高级管理特性</p>
+ <p>Advanced management features, such as gray release and sersvice grouping.</p>
</li>
</ul>
</blockquote>
-<p>使用SpringBoot/Cloud开发应用，并让服务运行于ServiceComb微服务SDK容器中，使用其高性能通信、服务治理、分布式事务管理等功能。</p>
+<p>You can use Spring Cloud or Spring Boot to develop applications, enable services run in the microservice SDK container, and use functions, such as high-performance communication, service governance, and distributed transaction management.</p>
-<h3 id="配置说明">配置说明</h3>
+<h3 id="configuration-description">Configuration Description</h3>
-<p>使用SpringBoot/Cloud开发应用，在原有应用的基础上按照以下步骤进行操作，即可对接ServiceComb的SDK各组件：</p>
+<p>Use Spring Boot or Spring Cloud to develop applications and perform the following steps based on the original application to interconnect with the SDK components of ServiceComb.</p>
<ul>
<li>
- <p><strong>步骤 1</strong> 在pom中添加依赖管理dependencyManagement：</p>
+ <p><strong>Step 1</strong> Add dependencyManagement to teh POM file:</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependencyManagement></span>
<span class="nt"><dependencies></span>
@@ -638,20 +638,20 @@
</div>
</li>
<li>
- <p><strong>步骤 2</strong> 在pom中添加依赖：</p>
+ <p><strong>Step 2</strong> Add the following dependency to POM file.</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependency></span>
- <span class="c"><!--让服务运行于微服务sdk容器中--></span>
+ <span class="c"><!--let services run in the microservice SDK container.--></span>
<span class="nt"><group></span>io.servicecomb<span class="nt"></group></span>
<span class="nt"><artifactId></span>spring-boot-starter-provider<span class="nt"></artifactId></span>
<span class="nt"></dependency></span>
<span class="nt"><dependency></span>
- <span class="c"><!--使用服务中心--></span>
+ <span class="c"><!--Use Service Center.--></span>
<span class="nt"><group></span>io.servicecomb<span class="nt"></group></span>
<span class="nt"><artifactId></span>spring-boot-starter-discovery<span class="nt"></artifactId></span>
<span class="nt"></dependency></span>
<span class="nt"><dependency></span>
- <span class="c"><!--让服务运行于Spring boot embedded tomcat中--></span>
+ <span class="c"><!--Let Servieces run in Spring boot embedded tomcat--></span>
<span class="nt"><group></span>io.servicecomb<span class="nt"></group></span>
<span class="nt"><artifactId></span>spring-boot-starter-transport<span class="nt"></artifactId></span>
<span class="nt"></dependency></span>
@@ -666,9 +666,9 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 配置处理链和协议：</p>
+ <p><strong>Step 3</strong> Configure the processing chain and protocol:</p>
- <p>在resources目录下新建microservice.yaml文件，对服务进行定义，详细定义规则请参考<a href="/users/service-definition/">服务定义章节</a>，示例如下：</p>
+ <p>Create the microservice.yaml file in the resources directory and define the service. For details, see Service Definition. For example:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">APPLICATION_ID</span><span class="pi">:</span> <span class="s">discoverytest</span>
<span class="s">service_description</span><span class="pi">:</span>
@@ -677,23 +677,23 @@
<span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
<span class="s">registry</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#服务注册中心地址</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">http://127.0.0.1:30100</span> <span class="c1">#Service Center registration</span>
<span class="err"> </span><span class="s">rest</span><span class="pi">:</span>
- <span class="s">address</span><span class="pi">:</span> <span class="s">0.0.0.0:8080</span> <span class="c1">#服务发布的端口</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s">0.0.0.0:8080</span> <span class="c1">#Port number released by the service</span>
<span class="s">handler</span><span class="pi">:</span>
<span class="s">chain</span><span class="pi">:</span>
<span class="s">Provider</span><span class="pi">:</span>
- <span class="s">default</span><span class="pi">:</span> <span class="s">bizkeeper-provider</span> <span class="c1">#调用的处理链</span>
+ <span class="s">default</span><span class="pi">:</span> <span class="s">bizkeeper-provider</span> <span class="c1">#Call processing chain</span>
</code></pre>
</div>
</li>
<li>
- <p><strong>步骤4</strong> 若要使用ServiceComb的服务中心：</p>
+ <p><strong>Step 4</strong> To use the ServiceComb configuration center, run the following commands</p>
- <p>在pom中添加依赖：</p>
+ <p>Add the following dependency to POM file:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="o"><</span><span class="n">dependency</span><span class="o">></span>
- <span class="o"><!--</span><span class="err">使用服务中心</span><span class="o">--></span>
+ <span class="o"><!--</span><span class="n">Use</span> <span class="n">the</span> <span class="n">configuration</span> <span class="n">center</span><span class="o">--></span>
<span class="o"><</span><span class="n">group</span><span class="o">></span><span class="n">io</span><span class="o">.</span><span class="na">servicecomb</span><span class="o"></</span><span class="n">group</span><span class="o">></span>
<span class="o"><</span><span class="n">artifactId</span><span class="o">></span><span class="n">spring</span><span class="o">-</span><span class="n">boot</span><span class="o">-</span><span class="n">starter</span><span class="o">-</span><span class="n">discovery</span><span class="o"></</span><span class="n">artifactId</span><span class="o">></span>
<span class="o"></</span><span class="n">dependency</span><span class="o">></span>
@@ -701,11 +701,11 @@
</div>
</li>
<li>
- <p><strong>步骤 5</strong> 在启动类添加注解@EnableServiceComb：</p>
+ <p><strong>Step 5</strong> Add the annotation @EnableServiceComb to the main class:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="nd">@EnableDiscoveryClient</span>
<span class="nd">@SpringBootApplication</span>
- <span class="nd">@EnableServiceComb</span> <span class="c1">//新增注解</span>
+ <span class="nd">@EnableServiceComb</span> <span class="c1">//new annotation</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">xxxServer</span> <span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="o">{</span>
<span class="n">SpringApplication</span><span class="o">.</span><span class="na">run</span><span class="o">(</span><span class="n">xxxServer</span><span class="o">.</span><span class="na">class</span><span class="o">,</span> <span class="n">args</span><span class="o">);</span>
@@ -715,7 +715,7 @@
</div>
</li>
<li>
- <p><strong>步骤 6</strong> 定义服务契约，具体请参考<a href="/users/service-contract/">服务契约</a>，示例如下：</p>
+ <p><strong>Step 6</strong> Define the API definition. For details ,see <a href="/users/service-contract/">Service Contract</a>:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="c1">// ControllerImpl.class:</span>
<span class="nd">@RestSchema</span><span class="o">(</span><span class="n">schemaId</span> <span class="o">=</span> <span class="s">"test"</span><span class="o">)</span>
@@ -731,34 +731,32 @@
</div>
</li>
<li>
- <p><strong>步骤 7</strong> 启动xxxServer，该服务便可注册到ServiceComb的Service Center。</p>
+ <p><strong>Step 7</strong> Start the xxxServer. The service can be registered in the service center of ServiceComb.</p>
</li>
</ul>
-<h2 id="在servicecomb框架中集成spring-boot框架">在ServiceComb框架中集成Spring Boot框架</h2>
-<h3 id="概念阐述-1">概念阐述</h3>
+<h2 id="integrating-spring-boot-into-java-chassis">Integrating Spring Boot into Java Chassis</h2>
+<h3 id="concept-description-1">Concept Description</h3>
-<p>本小节介绍了在ServiceComb框架中集成SpringBoot框架的好处和操作步骤。</p>
+<p>This section describes advantages and procedures of integrating the Spring Boot framework in the Java Chassis framework.</p>
-<h3 id="场景描述-1">场景描述</h3>
+<h3 id="scenario-1">Scenario</h3>
-<h4 id="springboot框架"><strong>SpringBoot框架</strong></h4>
+<h4 id="spring-boot-framework"><strong>Spring Boot framework</strong></h4>
-<p> Spring Boot是由Pivotal团队提供的全新框架，其设计目的是用来简化新Spring应用的初始搭建以及开发过程。该框架使用了特定的方式来进行配置，从而使开发人员不再需要定义样板化的配置。从最根本上来讲，Spring Boot就是一些库的集合，它能够被任意项目的构建系统所使用。Boot的功能是模块化的，通过导入Boot所谓的”starter”模块，可以将许多的依赖添加到工程中。</p>
+<p> Spring Boot is a new framework provided by the Pivotal team. It is designed to simplify the initial establishment and development of new Spring applications. The framework is configured in a specific manner so that developers do not need to define the sample configuration. Spring Boot is a collection of some databases and can be used by the construction system of any projects. The Boot function is modularized. By importing the starter module of Spring Boot, you can add many dependen [...]
-<h4 id="在servicecomb中集成springboot"><strong>在ServiceComb中集成SpringBoot</strong></h4>
+<h4 id="integrating-spring-boot-into-serviccomb"><strong>Integrating Spring Boot into ServicComb</strong></h4>
-<p> 使用原生的ServiceComb框架开发微服务应用，如若需要使用ServiceComb框架提供的各项功能服务，需要在微服务项目工程pom文件中添加相应的依赖包，例如需要使用ServiceComb框架提供的负载均衡服务，需要添加handler-loadbalance包依赖。这样可以把ServiceComb提供的能力以starter的方式插入Spring Boot中，同时使用Spring Boot中提供的其他开箱即用的starter（例如SpringCloud）一起构建微服务。</p>
+<p> You need to use the native Java Chassis framework to develop microservice applications. To use the functions provided by the Java Chaasis framework, add dependency packages to the POM file of microservice project. For example, to use the load balancing service provided by the Java Chassis framework, add the dependency package of the handler-loadbalance package. In this way, functions provided by ServiceComb can be inserted into Spring Boot in the manner of starter, and the microserv [...]
-<h3 id="servicecomb集成springboot">ServiceComb集成SpringBoot</h3>
+<h3 id="integrating-spring-boot-into-servicecomb">Integrating Spring Boot into ServiceComb</h3>
-<p> 首先使用ServiceComb框架开发微服务应用，详细步骤请参考<a href="/users/service-definition/">开发服务提供者</a>与<a href="/users/develop-with-rest-template/">开发服务消费者</a>。然后在这个基础上集成SpringBoot框架。</p>
-
-<p> 在对应用进行SpringBoot框架适配前，请确保应用能够正常运行，并且能够从中央的maven库下载依赖的资源。</p>
+<p> You need to use the Java Chassis framework to develop microservice applications, and then integrate the Spring Boot framework.</p>
<ul>
<li>
- <p><strong>步骤 1</strong> 在工程pom文件添加<dependencyManagement>节点：</p>
+ <p><strong>Step 1</strong> Add the dependency Management node to the POM file.</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependencyManagement></span>
<span class="nt"><dependencies></span>
@@ -775,9 +773,9 @@
</div>
</li>
<li>
- <p><strong>步骤 2</strong> 添加如下依赖：</p>
+ <p><strong>Step 2</strong> Add the following dependency:</p>
- <p>引入ServiceComb提供的Spring Boot依赖</p>
+ <p>Import Spring Boot dependency provided by ServiceComb</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependency></span>
<span class="nt"><groupId></span>io.servicecomb<span class="nt"></groupId></span>
@@ -786,8 +784,6 @@
</code></pre>
</div>
- <p>引入Spring Boot依赖</p>
-
<div class="language-xml highlighter-rouge"><pre class="highlight"><code> <span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.springframework.boot<span class="nt"></groupId></span>
<span class="nt"><artifactId></span>spring-boot-starter-web<span class="nt"></artifactId></span>
@@ -800,20 +796,20 @@
</div>
</li>
<li>
- <p><strong>步骤 3</strong> 在resources目录下新建application.yml文件，文件内容如下：</p>
+ <p><strong>Step 3</strong> Create the application.yaml file in the resources directory. The file content is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">server</span><span class="pi">:</span>
- <span class="s">port</span><span class="pi">:</span> <span class="s">7999</span> <span class="c1">#此处的端口为springboot服务端口</span>
+ <span class="s">port</span><span class="pi">:</span> <span class="s">7999</span> <span class="c1">#Port number of the Spring Boot service</span>
</code></pre>
</div>
</li>
<li>
- <p><strong>步骤 4</strong> 为微服务启动类添加注解：</p>
+ <p><strong>Step 4</strong> Add the following annotation for the microservice main class:</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code> <span class="kn">package</span> <span class="n">xxx</span>
<span class="kn">import</span> <span class="nn">xxx</span>
- <span class="nd">@SpringBootApplication</span> <span class="c1">//新增注解</span>
- <span class="nd">@EnableServiceComb</span> <span class="c1">//新增注解</span>
+ <span class="nd">@SpringBootApplication</span> <span class="c1">//New Annotation</span>
+ <span class="nd">@EnableServiceComb</span> <span class="c1">//New Annotation</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">xxxServer</span><span class="o">/</span><span class="n">Client</span> <span class="o">{</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="kd">final</span> <span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="o">{</span>
<span class="err"> </span> <span class="n">Log4jUtils</span><span class="o">.</span><span class="na">init</span><span class="o">();</span>
diff --git a/content/users/use-tls/index.html b/content/users/use-tls/index.html
index 6dedd08..ee9b2ca 100644
--- a/content/users/use-tls/index.html
+++ b/content/users/use-tls/index.html
@@ -19,12 +19,12 @@
-<title>使用TLS通信 - Apache incubator ServiceComb</title>
+<title>Using TLS for Communication - Apache incubator ServiceComb</title>
-<meta name="description" content="使用TLS通信">
+<meta name="description" content="Using TLS for Communication">
@@ -33,7 +33,7 @@
<meta property="og:locale" content="en">
<meta property="og:site_name" content="Apache incubator ServiceComb">
-<meta property="og:title" content="使用TLS通信">
+<meta property="og:title" content="Using TLS for Communication">
<link rel="canonical" href="http://github.com/pages/ServiceComb/servicesomb.github.io/users/use-tls/">
@@ -41,13 +41,13 @@
- <meta property="og:description" content="使用TLS通信">
+ <meta property="og:description" content="Using TLS for Communication">
<meta name="twitter:site" content="@ServiceComb">
- <meta name="twitter:title" content="使用TLS通信">
- <meta name="twitter:description" content="使用TLS通信">
+ <meta name="twitter:title" content="Using TLS for Communication">
+ <meta name="twitter:description" content="Using TLS for Communication">
<meta name="twitter:url" content="">
@@ -543,8 +543,8 @@
<article class="page" itemscope itemtype="http://schema.org/CreativeWork">
- <meta itemprop="headline" content="使用TLS通信">
- <meta itemprop="description" content="使用TLS通信">
+ <meta itemprop="headline" content="Using TLS for Communication">
+ <meta itemprop="description" content="Using TLS for Communication">
<meta itemprop="dateModified" content="August 15, 2017">
@@ -552,7 +552,7 @@
<header>
- <h1 class="page__title" itemprop="headline">使用TLS通信
+ <h1 class="page__title" itemprop="headline">Using TLS for Communication
</h1>
</header>
@@ -560,18 +560,18 @@
<section class="page__content" itemprop="text">
- <h2 id="场景描述">场景描述</h2>
+ <h2 id="scenario">Scenario</h2>
-<p>用户通过简单的配置即可启用TLS通信，以保障数据的传输安全。</p>
+<p>Users can use simple configurations to enable TLS communication to ensure data transmission security.</p>
-<h2 id="外部服务通信配置">外部服务通信配置</h2>
+<h2 id="external-service-communication-configuration">External Service Communication Configuration</h2>
-<p>与外部服务通信相关的配置写在microservice.yaml文件中。</p>
+<p>The configuration related to external service communication is set in the microservice.yaml file.</p>
<ul>
<li>
- <p>服务中心TLS通信配置
- 微服务与服务中心的连接可以通过将http改为https启用TLS通信，配置示例如下：</p>
+ <p>TLS communication configuration of the service center and configuration center
+ The connection between the microservice and the service and configuration centers can be changed from HTTP to HTTPS, enabling TLS communication. The configuration example is as below:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
@@ -581,8 +581,8 @@
</div>
</li>
<li>
- <p>服务提供者启用TLS通信
- 服务提供者在配置服务监听地址时，可以通过在地址后面追加<code class="highlighter-rouge">?sslEnabled=true</code>开启TLS通信，示例如下：</p>
+ <p>TLS communication enabled by the service provider
+ When configuring the service listening address, the service provider can add<code class="highlighter-rouge">?sslEnabled=true</code> to the end of the address to enable TLS communication. For example:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code> <span class="s">cse</span><span class="pi">:</span>
<span class="s">rest</span><span class="pi">:</span>
@@ -594,27 +594,27 @@
</li>
</ul>
-<h2 id="证书配置">证书配置</h2>
+<h2 id="configure-a-certificate">Configure a Certificate</h2>
-<p>证书配置项写在microservice.yaml文件中，支持统一制定证书，也可以添加tag进行更细粒度的配置，有tag的配置会覆盖全局配置，配置格式如下：</p>
+<p>The certificate configuration items are set in the microservice.yaml file. You can customize certificates in a unified manner or add tags for configuration in a small granularity. The tag configuration overwrites the global configuration, and the configuration format is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">ssl.[tag].[property]</span>
</code></pre>
</div>
-<p>证书配置项见下表证书配置项说明表。</p>
+<p>For details about the certificate configuration items, see Table 1.</p>
-<p><strong>表1 证书配置项说明表</strong></p>
+<p><strong>Table 1 Certificate configuration items</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -622,125 +622,125 @@
<td style="text-align: left">ssl.protocols</td>
<td style="text-align: left">TLSv1.2</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">协议列表</td>
- <td style="text-align: left">使用逗号分隔</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the protocol list.</td>
+ <td style="text-align: left">Use commas (,) to separate protocols.</td>
</tr>
<tr>
<td style="text-align: left">ssl.ciphers</td>
<td style="text-align: left">TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,<br />TLS_RSA_WITH_AES_256_GCM_SHA384,<br />TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,<br />TLS_RSA_WITH_AES_128_GCM_SHA256</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">算法列表</td>
- <td style="text-align: left">使用逗号分隔</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the algorithm list</td>
+ <td style="text-align: left">Use commas (,) to separate protocols.</td>
</tr>
<tr>
<td style="text-align: left">ssl.authPeer</td>
<td style="text-align: left">true</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否认证对端</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies whether auhentication is required for the peer end.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.checkCN.host</td>
<td style="text-align: left">true</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否对证书的CN进行检查</td>
- <td style="text-align: left">该配置项只对Consumer端，并且使用http协议有效，即Consumer端使用rest通道有效。对于Provider端、highway通道等无效。检查CN的目的是防止服务器被钓鱼，参考标准定义：<a href="https://tools.ietf.org/html/rfc2818。">https://tools.ietf.org/html/rfc2818。</a></td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Whether the CN of the certificate is checked</td>
+ <td style="text-align: left">This configuration item is available and valid only for consumers using the HTTP protocol (the rest channel). This parameter is invalid for providers and highway channels. The purpose of checking CN is to protect the server from phishing attacks. For details, see the following standard:<a href="https://tools.ietf.org/html/rfc2818。">https://tools.ietf.org/html/rfc2818。</a></td>
</tr>
<tr>
<td style="text-align: left">ssl.trustStore</td>
<td style="text-align: left">trust.jks</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">信任证书文件</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the trust certificate file.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.trustStoreType</td>
<td style="text-align: left">JKS</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">信任证书类型</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the type of trust certificate</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.trustStoreValue</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">信任证书密码</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the password of the trust certificate file.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.keyStore</td>
<td style="text-align: left">server.p12</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">身份证书文件</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the identity certificate file.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.keyStoreType</td>
<td style="text-align: left">PKCS12</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">身份证书类型</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the type of identity certificate.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.keyStoreValue</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">身份证书密码</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the password of identity certificate.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.crl</td>
<td style="text-align: left">revoke.crl</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">吊销证书文件</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the certificate revocation list(CRL) file.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl.sslCustomClass</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">io.servicecomb.foundation.ssl.SSLCustom的实现类</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">SSLCustom类的实现，用于开发者转换密码、文件路径等。</td>
+ <td style="text-align: left">io.servicecomb.foundation.ssl.SSLCustom implementation</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies implementation of the SSLCustom class, which is used by developers to convert passwords and file paths.</td>
<td style="text-align: left">-</td>
</tr>
</tbody>
</table>
<blockquote>
- <p><strong>说明</strong>：</p>
+ <p><strong>NOTE:</strong></p>
<ul>
- <li>默认的协议算法是高强度加密算法，JDK需要安装对应的策略文件，参考：<a href="http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html">http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html</a>。 您可以在配置文件配置使用非高强度算法。</li>
- <li>微服务消费者，可以针对不同的提供者指定证书（当前证书是按照HOST签发的，不同的提供者都使用一份证书存储介质，这份介质同时给微服务访问服务中心和配置中心使用）。</li>
+ <li>The default protocol algorithm is high-strength algorithm. The JDK needs to be installed together withe the corresponding policy file. For details, visit <a href="http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html">http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html</a>. You can configure a non-high-strength algorithm in the configuration file.</li>
+ <li>The microservice consumers can specify certificates for different providers. (The current certificate is issued by HOST. Different providers use a certificate storage medium, which is used by the service center and configuration center).</li>
</ul>
</blockquote>
-<h2 id="服务中心的证书配置">服务中心的证书配置</h2>
+<h2 id="certificate-configuration-in-the-service-center">Certificate Configuration in the Service Center</h2>
-<p>目前支持使用环境变量来配置服务中心的TLS认证方式，默认开启TLS通信，双向认证模式，认证对端时同时校验对端是否匹配证书（CommonName）字段。服务管理中心的证书配置项说明见下表服务中心TLS证书配置项说明。</p>
+<p>Currently, the TLS authentication mode of the service center can be configured using environment variables. By default, TLS communication and bidirectional authentication are enables. During peer end authentication, whether the peer end matches the CommonName field of the certificate is checked. For details about the certificate configuration items in the service center, see table 2.</p>
-<p><strong>表2 服务中心TLS证书配置项说明</strong></p>
+<p><strong>Table 2 Configuration file of the service center</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Item</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -748,42 +748,42 @@
<td style="text-align: left">CSE_SSL_MODE</td>
<td style="text-align: left">1</td>
<td style="text-align: left">1/0<br />0:HTTPS<br />1:HTTP</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">设置协议模式</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Set the protocol mode.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">CSE_SSL_VERIFY_CLIENT</td>
<td style="text-align: left">1</td>
<td style="text-align: left">1/0<br />0:HTTPS<br />1:HTTP</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">设置HTTPS模式下是否认证对端</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Set whether the peer end is authenticated in HTTPS mode</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">CSE_SSL_PASSPHASE</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">设置HTTPS模式下的证书密钥访问密码</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Set the password for the certificate key in HTTPS mode</td>
<td style="text-align: left">-</td>
</tr>
</tbody>
</table>
-<p>服务管理中心配置文件为$APP_ROOT/conf/app.conf，配置项见，该配置暂不支持环境变量方式设置。</p>
+<p>The configuration file of the service center is$APP_ROOT/conf/app.conf. For details about the configuration item, see table 3. This configuration does not support the settings of environment variables.</p>
-<p>表3 服务中心配置文件</p>
+<p>Table 3 Configuration file of the service center</p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Items</th>
+ <th style="text-align: left">Default Value</th>
+ <th style="text-align: left">Value Range</th>
+ <th style="text-align: left">Mandatory</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -791,32 +791,32 @@
<td style="text-align: left">ssl_protocols</td>
<td style="text-align: left">TLSv1.2</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">通信使用的SSL版本</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the SSL version used for communication.</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">ssl_ciphers</td>
<td style="text-align: left">TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,<br />TLS_RSA_WITH_AES_256_GCM_SHA384,<br />TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,<br />TLS_RSA_WITH_AES_128_GCM_SHA256,<br />TLS_RSA_WITH_AES_128_CBC_SHA</td>
<td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">配置使用算法列表</td>
- <td style="text-align: left">由于服务中心支持HTTP/2协议，所以ssl_ciphers必须配置有TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256算法。TLS_RSA_WITH_AES_128_GCM_SHA256、TLS_RSA_WITH_AES_128_CBC_SHA被列为HTTP/2协议的不安全算法黑名单，但为了客户端算法兼容性，存在时必须配置到最后一位。</td>
+ <td style="text-align: left">No</td>
+ <td style="text-align: left">Specifies the algorithms list used to configuration</td>
+ <td style="text-align: left">ssl_cipher must be configured with the TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 algorithm, because th eservice center supports the HTTP/2 protocal. TLS_RSA_WITH_AES_128_GCM_SHA256、TLS_RSA_WITH_AES_128_CBC_SHA are listd in the insecure algorithm blacklist of the HTTP/2 protocol, but they need to be configured to the last bit of ssl_ciphers to ensure compatibility of the client algorithm.</td>
</tr>
</tbody>
</table>
-<h2 id="密钥物料及证书存放路径">密钥物料及证书存放路径</h2>
+<h2 id="path-for-storing-key-materials-and-certificates">Path for Storing Key Materials and Certificates</h2>
-<p><strong>表4 密钥物料及证书存放路径</strong></p>
+<p><strong>Table 4 Path for storing key materials and certificate</strong></p>
<table>
<thead>
<tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">对应环境变量</th>
- <th style="text-align: left">注意</th>
+ <th style="text-align: left">Configuration Items</th>
+ <th style="text-align: left">Description</th>
+ <th style="text-align: left">Environment Variable</th>
+ <th style="text-align: left">Remarks</th>
</tr>
</thead>
<tbody>
@@ -846,37 +846,37 @@
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/cipher</td>
- <td style="text-align: left">密钥物料存放目录</td>
+ <td style="text-align: left">Specifies the directory for storing key materials</td>
<td style="text-align: left">CIPHER_ROOT</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/ssl</td>
- <td style="text-align: left">证书存放目录</td>
+ <td style="text-align: left">Specifies the directory for storing certificates.</td>
<td style="text-align: left">SSL_ROOT</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/ssl/trust.cer</td>
- <td style="text-align: left">授信CA</td>
+ <td style="text-align: left">Specifies the trusted CA.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/ssl/server_key.pem</td>
- <td style="text-align: left">已加密服务端私钥文件</td>
+ <td style="text-align: left">Specifies the private key file on the encrypted server.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/ssl/server.cer</td>
- <td style="text-align: left">服务器证书</td>
+ <td style="text-align: left">Specifies the server certificate.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/etc/ssl/cert_pwd</td>
- <td style="text-align: left">用于存放解密私钥的对称加密密文文件</td>
+ <td style="text-align: left">Specifies the symmetric ciphertext file used to store the decrypted private key.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
@@ -894,22 +894,22 @@
</tr>
<tr>
<td style="text-align: left">/opt/CSE/apps/ServiceCenter/conf</td>
- <td style="text-align: left">服务管理中心配置文件目录</td>
+ <td style="text-align: left">Specifies the configuration file directory of the service center.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
<tr>
<td style="text-align: left">/opt/CSE/apps/ServiceCenter/conf/app.conf</td>
- <td style="text-align: left">应用配置文件</td>
+ <td style="text-align: left">Specifies the application configuration file.</td>
<td style="text-align: left">-</td>
<td style="text-align: left">-</td>
</tr>
</tbody>
</table>
-<h2 id="示例代码">示例代码</h2>
+<h2 id="sample-code">Sample Code</h2>
-<p>microservice.yaml文件中启用TLS通信的配置示例如下：</p>
+<p>The configuration example of enabling the TLS communication in the microservicce.yaml file is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
<span class="s">service</span><span class="pi">:</span>
<span class="s">registry</span><span class="pi">:</span>
--
To stop receiving notification emails like this one, please contact
['"commits@servicecomb.apache.org" <co...@servicecomb.apache.org>'].