zhengyangyong commented on a change in pull request #48: Introduction dir 
translation
URL: 
https://github.com/apache/incubator-servicecomb-docs/pull/48#discussion_r212789898
 
 

 ##########
 File path: java-chassis-reference/en_US/start/architecture.md
 ##########
 @@ -1,27 +1,27 @@
-# 微服务系统架构
+# Java Chassis Architecture
+## Basic Framework
+![ServiceComb Model](/assets/images/servicecomb_mode_en.png){: .align-center}
 
-## ![](/start/architecture.png)框架概述
+## Purpose
 
-## **主要设计意图**
+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.
 
-1.编程模型和通信模型分离,不同的编程模型可以灵活组合不同的通信模型。应用开发者在开发阶段只关注接口开发,部署阶段灵活切换通信方式;支持legacy系统的切换,legacy系统只需要修改服务发布的配置文件(或者annotation),而不需要修改代码。
+Currently, applications can be developed in Spring MVC, JAX-RS, or transparent 
RPC mode.
 
-现阶段支持SpringMVC、JAX-RS和透明RPC三种开发方式。
+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.
 
-2.内建API-first支持。通过契约规范化微服务开发,实现跨语言的通信,并支持配套的软件工具链(契约生成代码、代码生成契约等)开发,构建完整的开发生态。
+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.
 
 Review comment:
   interaction -> invocation

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to