This is an automated email from the ASF dual-hosted git repository.
liubao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-servicecomb-docs.git
commit 9b72c658bcfba02aef84ed3925a8d2374194ca9f
Author: DeanLee <lidi...@huawei.com>
AuthorDate: Sat Aug 25 14:05:08 2018 +0800
update java-chassis-reference/en_US/catalog/build-provider.md
---
.../en_US/catalog/build-provider.md | 61 +++++++++++-----------
1 file changed, 30 insertions(+), 31 deletions(-)
diff --git a/java-chassis-reference/en_US/catalog/build-provider.md
b/java-chassis-reference/en_US/catalog/build-provider.md
index 21118ef..8ecabf9 100644
--- a/java-chassis-reference/en_US/catalog/build-provider.md
+++ b/java-chassis-reference/en_US/catalog/build-provider.md
@@ -1,47 +1,46 @@
-## [服务定义](/build-provider/definition/service-definition.html)
-• 服务定义信息是微服务的身份标识，它定义了服务从属于哪个应用，以及名字和版本。服务定义信息中也可以有扩展信息，用于定义服务的属性元数据。
-
+## [Service Definition] (/build-provider/definition/service-definition.html)
+• Service definition information is the identity of the microservice, which
defines which application the service belongs to, as well as the name and
version. The service definition information may also have extension information
for defining attribute metadata of the service.
+
-## [定义服务契约](/build-provider/define-contract.html)
-• 服务契约，指基于OpenAPI规范的微服务接口契约，是服务端与消费端对于接口的定义。java chassis提供了两种方式定义契约：code
first和contract first。
+## [Defining Service Contracts] (/build-provider/define-contract.html)
+• Service contract, which refers to the micro-service interface contract based
on the OpenAPI specification, which is the definition of the interface between
the server and the consumer. The java chassis provides two ways to define
contracts: code first and contract first.
-## [使用隐式契约](/build-provider/code-first.html)
-• 降级策略是当服务请求异常时，微服务所采用的异常处理策略。
+## [Use implicit contract] (/build-provider/code-first.html)
+• The downgrade strategy is the exception handling strategy used by the
microservice when the service request is abnormal.
-## [使用 Swagger 注解](/build-provider/swagger-annotation.html)
-• Swagger提供了一套注解用于描述接口契约，用户使用注解，可以在代码中增加对于契约的描述信息。ServiceComb支持其中的部分注解。
+## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+• Swagger provides a set of annotations to describe the interface contract.
Users can use annotations to add descriptions of contracts to the code.
ServiceComb supports some of these annotations.
-## [用SpringMVC 开发微服务](/build-provider/springmvc.html)
-• ServiceComb支持SpringMVC注解，允许使用SpringMVC风格开发微服务。建议参照着项目 SpringMVC进行详细阅读。
+## [Developing microservices with SpringMVC] (/build-provider/springmvc.html)
+• ServiceComb supports SpringMVC annotations, allowing the development of
microservices using SpringMVC style. It is recommended to read the project in
detail with reference to the project SpringMVC.
-## [用JAX-RS开发微服务](/build-provider/jaxrs.html)
-• ServiceComb支持开发者使用JAX-RS注解，使用JAX-RS模式开发服务。
+## [Developing microservices with JAX-RS] (/build-provider/jaxrs.html)
+• ServiceComb supports developers using JAX-RS annotations to develop services
using JAX-RS patterns.
-## [使用 Swagger 注解](/build-provider/swagger-annotation.html)
-• Swagger提供了一套注解用于描述接口契约，用户使用注解，可以在代码中增加对于契约的描述信息。ServiceComb支持其中的部分注解。
+## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+• Swagger provides a set of annotations to describe the interface contract.
Users can use annotations to add descriptions of contracts to the code.
ServiceComb supports some of these annotations.
-## [使用 Swagger 注解](/build-provider/swagger-annotation.html)
-• Swagger提供了一套注解用于描述接口契约，用户使用注解，可以在代码中增加对于契约的描述信息。ServiceComb支持其中的部分注解。
+## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+• Swagger provides a set of annotations to describe the interface contract.
Users can use annotations to add descriptions of contracts to the code.
ServiceComb supports some of these annotations.
-## [用透明RPC开发微服务](/build-provider/transparent-rpc.html)
-• 透明RPC开发模式是一种基于接口和接口实现的开发模式，服务的开发者不需要使用Spring MVC和JAX-RS注解。
+## [Developing microservices with transparent RPC]
(/build-provider/transparent-rpc.html)
+• The transparent RPC development model is a development model based on
interfaces and interfaces. Service developers do not need to use Spring MVC and
JAX-RS annotations.
-## [接口定义和数据类型](/build-provider/swagger-annotation.html)
-•
ServiceComb-Java-Chassis建议接口定义遵循一个简单的原则：接口定义即接口使用说明，不用通过查看代码实现，就能识别如何调用这个接口。可以看出，这个原则站在使用者这边，以更容易被使用作为参考。ServiceComb会根据接口定义生成接口契约，符合这个原则的接口，生成的契约也是用户容易阅读的。
+## [interface definition and data type]
(/build-provider/swagger-annotation.html)
+• ServiceComb-Java-Chassis suggests that the interface definition follows a
simple principle: the interface definition is the interface usage
specification, and you can identify how to call this interface without looking
at the code implementation. It can be seen that this principle stands on the
user side and is easier to use as a reference. ServiceComb will generate
interface contracts based on interface definitions, interfaces that conform to
this principle, and the generated contract [...]
-## [服务监听地址和发布地址](/build-provider/listen-address-and-publish-address.html)
-•在JavaChassis中，服务的监听地址和发布地址是两个独立的概念，可以独立配置：
+## [Service Listening Address and Publishing Address]
(/build-provider/listen-address-and-publish-address.html)
+• In JavaChassis, the listening and publishing addresses of the service are
two separate concepts that can be configured independently:
- 监听地址：指微服务实例启动时监听的地址。该配置项决定了可以通过哪些IP访问此服务。
-
发布地址：指微服务实例注册到服务中心的地址。其他的微服务实例会通过服务中心获取此实例的信息，根据发布地址访问此服务实例，所以该配置项决定了其他服务实际上会使用哪个IP访问此服务。
+Listening address: refers to the address that the microservice instance
listens to when it starts. This configuration item determines which IPs can be
accessed by this IP.
+Publish address: refers to the address where the microservice instance is
registered to the service center. Other microservice instances will obtain
information about this instance through the service center and access the
service instance based on the publication address, so this configuration item
determines which IP other services actually use to access the service.
-## [服务配置](/build-provider/service-configuration.html)
-
-• [负载均衡策略](/build-provider/configuration/lb-strategy.html)
-• [限流策略](/build-provider/configuration/ratelimite-strategy.html)
-• [降级策略](/build-provider/configuration/downgrade-strategy.html)
-• [参数教研](/build-provider/configuration/parameter-validator.html)
+## [Service Configuration](/build-provider/service-configuration.html)
+• [Load Balancing Policy] (/build-provider/configuration/lb-strategy.html)
+• [Limiting Policy] (/build-provider/configuration/ratelimite-strategy.html)
+• [Downgrade Strategy] (/build-provider/configuration/downgrade-strategy.html)
+• [Parameters and Research]
(/build-provider/configuration/parameter-validator.html)
\ No newline at end of file
