| <?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2020-06-13T20:55:51+08:00</updated><id>/feed.xml</id><title type="html">Apache ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=>"/assets/images/ServiceComb-logo-3.jpg", "bio"=>"ServiceComb is a microservice framework that provides service registration, discovery, configuration and management utilities.", "biocn"=>"ServiceComb提供了一套关于服务注册，服务发现，服务配置以及管理功能的微服务框架", "location"=>"China", "locationcn"=>"中国", "email"=>"dev@servicecomb.apache.org", "uri"=>nil, "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, "flickr"=>nil, "facebook"=>nil, "foursquare"=>nil, "github"=>"ServiceComb", "google_plus"=>nil, "keybase"=>nil, "instagram"=>nil, "lastfm"=>nil, "linkedin"=>nil, "pinterest"=>nil, "soundcloud"=>nil, "stackoverflow"=>nil, "steam"=>nil, "tumblr"=>nil, "twitter"=>nil, "vine"=>nil, "weibo"=>nil, "xing"=>nil, "youtube"=>nil}</name><email>dev@servicecomb.apache.org</email></author><entry xml:lang="cn"><title type="html">与Apache ServiceComb一起玩开源-广工站 (PPT Download)</title><link href="/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-GDUT/" rel="alternate" type="text/html" title="与Apache ServiceComb一起玩开源-广工站 (PPT Download)" /><published>2019-12-11T00:00:00+08:00</published><updated>2019-12-11T10:30:00+08:00</updated><id>/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-GDUT</id><content type="html" xml:base="/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-GDUT/"><p>近日，Apache ServiceComb与广东工业大学计算机院学生会联合举办“与Apache ServiceComb一起玩开源”讲座。Apache ServiceComb PMC成员马彬与华为开源软件架构师郑志鹏，为广工的同学们带来“开源开发者的一天”和“微服务架构及ServiceComb实践”的精彩演讲以及现场教学互动。</p> |
| |
| <p>本次讲座得到广东工业大学计算机院学生会同学们的鼎力支持和参与。报名通道开放后，报名人数迅速达到150+，活动放在学校报告厅举办。即便在周日，同学们的热情仍然很高，给广东工业大学的同学们点赞。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/GDUT/meeting.png" alt="1" /></p> |
| |
| <p><strong>主题 1: 《开源开发者的一天》</strong></p> |
| |
| <p><a href="/assets/slides/20191211/A_day_of_open_source_developer.pdf">中文PDF下载</a></p> |
| |
| <p>来自华为开源软件部的Apache ServiceComb PMC成员马彬为同学们分享了开源软件发展史及基金会介绍、开源开发的一天、如何加入开源社区做贡献以及Apache ServiceComb微服务项目介绍等内容。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/GDUT/mabin.jpg" alt="1" /></p> |
| |
| <hr /> |
| <p><strong>主题 2: 《微服务架构及ServiceComb实践》</strong></p> |
| |
| <p><a href="/assets/slides/20191211/Microservice_architecture_and_Apache_serviceComb_practice.pdf">中文PDF下载</a></p> |
| |
| <p>华为开源软件架构师郑志鹏为同学们普及了微服务的概念和作用，并从基于Apache ServiceComb构建的天气预报Demo出发，现场“庖丁解牛”动手教学，讲解微服务架构、微服务的基本组件、如何做微服务设计以及如何使用Apache ServiceComb的核心能力实现微服务快速开发的精彩内容。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/GDUT/zzp.jpg" alt="1" /></p> |
| |
| <p>分享结束后的提问交流环节，既有同学们就开源和微服务主题，提出了自己有见解和有深度的问题，讲师积极的给予了回复。也有多个同学表示，愿意开始尝试开源活动或在自己的项目中应用微服务架构，希望寻求进一步支持和帮助的。交流环节，延长了近一个小时才彻底结束。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/GDUT/answer1.jpg" alt="1" /></p> |
| |
| <p><img src="/assets/images/colleges_and_universities/GDUT/answer2.png" alt="1" /></p> |
| |
| <p><strong>关于Apache ServiceComb 项目</strong>：</p> |
| |
| <p>ServiceComb Apache软件基金会孵化项目的主体代码由华为云捐赠，致力于帮助企业轻松构建云原生应用及传统企业业务快速微服务化，通过系列解决方案帮助用户快速开发微服务的同时实现对这些微服务应用的高效运维管理。它具有完整的微服务生态栈，无厂商锁定，当前遵循Apache Way进行孵化，已拥有如消费者云、云EI、云安全、云核等华为业务之外的一批非华为商用用户，且社区和开发者也日趋多样化。</p> |
| |
| <hr /> |
| <p><strong>如您对开源开发、微服务感兴趣，欢迎微信扫码添加“ServiceComb小助手”，咱们一起做点有意思的事情</strong></p> |
| |
| <p><img src="/assets/images/QRcode.png" alt="1" /></p></content><author><name>Zhou Zhongyuan</name></author><category term="microservice" /><category term="Meetup" /><summary type="html">与Apache ServiceComb一起玩开源-广工站 (PPT Download)</summary></entry><entry xml:lang="cn"><title type="html">使用ServiceComb客户端轻松调用ServiceCenter</title><link href="/cn/docs/servicecomb-service-center-client/" rel="alternate" type="text/html" title="使用ServiceComb客户端轻松调用ServiceCenter" /><published>2019-12-09T00:00:00+08:00</published><updated>2019-12-09T14:00:30+08:00</updated><id>/cn/docs/servicecomb-service-center-client</id><content type="html" xml:base="/cn/docs/servicecomb-service-center-client/"><h2 id="1-问题背景">1. 问题/背景</h2> |
| <p>在微服务架构中，服务注册中心是必不可少的组件，提供服务注册与管理的能力。目前使用ServiceComb服用中心的java微服务开发者，不仅需要写微服务业务代码，还要写客户端代码去调用ServiceCenter的openAPI。开发者首先需要熟悉ServiceCenter的openAPI文档，然后代码实现http客户端用于发起请求和接收响应，并绑定ServiceCenter配置参数，最后代码实现对服务中心API的调用，才能使用上ServiceCenter。为了简单化开发者使用ServiceCenter，ServiceCenter客户端实现了上述步骤。开发者只需要添加客户端jar包调用API就能轻松使用ServiceCenter，不需要过多关注openAPI文档、不需要写http客户端层代码。使用ServiceComb客户端，开发者可以轻松调用ServiceCenter，更专注于写微服务业务代码。<br /> |
| 了解更多ServiceComb-Service-Center：<a href="https://docs.servicecomb.io/service-center/zh_CN/index.html">https://docs.servicecomb.io/service-center/zh_CN/index.html</a><br /> |
| 了解更多ServiceCenter客户端：<a href="https://github.com/apache/servicecomb-java-chassis/tree/master/clients/service-center-client">https://github.com/apache/servicecomb-java-chassis/tree/master/clients/service-center-client</a><br /> |
| <img src="/assets/images/client/sc-client.jpg" alt="service-center-client-design" /></p> |
| |
| <h2 id="2-客户端原理及关键代码解读">2. 客户端原理及关键代码解读</h2> |
| <p>2.1 基于httpClient设计ServiceCenter客户端</p> |
| <ul> |
| <li> |
| <p>客户端发起请求和接收响应。客户端选择httpclient作为底层组件，用于实际发起请求和接收响应，并对请求和响应类进行了封装。代码中get方法对应发起GET请求，调用doRequest方法首先添加服务注册中心信息到封装过的httpRequest请求头部，再基于httpclient组件发起实际的http请求，最后将请求响应结果转化为封装过的httpResponse对象返回。</p> |
| |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">//make GET request</span> |
| <span class="nd">@Override</span> |
| <span class="kd">public</span> <span class="nc">HttpResponse</span> <span class="nf">get</span><span class="o">(</span><span class="nc">HttpRequest</span> <span class="n">request</span><span class="o">)</span> <span class="kd">throws</span> <span class="nc">IOException</span> <span class="o">{</span> |
| <span class="n">request</span><span class="o">.</span><span class="na">setMethod</span><span class="o">(</span><span class="nc">HttpRequest</span><span class="o">.</span><span class="na">GET</span><span class="o">);</span> |
| <span class="k">return</span> <span class="nf">doRequest</span><span class="o">(</span><span class="n">request</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="o">......</span> |
| |
| <span class="c1">//make http request with httpClient component</span> |
| <span class="kd">public</span> <span class="nc">HttpResponse</span> <span class="nf">doRequest</span><span class="o">(</span><span class="nc">HttpRequest</span> <span class="n">httpRequest</span><span class="o">)</span> <span class="kd">throws</span> <span class="nc">IOException</span> <span class="o">{</span> |
| <span class="c1">//add cse-serviceregistry-client header to identify client</span> |
| <span class="n">httpRequest</span><span class="o">.</span><span class="na">addHeader</span><span class="o">(</span><span class="no">HEADER_CONTENT_TYPE</span><span class="o">,</span> <span class="s">"application/json"</span><span class="o">);</span> |
| <span class="n">httpRequest</span><span class="o">.</span><span class="na">addHeader</span><span class="o">(</span><span class="no">HEADER_USER_AGENT</span><span class="o">,</span> <span class="s">"cse-serviceregistry-client/1.0.0"</span><span class="o">);</span> |
| |
| <span class="k">if</span> <span class="o">(</span><span class="n">globalHeaders</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span> |
| <span class="n">globalHeaders</span><span class="o">.</span><span class="na">forEach</span><span class="o">(</span><span class="nl">httpRequest:</span><span class="o">:</span><span class="n">addHeader</span><span class="o">);</span> |
| <span class="o">}</span> |
| |
| <span class="c1">//make http request</span> |
| <span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class="o">.</span><span class="na">http</span><span class="o">.</span><span class="na">HttpResponse</span> <span class="n">response</span> <span class="o">=</span> <span class="n">httpClient</span><span class="o">.</span><span class="na">execute</span><span class="o">(</span><span class="n">httpRequest</span><span class="o">.</span><span class="na">getRealRequest</span><span class="o">());</span> |
| |
| <span class="kt">int</span> <span class="n">statusCode</span> <span class="o">=</span> <span class="n">response</span><span class="o">.</span><span class="na">getStatusLine</span><span class="o">().</span><span class="na">getStatusCode</span><span class="o">();</span> |
| <span class="nc">String</span> <span class="n">messgae</span> <span class="o">=</span> <span class="n">response</span><span class="o">.</span><span class="na">getStatusLine</span><span class="o">().</span><span class="na">getReasonPhrase</span><span class="o">();</span> |
| <span class="nc">String</span> <span class="n">context</span> <span class="o">=</span> <span class="nc">EntityUtils</span><span class="o">.</span><span class="na">toString</span><span class="o">(</span><span class="n">response</span><span class="o">.</span><span class="na">getEntity</span><span class="o">(),</span> <span class="s">"UTF-8"</span><span class="o">);</span> |
| |
| <span class="k">return</span> <span class="k">new</span> <span class="nf">HttpResponse</span><span class="o">(</span><span class="n">statusCode</span><span class="o">,</span> <span class="n">messgae</span><span class="o">,</span> <span class="n">context</span><span class="o">);</span> |
| <span class="o">}</span> |
| </code></pre></div> </div> |
| </li> |
| <li> |
| <p>客户端支持定制化服务中心配置参数。代码中看到，客户端支持开发者定制服务中心IP，端口，项目名称，租户名称，导入TLSConfig和新增请求头，并通过客户端的Builder方法注入配置。TLSConfig为客户端TLS认证配置类，给客户端导入TLS证书配置，即可开启客户端双向认证模式。</p> |
| |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="cm">/** |
| * Customized host, port, projectName, tenantName, TLSConf, headers and any one parameter can be null. |
| */</span> |
| <span class="kd">public</span> <span class="nf">ServiceCenterClient</span><span class="o">(</span><span class="nc">String</span> <span class="n">host</span><span class="o">,</span> <span class="kt">int</span> <span class="n">port</span><span class="o">,</span> <span class="nc">String</span> <span class="n">projectName</span><span class="o">,</span> <span class="nc">String</span> <span class="n">tenantName</span><span class="o">,</span> <span class="nc">TLSConfig</span> <span class="n">tlsConfig</span><span class="o">,</span> |
| <span class="nc">Map</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">,</span> <span class="nc">String</span><span class="o">&gt;</span> <span class="n">extraGlobalHeaders</span><span class="o">)</span> <span class="o">{</span> |
| <span class="nc">HttpTransport</span> <span class="n">httpTransport</span> <span class="o">=</span> <span class="nc">HttpTransportFactory</span><span class="o">.</span><span class="na">getDefaultHttpTransport</span><span class="o">();</span> |
| <span class="k">if</span> <span class="o">(</span><span class="n">tlsConfig</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span> |
| <span class="n">httpTransport</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">TLSHttpsTransport</span><span class="o">(</span><span class="n">tlsConfig</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="n">httpTransport</span><span class="o">.</span><span class="na">addHeaders</span><span class="o">(</span><span class="n">extraGlobalHeaders</span><span class="o">);</span> |
| |
| <span class="c1">//set configuration parameters</span> |
| <span class="k">this</span><span class="o">.</span><span class="na">httpClient</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ServiceCenterRawClient</span><span class="o">.</span><span class="na">Builder</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">setHost</span><span class="o">(</span><span class="n">host</span><span class="o">)</span> |
| <span class="o">.</span><span class="na">setPort</span><span class="o">(</span><span class="n">port</span><span class="o">)</span> |
| <span class="o">.</span><span class="na">setProjectName</span><span class="o">(</span><span class="n">projectName</span><span class="o">)</span> |
| <span class="o">.</span><span class="na">setTenantName</span><span class="o">(</span><span class="n">tenantName</span><span class="o">)</span> |
| <span class="o">.</span><span class="na">setHttpTransport</span><span class="o">(</span><span class="n">httpTransport</span><span class="o">).</span><span class="na">build</span><span class="o">();</span> |
| <span class="o">}</span> |
| </code></pre></div> </div> |
| </li> |
| </ul> |
| |
| <p>2.2 ServiceCenter客户端核心API</p> |
| <ul> |
| <li>服务注册与发现，注册服务和实例到服务注册中心，根据服务ID发现服务实例。registerMicroserviceInstance方法用于注册服务实例，发起httpPOST请求访问服务实例注册URL，并将实例注入到请求body中，返回服务ID字符串; getMicroserviceInstanceList方法用于发现服务的所有实例，根据服务ID，发起httpGET请求访问服务发现URL，返回MicroserviceInstancesResponse对象。 |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="c1">//service register</span> |
| <span class="kd">public</span> <span class="nc">String</span> <span class="nf">registerMicroserviceInstance</span><span class="o">(</span><span class="nc">MicroserviceInstance</span> <span class="n">instance</span><span class="o">,</span> <span class="nc">String</span> <span class="n">serviceId</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">try</span> <span class="o">{</span> |
| <span class="nc">ObjectMapper</span> <span class="n">mapper</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ObjectMapper</span><span class="o">();</span> |
| <span class="n">mapper</span><span class="o">.</span><span class="na">configure</span><span class="o">(</span><span class="nc">SerializationFeature</span><span class="o">.</span><span class="na">WRAP_ROOT_VALUE</span><span class="o">,</span> <span class="kc">true</span><span class="o">);</span> |
| <span class="nc">HttpResponse</span> <span class="n">response</span> <span class="o">=</span> <span class="n">httpClient</span><span class="o">.</span><span class="na">postHttpRequest</span><span class="o">(</span><span class="s">"/registry/microservices/"</span> <span class="o">+</span> <span class="n">serviceId</span> <span class="o">+</span> <span class="s">"/instances"</span><span class="o">,</span> <span class="kc">null</span><span class="o">,</span> |
| <span class="n">mapper</span><span class="o">.</span><span class="na">writeValueAsString</span><span class="o">(</span><span class="n">instance</span><span class="o">));</span> |
| <span class="k">if</span> <span class="o">(</span><span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">==</span> <span class="nc">HttpStatus</span><span class="o">.</span><span class="na">SC_OK</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">return</span> <span class="n">response</span><span class="o">.</span><span class="na">getContent</span><span class="o">();</span> |
| <span class="o">}</span> <span class="k">else</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"register service instance fails, statusCode = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">+</span> <span class="s">"; message = "</span> <span class="o">+</span> <span class="n">response</span> |
| <span class="o">.</span><span class="na">getMessage</span><span class="o">()</span> |
| <span class="o">+</span> <span class="s">"; content = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getContent</span><span class="o">());</span> |
| <span class="o">}</span> |
| <span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="nc">IOException</span> <span class="n">e</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"register service instance fails"</span><span class="o">,</span> <span class="n">e</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| |
| <span class="c1">//service discovery</span> |
| <span class="kd">public</span> <span class="nc">MicroserviceInstancesResponse</span> <span class="nf">getMicroserviceInstanceList</span><span class="o">(</span><span class="nc">String</span> <span class="n">serviceId</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">try</span> <span class="o">{</span> |
| <span class="nc">HttpResponse</span> <span class="n">response</span> <span class="o">=</span> <span class="n">httpClient</span> |
| <span class="o">.</span><span class="na">getHttpRequest</span><span class="o">(</span><span class="s">"/registry/microservices/"</span> <span class="o">+</span> <span class="n">serviceId</span> <span class="o">+</span> <span class="s">"/instances"</span><span class="o">,</span> <span class="kc">null</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span> |
| <span class="k">if</span> <span class="o">(</span><span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">==</span> <span class="nc">HttpStatus</span><span class="o">.</span><span class="na">SC_OK</span><span class="o">)</span> <span class="o">{</span> |
| <span class="nc">ObjectMapper</span> <span class="n">mapper</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ObjectMapper</span><span class="o">();</span> |
| <span class="k">return</span> <span class="n">mapper</span><span class="o">.</span><span class="na">readValue</span><span class="o">(</span><span class="n">response</span><span class="o">.</span><span class="na">getContent</span><span class="o">(),</span> <span class="nc">MicroserviceInstancesResponse</span><span class="o">.</span><span class="na">class</span><span class="o">);</span> |
| <span class="o">}</span> <span class="k">else</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"get service instances list fails, statusCode = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">+</span> <span class="s">"; message = "</span> <span class="o">+</span> <span class="n">response</span> |
| <span class="o">.</span><span class="na">getMessage</span><span class="o">()</span> |
| <span class="o">+</span> <span class="s">"; content = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getContent</span><span class="o">());</span> |
| <span class="o">}</span> |
| <span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="nc">IOException</span> <span class="n">e</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"get service instances list fails"</span><span class="o">,</span> <span class="n">e</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| </code></pre></div> </div> |
| </li> |
| <li>心跳，服务实例发送心跳告知服务中心。代码中发起httpPUT请求中访问心跳URL，并导入HeartbeatsRequest （包含服务ID和实例ID）到请求body中，响应状态码为200表示心跳成功。 |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="c1">//heartBeats</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">sendHeartBeats</span><span class="o">(</span><span class="nc">HeartbeatsRequest</span> <span class="n">heartbeatsRequest</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">try</span> <span class="o">{</span> |
| <span class="nc">ObjectMapper</span> <span class="n">mapper</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ObjectMapper</span><span class="o">();</span> |
| <span class="nc">HttpResponse</span> <span class="n">response</span> <span class="o">=</span> <span class="n">httpClient</span> |
| <span class="o">.</span><span class="na">putHttpRequest</span><span class="o">(</span><span class="s">"/registry/heartbeats"</span><span class="o">,</span> <span class="kc">null</span><span class="o">,</span> <span class="n">mapper</span><span class="o">.</span><span class="na">writeValueAsString</span><span class="o">(</span><span class="n">heartbeatsRequest</span><span class="o">));</span> |
| |
| <span class="k">if</span> <span class="o">(</span><span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">==</span> <span class="nc">HttpStatus</span><span class="o">.</span><span class="na">SC_OK</span><span class="o">)</span> <span class="o">{</span> |
| <span class="no">LOGGER</span><span class="o">.</span><span class="na">info</span><span class="o">(</span><span class="s">"HEARTBEATS SUCCESS"</span><span class="o">);</span> |
| <span class="o">}</span> <span class="k">else</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"heartbeats fails, statusCode = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getStatusCode</span><span class="o">()</span> <span class="o">+</span> <span class="s">"; message = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getMessage</span><span class="o">()</span> |
| <span class="o">+</span> <span class="s">"; content = "</span> <span class="o">+</span> <span class="n">response</span><span class="o">.</span><span class="na">getContent</span><span class="o">());</span> |
| <span class="o">}</span> |
| <span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="nc">IOException</span> <span class="n">e</span><span class="o">)</span> <span class="o">{</span> |
| <span class="k">throw</span> <span class="k">new</span> <span class="nf">OperationException</span><span class="o">(</span> |
| <span class="s">"heartbeats fails "</span><span class="o">,</span> <span class="n">e</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| </code></pre></div> </div> |
| </li> |
| </ul> |
| |
| <p>2.3 更多客户端API介绍，参考客户端说明文档 <a href="https://github.com/apache/servicecomb-java-chassis/tree/master/clients/service-center-client">https://github.com/apache/servicecomb-java-chassis/tree/master/clients/service-center-client</a></p> |
| |
| <h2 id="3-servicecenter客户端实践">3. ServiceCenter客户端实践</h2> |
| <p>3.1 实践准备</p> |
| <ul> |
| <li>启动ServiceComb服务中心：<a href="http://servicecomb.apache.org/cn/docs/service-center/install/">http://servicecomb.apache.org/cn/docs/service-center/install/</a></li> |
| <li>下载演示代码：<a href="https://github.com/zaneChou1/spring-boot-servicecenter">https://github.com/zaneChou1/spring-boot-servicecenter</a></li> |
| </ul> |
| |
| <p>3.2 provider端启动服务，通过客户端注册到ServiceCenter<br /> |
| 运行provider模块，启动helloServer服务，并调用客户端API创建客户端对象、创建helloServer服务和实例对象、注册服务和实例到servicecomb 服务中心，并保持30s一次心跳，代码实现如下。</p> |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">registerMicroservice</span><span class="o">(){</span> |
| <span class="c1">//new ServiceCenterClient object</span> |
| <span class="nc">ServiceCenterClient</span> <span class="n">sc</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ServiceCenterClient</span><span class="o">();</span> |
| |
| <span class="c1">//new Microservice object and setting properties and serviceName is necessary</span> |
| <span class="nc">Microservice</span> <span class="n">microservice</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">Microservice</span><span class="o">();</span> |
| <span class="n">microservice</span><span class="o">.</span><span class="na">setServiceId</span><span class="o">(</span><span class="s">"1111"</span><span class="o">);</span> |
| <span class="n">microservice</span><span class="o">.</span><span class="na">setServiceName</span><span class="o">(</span><span class="s">"HelloServer"</span><span class="o">);</span> |
| <span class="c1">//register microservice to service-center</span> |
| <span class="n">sc</span><span class="o">.</span><span class="na">registerMicroservice</span><span class="o">(</span><span class="n">microservice</span><span class="o">);</span> |
| |
| <span class="c1">//new MicroserviceInstance object and bind server IP and port</span> |
| <span class="nc">MicroserviceInstance</span> <span class="n">instance</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">MicroserviceInstance</span><span class="o">();</span> |
| <span class="nc">List</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">&gt;</span> <span class="n">endPoints</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ArrayList</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">&gt;();</span> |
| <span class="n">endPoints</span><span class="o">.</span><span class="na">add</span><span class="o">(</span><span class="s">"rest://127.0.0.1:8080/"</span><span class="o">);</span> |
| <span class="n">instance</span><span class="o">.</span><span class="na">setEndpoints</span><span class="o">(</span><span class="n">endPoints</span><span class="o">);</span> |
| <span class="c1">//setting instance hostName, instanceId and hostName is necessary</span> |
| <span class="n">instance</span><span class="o">.</span><span class="na">setHostName</span><span class="o">(</span><span class="s">"test"</span><span class="o">);</span> |
| <span class="n">instance</span><span class="o">.</span><span class="na">setInstanceId</span><span class="o">(</span><span class="s">"2222"</span><span class="o">);</span> |
| <span class="c1">//register microservice instance to service-center</span> |
| <span class="n">sc</span><span class="o">.</span><span class="na">registerMicroserviceInstance</span><span class="o">(</span><span class="n">instance</span><span class="o">,</span><span class="n">microservice</span><span class="o">.</span><span class="na">getServiceId</span><span class="o">());</span> |
| |
| <span class="c1">//send a heartbeat every 30s</span> |
| <span class="nc">HeartbeatsRequest</span> <span class="n">heartbeatsRequest</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">HeartbeatsRequest</span><span class="o">(</span><span class="s">"1111"</span><span class="o">,</span><span class="s">"2222"</span><span class="o">);</span> |
| <span class="k">while</span><span class="o">(</span><span class="kc">true</span><span class="o">){</span> |
| <span class="n">sc</span><span class="o">.</span><span class="na">sendHeartBeats</span><span class="o">(</span><span class="n">heartbeatsRequest</span><span class="o">);</span> |
| <span class="k">try</span> <span class="o">{</span> |
| <span class="nc">Thread</span><span class="o">.</span><span class="na">sleep</span><span class="o">(</span><span class="mi">30000</span><span class="o">);</span> |
| <span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="nc">InterruptedException</span> <span class="n">e</span><span class="o">)</span> <span class="o">{</span> |
| <span class="n">e</span><span class="o">.</span><span class="na">printStackTrace</span><span class="o">();</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| </code></pre></div></div> |
| <p>查看service-center的UI显示如下，helloServer服务注册到服务中心成功，且有一个服务实例test。 <br /> |
| <img src="/assets/images/client/sc-sample-UI.png" alt="" /><br /> |
| 访问provider服务监听的8080端口，返回“Hello Spring-Boot-ServiceCenter !”。<br /> |
| <img src="/assets/images/client/sc-sample-provider.png" alt="" /></p> |
| |
| <p>3.3 consumer端通过客户端发现服务实例，发起服务调用<br /> |
| 运行consumer模块，启动consumer服务，调用客户端API新建客户端对象、发现helloServer服务实例、获取服务监听的IP和端口，最后调用provider端helloServer服务返回结果。</p> |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">//find service instance</span> |
| <span class="nc">ServiceCenterClient</span> <span class="n">sc</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ServiceCenterClient</span><span class="o">();</span> |
| <span class="nc">MicroserviceInstancesResponse</span> <span class="n">instances</span> <span class="o">=</span> <span class="n">sc</span><span class="o">.</span><span class="na">getMicroserviceInstanceList</span><span class="o">(</span><span class="s">"1111"</span><span class="o">);</span> |
| <span class="c1">//get IP and port that service is listening on</span> |
| <span class="no">URI</span> <span class="n">endpointURIBuilder</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">URIBuilder</span><span class="o">(</span><span class="n">instances</span><span class="o">.</span><span class="na">getInstances</span><span class="o">().</span><span class="na">get</span><span class="o">(</span><span class="mi">0</span><span class="o">).</span><span class="na">getEndpoints</span><span class="o">().</span><span class="na">get</span><span class="o">(</span><span class="mi">0</span><span class="o">)).</span><span class="na">build</span><span class="o">();</span> |
| <span class="kt">int</span> <span class="n">port</span> <span class="o">=</span> <span class="n">endpointURIBuilder</span><span class="o">.</span><span class="na">getPort</span><span class="o">();</span> |
| <span class="nc">String</span> <span class="n">host</span> <span class="o">=</span> <span class="n">endpointURIBuilder</span><span class="o">.</span><span class="na">getHost</span><span class="o">();</span> |
| |
| <span class="c1">//call service</span> |
| <span class="nc">RestTemplate</span> <span class="n">restTemplate</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">RestTemplate</span><span class="o">();</span> |
| <span class="nc">ResponseEntity</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">&gt;</span> <span class="n">result</span> <span class="o">=</span> <span class="n">restTemplate</span><span class="o">.</span><span class="na">getForEntity</span><span class="o">(</span><span class="s">"http://"</span><span class="o">+</span><span class="n">host</span><span class="o">+</span><span class="s">":"</span><span class="o">+</span><span class="n">port</span><span class="o">,</span><span class="nc">String</span><span class="o">.</span><span class="na">class</span><span class="o">);</span> |
| <span class="k">return</span> <span class="n">result</span><span class="o">.</span><span class="na">getBody</span><span class="o">();</span> |
| </code></pre></div></div> |
| <p>访问consumer端监听的8081端口，返回helloServer的响应结果“Hello Spring-Boot-ServiceCenter !”，consumer端通过ServiceComb服务注册中心调用provider端服务成功。 <br /> |
| <img src="/assets/images/client/sc-sample-consumer.png" alt="" /></p></content><author><name>Zhou Zhongyuan</name></author><category term="ServiceCenter" /><category term="Client" /><summary type="html">使用ServiceComb客户端轻松调用ServiceCenter</summary></entry><entry xml:lang="cn"><title type="html">与Apache ServiceComb一起玩开源-北邮站 (PPT Download)</title><link href="/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-BUPT/" rel="alternate" type="text/html" title="与Apache ServiceComb一起玩开源-北邮站 (PPT Download)" /><published>2019-11-20T00:00:00+08:00</published><updated>2019-11-21T15:18:43+08:00</updated><id>/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-BUPT</id><content type="html" xml:base="/cn/docs/playing-on-the-open-source-community-with-Apache-ServiceComb-BUPT/"><p>近日，Apache ServiceComb与北京邮电大学“乐群学堂”联合举办“与Apache ServiceComb一起玩开源”讲座。Apache ServiceComb PMC成员马彬与华为开源软件架构师郑志鹏，为北邮的同学们带来“ServiceComb带你走进开源”和“使用ServiceComb快速开发高并发高可用电商系统实践使用微服务架构快速开发万级TPS高可用电商系统”的精彩演讲以及现场教学互动。</p> |
| |
| <p>本次讲座得到北邮计算机学院闫博、徐飒等老师以及广大同学的鼎力支持和参与。报名通道开放伊始，原定200个的参会名额即被定满，经过老师们积极协调临时增加了部分名额，但是由于场地资源有限，这次没有报上名的同学，期待下次再会面啦&gt;_&lt;~~</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/1.signup.jpg" alt="1" /> <img src="/assets/images/colleges_and_universities/BUPT/2.signup.jpg" alt="1" /></p> |
| |
| <p>讲座开展前期，同学们积极响应和回馈社区，ServiceComb通过建立社区交流群组，与同学互动交流，提前分享动手实践指南以及解答疑问。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/3.answer.jpg" alt="1" /> <img src="/assets/images/colleges_and_universities/BUPT/4.answer.jpg" alt="1" /></p> |
| |
| <ul> |
| <li>讲座定于19:00开始，18:10会场前同学已经在有序地排队入场，给北邮的同学点赞</li> |
| </ul> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/5.enter.jpg" alt="1" /></p> |
| |
| <ul> |
| <li>为“乐群学堂”的师生们点赞，非常贴心地在走廊安排了临时加座~~~</li> |
| </ul> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/6.meeting.jpg" alt="1" /></p> |
| |
| <p><strong>主题 1: 《Apache ServiceComb带你走进开源开发》</strong></p> |
| |
| <p><a href="/assets/slides/20191120/Apache_ServiceComb.pdf">中文PDF下载</a></p> |
| |
| <p>来自华为开源软件部的Apache ServiceComb PMC成员马彬为同学们分享了开源软件的演进历史、开源基金会介绍、开源社区以及基于首个Apache ServiceComb微服务项目的开源开发实战内容。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/7.meeting.jpg" alt="1" /></p> |
| |
| <hr /> |
| <p><strong>主题 2: 《使用ServiceComb快速开发高并发高可用电商系统实践》</strong></p> |
| |
| <p><a href="/assets/slides/20191120/2.Apache_ServiceComb_builds_online_store.pdf">中文PDF下载</a></p> |
| |
| <p>华为开源软件架构师郑志鹏为同学们普及了微服务的概念和作用，并从基于Apache ServiceComb构建的万级TPS高可用电商系统案例出发，现场“庖丁解牛”动手教学，讲解如何做微服务设计、如何合理拆分微服务、如何分库分表，以及如何使用Apache ServiceComb的核心能力实现微服务快速开发、部署、上线等精彩内容。</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/8.meeting.jpg" alt="1" /></p> |
| |
| <p>会后，同学们踊跃发言，与讲师就开源、微服务、个人职业发展等问题进行了开放式的交流，收获满满~</p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/9.meeting.jpg" alt="1" /></p> |
| |
| <p><img src="/assets/images/colleges_and_universities/BUPT/10.meeting.jpg" alt="1" /></p> |
| |
| <p><strong>关于Apache ServiceComb 项目</strong>：</p> |
| |
| <p>ServiceComb Apache软件基金会孵化项目的主体代码由华为云捐赠，致力于帮助企业轻松构建云原生应用及传统企业业务快速微服务化，通过系列解决方案帮助用户快速开发微服务的同时实现对这些微服务应用的高效运维管理。它具有完整的微服务生态栈，无厂商锁定，当前遵循Apache Way进行孵化，已拥有如消费者云、云EI、云安全、云核等华为业务之外的一批非华为商用用户，且社区和开发者也日趋多样化。</p> |
| |
| <hr /> |
| <p><strong>如您对开源开发、微服务感兴趣，欢迎微信扫码添加“ServiceComb小助手”，咱们一起做点有意思的事情</strong></p> |
| |
| <p><img src="/assets/images/QRcode.png" alt="1" /></p></content><author><name>Chinx</name></author><category term="microservice" /><category term="Meetup" /><summary type="html">与Apache ServiceComb一起玩开源-北邮站 (PPT Download)</summary></entry><entry xml:lang="en"><title type="html">Apache ServiceComb Accept Code Donation From NewCapec Institute</title><link href="/docs/servicecomb-accept-newcapec-institute-code-donation/" rel="alternate" type="text/html" title="Apache ServiceComb Accept Code Donation From NewCapec Institute" /><published>2019-11-07T00:00:00+08:00</published><updated>2019-11-07T09:24:43+08:00</updated><id>/docs/servicecomb-accept-newcapec-institute-code-donation</id><content type="html" xml:base="/docs/servicecomb-accept-newcapec-institute-code-donation/"><p><a href="https://github.com/apache/servicecomb-toolkit">ServiceComb Toolkit</a> recently recieved a code donation(<a href="https://github.com/NewCapec-Institute/oas-validator">oas-validator</a>) from <a href="https://github.com/orgs/NewCapec-Institute/dashboard">NewCapec Institute</a>, oas-validator provides OpenAPI V3 style and compatiblity check functionalities。Related links：</p> |
| |
| <ul> |
| <li><a href="https://lists.apache.org/thread.html/062cf6e67add1061aad3b106543842a8ac95959da8cd45bf2f88d597@%3Cdev.servicecomb.apache.org%3E">Donation acceptance vote</a></li> |
| <li><a href="https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html">IP Clearance Status</a></li> |
| <li><a href="https://github.com/apache/servicecomb-toolkit/pull/40">Code import PR</a></li> |
| </ul> |
| |
| <p>ServiceComb community will complete the integration work as soon as possible, provide more helpful functionalities to developers.</p></content><author><name>Qian Jia</name><email>chanjarster@gmail.com</email><uri>https://github.com/chanjarster</uri></author><category term="microservice" /><summary type="html">Apache ServiceComb Accept Code Donation From NewCapec Institute</summary></entry><entry xml:lang="cn"><title type="html">Apache ServiceComb社区接受新开普软件研究院的代码捐赠</title><link href="/cn/docs/servicecomb-accept-newcapec-institute-code-donation/" rel="alternate" type="text/html" title="Apache ServiceComb社区接受新开普软件研究院的代码捐赠" /><published>2019-10-29T00:00:00+08:00</published><updated>2019-10-29T10:24:43+08:00</updated><id>/cn/docs/servicecomb-accept-newcapec-institute-code-donation</id><content type="html" xml:base="/cn/docs/servicecomb-accept-newcapec-institute-code-donation/"><p><a href="https://github.com/apache/servicecomb-toolkit">ServiceComb Toolkit</a>项目收到来自<a href="https://github.com/orgs/NewCapec-Institute/dashboard">新开普软件研究院</a>捐赠的<a href="https://github.com/NewCapec-Institute/oas-validator">OAS Validator</a>，该工具提供OpenAPI V3合规性检查和兼容性校验等能力。相关链接：</p> |
| |
| <ul> |
| <li><a href="https://lists.apache.org/thread.html/062cf6e67add1061aad3b106543842a8ac95959da8cd45bf2f88d597@%3Cdev.servicecomb.apache.org%3E">社区接受捐赠投票</a></li> |
| <li><a href="https://incubator.apache.org/ip-clearance/servicecomb-oas-validator.html">IP Clearance Status</a></li> |
| <li><a href="https://github.com/apache/servicecomb-toolkit/pull/40">代码导入PR</a></li> |
| </ul> |
| |
| <p>后续社区将尽快完成整合工作，给广大开发者提供更多帮助。</p></content><author><name>Qian Jia</name><email>chanjarster@gmail.com</email><uri>https://github.com/chanjarster</uri></author><category term="微服务" /><summary type="html">Apache Servicecomb社区接受新开普软件研究院的代码捐赠</summary></entry><entry xml:lang="cn"><title type="html">使用OAS Validator帮助你规范OpenAPI Spec文档</title><link href="/cn/docs/use-oas-validator-help-standardize-oas-spec/" rel="alternate" type="text/html" title="使用OAS Validator帮助你规范OpenAPI Spec文档" /><published>2019-10-23T00:00:00+08:00</published><updated>2019-10-23T12:37:43+08:00</updated><id>/cn/docs/use-oas-validator-help-standardize-oas-spec</id><content type="html" xml:base="/cn/docs/use-oas-validator-help-standardize-oas-spec/"><h2 id="使用oas-validator规范你的openapi-spec文档">使用OAS Validator规范你的OpenAPI Spec文档</h2> |
| |
| <p>当前主流的开发RESTful API的做法有两种：Code First和Contract First。Code First指先写代码，然后生成Contract，而Contract First则是先写Contract再写代码实现。</p> |
| |
| <p>两种做法各有利弊，Code First可以让开发人员先写接口实现，然后利用工具反向生成Contract，优点是快速开发，并能保证接口实现与Contract保证一致，缺点是Contract太过易变容易导致下游应用故障。Contract First则可以让Contract的变动受控，保证下游应用的稳定性，缺点是需要人工来保证接口实现与Contact的一致性，具有一定难度。</p> |
| |
| <p>对于如何规范管理Contract，新开普软件研究院开源的<a href="https://github.com/NewCapec-Institute/oas-validator">OAS Validator[1]</a>提供了一些思路，下面简单介绍。</p> |
| |
| <h3 id="合规性校验">合规性校验</h3> |
| |
| <p>OAS Validator支持对使用<a href="https://github.com/OAI/OpenAPI-Specification">OpenAPI V3[2]</a>编写的Contract文档做合规性校验（也可称之为风格校验）。</p> |
| |
| <p>在一个微服务架构的系统中，提供RESTful API的组件可能会有很多个，并且由不同开发人员/团队开发，那么在使用这些接口的时候有一个很自然的需求就是希望这些接口（或接口文档）的风格是一致的。OAS Validator的合规性校验做的就是这部分工作。下面举例说明怎么使用合规性校验功能：</p> |
| |
| <ol> |
| <li>到 https://github.com/NewCapec-Institute/oas-validator clone下代码</li> |
| <li>然后 <code class="highlighter-rouge">mvn clean install</code>打包</li> |
| <li>到<code class="highlighter-rouge">oas-validator-web/target</code>目录下执行<code class="highlighter-rouge">java -jar oas-validator-web-exec.jar</code>启动OAS Validator Web</li> |
| <li>访问 http://localhost:8080，进入合规性校验功能</li> |
| <li>把 <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/examples/v3.0/petstore.yaml">petstore.yaml</a> 内容贴到文本框中然后点击校验得到结果：</li> |
| </ol> |
| |
| <pre><code class="language-txt">$.tags : 至少提供一个 |
| $.openapi : 必须&gt;=3.0.2 |
| $.components.schemas.'Pet'.title : 必须提供 |
| $.components.schemas.'Pet'.properties.'id'.title : 必须提供 |
| $.components.schemas.'Pet'.properties.'name'.title : 必须提供 |
| $.components.schemas.'Pet'.properties.'tag'.title : 必须提供 |
| $.components.schemas.'Error'.title : 必须提供 |
| $.components.schemas.'Error'.properties.'code'.title : 必须提供 |
| $.components.schemas.'Error'.properties.'message'.title : 必须提供 |
| $.info.description : 必须提供 |
| $.paths./pets.get.tags[0] : 不在$.tags所定义的范围内 |
| $.paths./pets.get.responses.200.headers.'x-next' : 必须为upper hyphen case |
| $.paths./pets.post.tags[0] : 不在$.tags所定义的范围内 |
| $.paths./pets/{petId}.get.tags[0] : 不在$.tags所定义的范围内 |
| </code></pre> |
| |
| <p>下面是功能截图：</p> |
| |
| <p><img src="/assets/images/2019-10-23-use-oas-validator-help-standardize-oas-spec/oas-validator-1.png" alt="图1 合规性校验" class="align-center" /></p> |
| |
| <p>下面举例解释检查报告的意思：</p> |
| |
| <p><code class="highlighter-rouge">$.components.schemas.'Pet'.title : 必须提供</code>，前面一段是<a href="https://github.com/json-path/JsonPath">JsonPath[3]</a>，用来描述出问题的元素/属性的位置，“必须提供”则的意思是没有填写该属性。如下图：</p> |
| |
| <p><img src="/assets/images/2019-10-23-use-oas-validator-help-standardize-oas-spec/oas-validator-2.png" alt="图2 合规性校验示例" class="align-center" /></p> |
| |
| <p><code class="highlighter-rouge">title</code>是一个文档性字段，没有它虽然不影响接口的语义，但是对于下游应用的开发者来说没有它会造成理解上的困难，因此在这里我们把它设定为必填。</p> |
| |
| <p>再来看这一条报告 <code class="highlighter-rouge">$.paths./pets.get.responses.200.headers.'x-next' : 必须为upper hyphen case</code>，同样前面是JsonPath，告诉你该属性应该为Upper Hyphen Case，正确的写法应该是<code class="highlighter-rouge">X-Next</code>。和<code class="highlighter-rouge">title</code>属性一样Header的大小写不是一个技术问题，但是统一的大小写风格能够让下游应用的开发人员更舒适，从而有更少的Bug。</p> |
| |
| <h3 id="兼容性校验">兼容性校验</h3> |
| |
| <p>不管你是采用Code First还是Contract First，Contract的变动不可避免，那么如何保证变化后的Contract能够对下游应用向下兼容就成了不可回避的问题。这个问题的具体描述就是根据V1.0 Contract开发的下游应用是否依然能够与根据V1.1 Contract实现的接口正确交互。</p> |
| |
| <p>OAS Validator提供了这种兼容性校验，当然同样只支持OpenAPI V3文档。下面举例说明如何使用这一功能：</p> |
| |
| <p>我们先提供一个v1.0的OAS Spec：</p> |
| |
| <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">openapi</span><span class="pi">:</span> <span class="s2">"</span><span class="s">3.0.0"</span> |
| <span class="na">info</span><span class="pi">:</span> |
| <span class="na">version</span><span class="pi">:</span> <span class="m">1.0</span> |
| <span class="na">title</span><span class="pi">:</span> <span class="s">Swagger Petstore</span> |
| <span class="na">paths</span><span class="pi">:</span> |
| <span class="s">/pets/{petId}</span><span class="pi">:</span> |
| <span class="na">get</span><span class="pi">:</span> |
| <span class="na">operationId</span><span class="pi">:</span> <span class="s">showPetById</span> |
| <span class="na">tags</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="s">pets</span> |
| <span class="na">parameters</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">petId</span> |
| <span class="na">in</span><span class="pi">:</span> <span class="s">path</span> |
| <span class="na">required</span><span class="pi">:</span> <span class="no">true</span> |
| <span class="na">schema</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">string</span> |
| <span class="na">responses</span><span class="pi">:</span> |
| <span class="s1">'</span><span class="s">200'</span><span class="pi">:</span> |
| <span class="na">description</span><span class="pi">:</span> <span class="s">Expected response to a valid request</span> |
| <span class="na">content</span><span class="pi">:</span> |
| <span class="s">application/json</span><span class="pi">:</span> |
| <span class="na">schema</span><span class="pi">:</span> |
| <span class="s">$ref</span><span class="pi">:</span> <span class="s2">"</span><span class="s">#/components/schemas/Pet"</span> |
| <span class="na">components</span><span class="pi">:</span> |
| <span class="na">schemas</span><span class="pi">:</span> |
| <span class="na">Pet</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">object</span> |
| <span class="na">required</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="s">id</span> |
| <span class="pi">-</span> <span class="s">name</span> |
| <span class="na">properties</span><span class="pi">:</span> |
| <span class="na">id</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">integer</span> |
| <span class="na">format</span><span class="pi">:</span> <span class="s">int64</span> |
| <span class="na">name</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">string</span> |
| </code></pre></div></div> |
| |
| <p>再写一个v1.1的OAS Spec，添加了一个query参数<code class="highlighter-rouge">name</code>：</p> |
| |
| <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">openapi</span><span class="pi">:</span> <span class="s2">"</span><span class="s">3.0.0"</span> |
| <span class="na">info</span><span class="pi">:</span> |
| <span class="na">version</span><span class="pi">:</span> <span class="m">1.1</span> |
| <span class="na">title</span><span class="pi">:</span> <span class="s">Swagger Petstore</span> |
| <span class="na">paths</span><span class="pi">:</span> |
| <span class="s">/pets/{petId}</span><span class="pi">:</span> |
| <span class="na">get</span><span class="pi">:</span> |
| <span class="na">operationId</span><span class="pi">:</span> <span class="s">showPetById</span> |
| <span class="na">tags</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="s">pets</span> |
| <span class="na">parameters</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">petId</span> |
| <span class="na">in</span><span class="pi">:</span> <span class="s">path</span> |
| <span class="na">required</span><span class="pi">:</span> <span class="no">true</span> |
| <span class="na">schema</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">string</span> |
| <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">name</span> |
| <span class="na">in</span><span class="pi">:</span> <span class="s">query</span> |
| <span class="na">required</span><span class="pi">:</span> <span class="no">true</span> |
| <span class="na">schema</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">string</span> |
| <span class="na">responses</span><span class="pi">:</span> |
| <span class="s1">'</span><span class="s">200'</span><span class="pi">:</span> |
| <span class="na">description</span><span class="pi">:</span> <span class="s">Expected response to a valid request</span> |
| <span class="na">content</span><span class="pi">:</span> |
| <span class="s">application/json</span><span class="pi">:</span> |
| <span class="na">schema</span><span class="pi">:</span> |
| <span class="s">$ref</span><span class="pi">:</span> <span class="s2">"</span><span class="s">#/components/schemas/Pet"</span> |
| <span class="na">components</span><span class="pi">:</span> |
| <span class="na">schemas</span><span class="pi">:</span> |
| <span class="na">Pet</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">object</span> |
| <span class="na">required</span><span class="pi">:</span> |
| <span class="pi">-</span> <span class="s">id</span> |
| <span class="pi">-</span> <span class="s">name</span> |
| <span class="na">properties</span><span class="pi">:</span> |
| <span class="na">id</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">integer</span> |
| <span class="na">format</span><span class="pi">:</span> <span class="s">int64</span> |
| <span class="na">name</span><span class="pi">:</span> |
| <span class="na">type</span><span class="pi">:</span> <span class="s">string</span> |
| </code></pre></div></div> |
| |
| <p>然后同样打开OAS Validator Web，进入“兼容性校验”功能，在左侧贴上v1.0在右侧贴上v1.1，点击校验得到结果：</p> |
| |
| <pre><code class="language-txt">$.paths./pets/{petId}.get.parameters[1].required : [name=name,in=query]:仅允许新增required=false的parameter |
| </code></pre> |
| |
| <p>这个报告的意思是新增的query参数<code class="highlighter-rouge">name</code>是必填的，这种做法不向下兼容。仔细想想是不是的确如此？</p> |
| |
| <h3 id="总结">总结</h3> |
| |
| <p>关于OAS Validator的详细文档可见Github。需要注意的是，目前校验规则还不能配置，但是在代码层面提供了接口供扩展，你可以根据自己的需求写一个自己的合规性校验器。</p> |
| |
| <p>同时OAS Validator正在请求捐赠到<a href="https://github.com/apache/servicecomb-toolkit">Servicecomb Toolkit[4]</a>项目，流程结束后会尽快将其整合到Servicecomb Toolkit中希望能够为广大开发者带来帮助。</p> |
| |
| <p>最后，欢迎开发者朋友们加入ServiceComb社区，一起做些有意思的事情。<a href="http://servicecomb.incubator.apache.org/cn/docs/join_the_community/">加入社区方法[5]</a></p> |
| |
| <h3 id="参考资料">参考资料</h3> |
| |
| <p>[1] OAS Validator https://github.com/NewCapec-Institute/oas-validator</p> |
| |
| <p>[2] OpenAPI V3 https://github.com/OAI/OpenAPI-Specification</p> |
| |
| <p>[3] JsonPath https://github.com/json-path/JsonPath</p> |
| |
| <p>[4] Servicecomb Toolkit https://github.com/apache/servicecomb-toolkit</p> |
| |
| <p>[5] 加入Servicecomb社区 http://servicecomb.incubator.apache.org/cn/docs/join_the_community/</p></content><author><name>Qian Jia</name><email>chanjarster@gmail.com</email><uri>https://github.com/chanjarster</uri></author><category term="微服务" /><summary type="html">本文将介绍如何规范你的OpenAPI Spec文档</summary></entry><entry xml:lang="cn"><title type="html">Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT Download)</title><link href="/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report/" rel="alternate" type="text/html" title="Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT Download)" /><published>2019-09-20T00:00:00+08:00</published><updated>2019-09-23T17:18:43+08:00</updated><id>/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report</id><content type="html" xml:base="/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report/"><p>北京时间2019年09月20日，Apache ServiceComb社区在中国上海世博中心举办的华为全链接大会组织了微服务同场活动 Apache ServiceComb Meetup，并圆满落下帷幕。</p> |
| |
| <p>本次活动邀请了Apache基金会主席、Apache孵化器项目管理委员会主席、Apache Member、Apache Committer、华为云PaaS团队架构师，携手为大家分享了Apache基金会介绍、Apache 孵化器的运作、ServiceComb的Apache孵化之路分享、Apache ServiceComb：微服务创新项目解读、华为云微服务工具解放开发者等诸多微服务技术及经验，ServiceComb社区也重磅发布了一系列解决用户应用微服务化痛点的创新新品。</p> |
| |
| <p><strong>Session 1: 《Apache软件基金会开源开发详解》</strong></p> |
| |
| <p>Apache软件基金会是全球最大的开源基金会，目前拥有300多个开源项目，涵盖大数据、云计算、服务器和Web框架、构建管理、内容管理、物联网等众多领域。基金会成员介绍了Apache软件基金会，开源社区治理原则，以及Apache孵化器的运作机制，并以华为捐赠的Apache ServiceComb孵化经历，分享Apache项目的孵化成功经验。</p> |
| |
| <p><a href="/assets/slides/20190920/The_Apache_Way_En.pdf">中文PDF下载</a> <a href="/assets/slides/20190920/EN/The_Apache_Way_En.pdf">英文PDF下载</a></p> |
| |
| <p><img src="/assets/images/hc2019/apache.jpg" alt="1" /></p> |
| |
| <p><strong>《Apache基金会介绍》</strong></p> |
| |
| <p><strong>Craig Russell, Apache基金会主席：</strong> 详细的介绍的Apache基金会的历史和现状及核心原则。</p> |
| |
| <p><img src="/assets/images/hc2019/introduction.jpg" alt="1" /></p> |
| |
| <p><strong>Justin Mclean, Apache孵化器项目管理委员会主席：</strong> 详解了Apache孵化器的运作机制以及Apache协议的特点，Apache项目的发布流程。</p> |
| |
| <p><strong>《Apache 孵化器的运作》</strong></p> |
| |
| <p><img src="/assets/images/hc2019/process.jpg" alt="1" /></p> |
| |
| <p><strong>姜宁，华为开源软件部技术专家，Apache软件基金会会员：</strong> 分享了华为捐赠的Apache ServiceComb成功孵化的实战经验，并对如何更好的发展开源社区给出了自己的总结和建议。</p> |
| |
| <p><strong>《ServiceComb的Apache孵化之路》</strong></p> |
| |
| <p><img src="/assets/images/hc2019/incubation.jpg" alt="1" /></p> |
| |
| <hr /> |
| <p><strong>Session 2: 《庖丁解牛： 微服务创新实践解放开发者》</strong></p> |
| |
| <p>Apache ServiceComb社区认真的听取了用户实施微服务架构中遇到的痛点。本主题前半部分将和大家分享这些获取到的痛点和为解决部分痛点而孵化项目，期望与用户一起思考如何去摆平微服务化实践中的难题。本主题后半部分将介绍与用户携手实践出真知的微服务化工具创新实践。</p> |
| |
| <p><img src="/assets/images/hc2019/servicecomb.jpg" alt="1" /></p> |
| |
| <p><strong>《Apache ServiceComb：微服务创新项目解读》</strong></p> |
| |
| <p><a href="/assets/slides/20190920/Apache_ServiceComb-Innovative_Microservices.pdf">中文PDF下载</a> <a href="/assets/slides/20190920/EN/Apache_ServiceComb-Innovative_Microservices.pdf">英文PDF下载</a></p> |
| |
| <p><strong>马彬，华为开源软件部架构师，Apache Committer：</strong> 解读ServiceComb社区针对用户痛点所推出的创新项目架构、roadmap及场景案例，包括:多语言运行环境、微服务契约工具、服务中心异构通信、分布式配置中心、微服务鉴权；同时向社区发出召集令，号召更多的兴趣爱好者投入开源社区贡献。</p> |
| |
| <p><img src="/assets/images/hc2019/innovative.jpg" alt="2" /></p> |
| |
| <hr /> |
| |
| <p><strong>《华为云微服务工具解放开发者》</strong></p> |
| |
| <p><a href="/assets/slides/20190920/HUAWEI_CLOUD_Microservice_Tool_Improves_Development_Efficiency.pdf">中文PDF下载</a> <a href="/assets/slides/20190920/EN/HUAWEI_CLOUD_Microservice_Tool_Improves_Development_Efficiency.pdf">英文PDF下载</a></p> |
| |
| <p><strong>王启军, 华为云PaaS团队架构师：</strong> 华为云微服务基于ServiceComb的实践，通过案例分享了微服务拆分工具，契约管理工具这2个开发者/用户关注度最高的微服务工具。</p> |
| |
| <p><img src="/assets/images/hc2019/efficiency.jpg" alt="4" /></p> |
| |
| <hr /> |
| |
| <p><strong>关于Apache ServiceComb 项目</strong>：</p> |
| |
| <p>ServiceComb Apache软件基金会孵化项目的主体代码由华为云捐赠，致力于帮助企业轻松构建云原生应用及传统企业业务快速微服务化，通过系列解决方案帮助用户快速开发微服务的同时实现对这些微服务应用的高效运维管理。它具有完整的微服务生态栈，无厂商锁定，当前遵循Apache Way进行孵化，已拥有如消费者云、云EI、云安全、云核等华为业务之外的一批非华为商用用户，且社区和开发者也日趋多样化。</p> |
| |
| <hr /> |
| <p><strong>如您有更多问题关于Aapche ServiceComb，欢迎您扫码或微信添加“ServiceComb小助手”，我们将认真对待您的每一个问题</strong> |
| <img src="/assets/images/QRcode.png" alt="1" /></p></content><author><name>Dean Lee</name></author><category term="microservice" /><category term="Meetup" /><summary type="html">Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT)</summary></entry><entry xml:lang="en"><title type="html">Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT Download)</title><link href="/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report/" rel="alternate" type="text/html" title="Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT Download)" /><published>2019-09-20T00:00:00+08:00</published><updated>2019-09-23T17:18:43+08:00</updated><id>/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report</id><content type="html" xml:base="/docs/Apache-ServiceComb-Meetup-2019-Shanghai-Report/"><p>On September 20, 2019, at the Shanghai World Expo Center in China, the Apache ServiceComb community held microservice Co-Located event at the HUAWEI CONNECT 2019, that concluded successfully.</p> |
| |
| <p>The event invited the chairman of the Apache Foundation, the chairman of the Apache Incubator Project Management Committee, Apache Member, Apache Committer, and Huawei Cloud PaaS team architect. They shared the “Apache Explained”, “The Apache Incubator”, “ServiceComb Incubating Journey”, “Apache ServiceComb-Innovative Microservices”, “HUAWEI CLOUD Microservice Tool Improves Development Efficiency”, etc. Many micro-service technologies and experience. ServiceComb community has also released a series of innovative new projects to assist user solve pain points of microservice.</p> |
| |
| <p><strong>Session 1: The Apache Way</strong></p> |
| |
| <p>The Apache Software Foundation is the world’s largest open source foundation and currently has more than 300 open source projects covering big data, cloud computing, server and web frameworks, build management, content management, and the Internet of Things. Foundation members introduced the Apache Software Foundation, open source community governance principles, and the operating mechanism of the Apache incubator, and shared the Apache project’s successful incubation experience with Huawei-funded project Apache ServiceComb.</p> |
| |
| <p><a href="/assets/slides/20190920/EN/The_Apache_Way_En.pdf">PDF Download</a></p> |
| |
| <p><img src="/assets/images/hc2019/apache.jpg" alt="1" /></p> |
| |
| <p><strong>Apache Explained</strong></p> |
| |
| <p><strong>Craig Russell, Chairman of the ASF, Apache Software Foundation:</strong> A detailed introduction to the history and current state of the Apache Foundation and its core principles.</p> |
| |
| <p><img src="/assets/images/hc2019/introduction.jpg" alt="1" /></p> |
| |
| <p><strong>The Apache Incubator</strong></p> |
| |
| <p><strong>Justin Mclean, Chairman of the Apache IPMC, Apache Software Foundation:</strong> Explains the operating mechanism of the Apache incubator and the features of the Apache protocol, and the release process for the Apache project.</p> |
| |
| <p><img src="/assets/images/hc2019/process.jpg" alt="1" /></p> |
| |
| <p><strong>ServiceComb Incubating Journey</strong></p> |
| |
| <p><strong>Willem Jiang, Huawei Open Source Expert, ASF Member:</strong> Shared the practical experience of Huawei’s donated Apache ServiceComb successful incubation, and gave its own summary and suggestions on how to better develop the open source community.</p> |
| |
| <p><img src="/assets/images/hc2019/incubation.jpg" alt="1" /></p> |
| |
| <hr /> |
| <p><strong>Session 2: Innovative Microservices for More Efficient Development</strong></p> |
| |
| <p>The Apache ServiceComb community has listened carefully to the pain points encountered by users implementing the microservices architecture. The first half of this topic will share these pain points and incubate projects to solve some pain points. I hope to discuss with users how to solve the problems in micro-service practice. The second half of this topic will introduce the micro-service tool innovation practices that work hand-in-hand with users.</p> |
| |
| <p><img src="/assets/images/hc2019/servicecomb.jpg" alt="1" /></p> |
| |
| <p><strong>Apache ServiceComb-Innovative Microservices</strong></p> |
| |
| <p><a href="/assets/slides/20190920/EN/Apache_ServiceComb-Innovative_Microservices.pdf">PDF Download</a></p> |
| |
| <p><strong>Ma Bin, Huawei Open Source Architect, Apache Committer:</strong> Interpret the innovative project architecture, roadmap and scenario cases launched by the ServiceComb community for user pain points, including: multi-language operating environment, micro-service contract tools, heterogeneous communication in service centers, distributed configuration centers, micro-service authentication; The convening order calls for more interested fans to contribute to the open source community.</p> |
| |
| <p><img src="/assets/images/hc2019/innovative.jpg" alt="2" /></p> |
| |
| <hr /> |
| |
| <p><strong>HUAWEI CLOUD Microservice Tool Improves Development Efficiency</strong></p> |
| |
| <p><a href="/assets/slides/20190920/EN/HUAWEI_CLOUD_Microservice_Tool_Improves_Development_Efficiency.pdf">PDF Download</a></p> |
| |
| <p><strong>Wang Qijun, Huawei Cloud PaaS Architect:</strong> Based on the practice of ServiceComb, Huawei Cloud Micro Service shared the micro-service splitting tools and contract management tools, which are the two developers/users with the highest attention.</p> |
| |
| <p><img src="/assets/images/hc2019/efficiency.jpg" alt="4" /></p> |
| |
| <hr /> |
| |
| <p><strong>About the Apache ServiceComb</strong>：</p> |
| |
| <p>Apache ServiceComb, the main code of the Apache Software Foundation Incubation Project, donated by Huawei Cloud, is dedicated to helping enterprises easily build cloud native applications and traditional enterprise business rapid micro-services, helping users quickly develop micro-services through a series of solutions to achieve these Efficient operation and maintenance management of microservice applications. It has a complete micro-service ecological stack, no vendor lock-in, currently incubating with Apache Way, and has a number of non-Huawei commercial users outside of Huawei’s business such as consumer cloud, cloud EI, cloud security, cloud core, and community. And developers are also increasingly diverse.</p> |
| |
| <hr /> |
| <p><strong>more questions, welcome to scan the QR code or WeChat to add “ServiceComb Assistant</strong> |
| <img src="/assets/images/QRcode.png" alt="1" /></p></content><author><name>Mabin</name></author><category term="microservice" /><category term="Meetup" /><summary type="html">Apache ServiceComb Meetup -Shanghai 2019.09.20 Report (PPT)</summary></entry><entry xml:lang="cn"><title type="html">如何给微服务架构的项目做验收测试？</title><link href="/cn/docs/how-to-do-microservice-accept-test/" rel="alternate" type="text/html" title="如何给微服务架构的项目做验收测试？" /><published>2019-07-04T00:00:00+08:00</published><updated>2019-07-04T10:37:43+08:00</updated><id>/cn/docs/how-to-do-microservice-accept-test</id><content type="html" xml:base="/cn/docs/how-to-do-microservice-accept-test/"><h3 id="如何给微服务架构的项目做验收测试">如何给微服务架构的项目做验收测试？</h3> |
| |
| <p>基于微服务架构的应用相对于单体架构的应用而言在验收测试阶段具有以下挑战：</p> |
| |
| <ol> |
| <li>复数的服务增加了测试环境搭建的难度</li> |
| <li>各种异常情况的模拟变得困难，基于Mock的测试方式无法对整个调用链路作异常模拟，进而使得对整体架构的健壮性测试变得困难</li> |
| <li>基于成本和效率的原因，测试工作已经不适合通过人工完成</li> |
| </ol> |
| |
| <p>我们认为对基于微服务架构的应用的验收测试应该具有以下特征：</p> |
| |
| <ol> |
| <li>自动化、可重复、易于和CI工具集成</li> |
| <li>能够在测试运行时修改服务的行为</li> |
| </ol> |
| |
| <p>下面将就一个Demo来介绍如何利用 <a href="https://www.docker.com/">Docker [1]</a>、<a href="https://cucumber.io/">Cucumber [2]</a>、<a href="https://byteman.jboss.org/">Byteman [3]</a>、<a href="https://dmp.fabric8.io/">Fabric8 docker-maven-plugin [4]</a>、<a href="https://github.com/spotify/dockerfile-maven">Spotify dockerfile-maven-plugin [5]</a>达成以上目标。</p> |
| |
| <h3 id="demo介绍">Demo介绍</h3> |
| |
| <p>一共有两个服务Product Service（商品服务）和Product Price Service（商品价格服务），Product Service提供了一个查询接口用于获得商品信息及其价格信息的组合结果，这相当于跨服务的SQL JOIN。</p> |
| |
| <p>下面是Product的Schema：</p> |
| |
| <div class="language-json highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{</span><span class="w"> |
| </span><span class="nl">"id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"name"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"description"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="w"> |
| </span><span class="p">}</span><span class="w"> |
| </span></code></pre></div></div> |
| |
| <p>下面是ProductPrice的Schema：</p> |
| |
| <div class="language-json highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{</span><span class="w"> |
| </span><span class="nl">"id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"price"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;number&gt;"</span><span class="w"> |
| </span><span class="p">}</span><span class="w"> |
| </span></code></pre></div></div> |
| |
| <p>Product Service返回的Schema则是：</p> |
| |
| <div class="language-json highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{</span><span class="w"> |
| </span><span class="nl">"products"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w"> |
| </span><span class="p">{</span><span class="w"> |
| </span><span class="nl">"id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"name"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"description"</span><span class="p">:</span><span class="w"> </span><span class="s2">"&lt;string&gt;"</span><span class="p">,</span><span class="w"> |
| </span><span class="nl">"price"</span><span class="p">:</span><span class="w"> </span><span class="err">&lt;number&gt;</span><span class="w"> |
| </span><span class="p">}</span><span class="w"> |
| </span><span class="p">]</span><span class="w"> |
| </span><span class="p">}</span><span class="w"> |
| </span></code></pre></div></div> |
| |
| <p>该接口的实现逻辑是：</p> |
| |
| <ol> |
| <li>Product Service本地查询得到Product List</li> |
| <li>Product Service调用Product Price Service接口得到ProductPrice List</li> |
| <li>拼装结果</li> |
| </ol> |
| |
| <p>此外还有一个要求，当Product Price Service出现异常时，Product Service依然要能够返回结果，只不过<code class="highlighter-rouge">price</code>字段为<code class="highlighter-rouge">null</code>，即无论如何Product Service都要能够返回结果。</p> |
| |
| <h3 id="实现步骤">实现步骤</h3> |
| |
| <h4 id="构建docker-image">构建Docker Image</h4> |
| |
| <p>为了能够便利地搭建测试环境，我们需要先为Product Servcie和Product Price Service构建Docker Image。利用<a href="https://github.com/spotify/dockerfile-maven">Spotify dockerfile-maven-plugin [5]</a>可以很方便地做到这一点，它没有引入额外的概念，只要你会写<a href="https://docs.docker.com/engine/reference/builder/">Dockerfile [6]</a>就行。我们在Product Service和Producer Price Service的<code class="highlighter-rouge">pom.xml</code>中添加类似以下的配置：</p> |
| |
| <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt">&lt;plugin&gt;</span> |
| <span class="nt">&lt;groupId&gt;</span>com.spotify<span class="nt">&lt;/groupId&gt;</span> |
| <span class="nt">&lt;artifactId&gt;</span>dockerfile-maven-plugin<span class="nt">&lt;/artifactId&gt;</span> |
| <span class="nt">&lt;version&gt;</span>${dockerfile-maven-plugin.version}<span class="nt">&lt;/version&gt;</span> |
| <span class="nt">&lt;configuration&gt;</span> |
| <span class="nt">&lt;repository&gt;</span>msat-${project.artifactId}<span class="nt">&lt;/repository&gt;</span> |
| <span class="nt">&lt;tag&gt;</span>${project.version}<span class="nt">&lt;/tag&gt;</span> |
| <span class="nt">&lt;buildArgs&gt;</span> |
| <span class="nt">&lt;JAR_FILE&gt;</span>${project.build.finalName}-exec.${project.packaging}<span class="nt">&lt;/JAR_FILE&gt;</span> |
| <span class="nt">&lt;/buildArgs&gt;</span> |
| <span class="nt">&lt;/configuration&gt;</span> |
| <span class="nt">&lt;executions&gt;</span> |
| <span class="nt">&lt;execution&gt;</span> |
| <span class="nt">&lt;id&gt;</span>build<span class="nt">&lt;/id&gt;</span> |
| <span class="nt">&lt;phase&gt;</span>package<span class="nt">&lt;/phase&gt;</span> |
| <span class="nt">&lt;goals&gt;</span> |
| <span class="nt">&lt;goal&gt;</span>build<span class="nt">&lt;/goal&gt;</span> |
| <span class="nt">&lt;/goals&gt;</span> |
| <span class="nt">&lt;/execution&gt;</span> |
| <span class="nt">&lt;/executions&gt;</span> |
| <span class="nt">&lt;/plugin&gt;</span> |
| </code></pre></div></div> |
| |
| <p>并且提供了Dockerfile：</p> |
| |
| <pre><code class="language-txt">FROM openjdk:8-jre-alpine |
| ARG JAR_FILE |
| ENV JAR_FILE=${JAR_FILE} |
| RUN mkdir /maven |
| COPY target/${JAR_FILE} /maven |
| COPY target/lib/byteman.jar /maven |
| ENTRYPOINT java $JAVA_OPTS -jar /maven/$JAR_FILE |
| EXPOSE 8080 |
| </code></pre> |
| |
| <p>注意我们在Image中添加了byteman.jar，利用它我们可以在运行时修改程序的行为。</p> |
| |
| <h4 id="编写验收测试脚本">编写验收测试脚本</h4> |
| |
| <p>我们新建一个验收测试的Maven项目，然后使用<a href="https://cucumber.io/">Cucumber [2]</a>编写了以下两个场景的验收测试脚本：</p> |
| |
| <p>正常情况：</p> |
| |
| <pre><code class="language-txt">Feature: List product information with price |
| |
| Scenario: Everything is good |
| Given Product Service is up and running |
| And Product Price Service is up and running |
| |
| When User query product list |
| |
| Then Get following products |
| |
| | id | name | description | price | |
| | animal-1 | dog | woof woof | 1000 | |
| | animal-2 | duck | quack quack | 40 | |
| | animal-3 | fox | what does the fox say? | 5000 | |
| </code></pre> |
| |
| <p>这个脚本的大致意思是在Product Service和Product Price Service都启动的情况下，当用户查询Product信息时，我们会得到上述表格中的结果。</p> |
| |
| <p>Product Price Service异常情况：</p> |
| |
| <pre><code class="language-txt">Feature: List product information with price |
| |
| Scenario: Product Price Service throws exception when being queried |
| Given Product Service is up and running |
| And Product Price Service is up and running |
| |
| Given Install the byteman script product_price_exception.btm to Product Price Service |
| |
| When User query product list |
| |
| Then Get following products |
| |
| | id | name | description | price | |
| | animal-1 | dog | woof woof | | |
| | animal-2 | duck | quack quack | | |
| | animal-3 | fox | what does the fox say? | | |
| </code></pre> |
| |
| <p>注意到我们在这里使用了<a href="https://byteman.jboss.org/">Byteman [3]</a>注入了异常情况给Product Price Service：</p> |
| |
| <pre><code class="language-txt">Given Install the byteman script product_price_exception.btm to Product Price Service |
| </code></pre> |
| |
| <p><code class="highlighter-rouge">product_price_exception.btm</code>的内容是这样的：</p> |
| |
| <pre><code class="language-txt">RULE throw exception |
| CLASS me.chanjar.msat.productprice.FakeProductPriceRepository |
| METHOD listAll |
| AT ENTRY |
| IF TRUE |
| DO debug("throw RuntimeException here"), |
| throw new RuntimeException("Product Repository Error!") |
| ENDRULE |
| </code></pre> |
| |
| <p>意思是在调用<code class="highlighter-rouge">FakeProductPriceRepository.listAll</code>方法时抛出异常，注意这样做并没有修改Product Price Service的源码，而是在运行时修改了它的逻辑。</p> |
| |
| <p>接下来我们为上面的验收测试脚本实现逻辑（下面代码与实际上有所不同，这是为了尽量使得代码篇幅精简）：</p> |
| |
| <div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="kd">public</span> <span class="kd">class</span> <span class="nc">Stepdefs</span> <span class="o">{</span> |
| |
| <span class="kd">private</span> <span class="nc">List</span><span class="o">&lt;</span><span class="nc">Map</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">,</span> <span class="nc">String</span><span class="o">&gt;&gt;</span> <span class="n">answer</span><span class="o">;</span> |
| |
| <span class="nd">@Given</span><span class="o">(</span><span class="s">"^Product Service is up and running$"</span><span class="o">)</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">productServiceIsUpAndRunning</span><span class="o">()</span> <span class="o">{</span> |
| <span class="n">probe</span><span class="o">(</span><span class="s">"Product Service"</span><span class="o">,</span> <span class="no">PRODUCT_ADDRESS</span><span class="o">);</span> |
| <span class="o">}</span> |
| |
| <span class="nd">@And</span><span class="o">(</span><span class="s">"^Product Price Service is up and running$"</span><span class="o">)</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">productPriceServiceIsUpAndRunning</span><span class="o">()</span> <span class="o">{</span> |
| <span class="n">probe</span><span class="o">(</span><span class="s">"Product Price Service"</span><span class="o">,</span> <span class="no">PRODUCT_PRICE_ADDRESS</span><span class="o">);</span> |
| <span class="n">clearBytemanScript</span><span class="o">();</span> |
| <span class="o">}</span> |
| |
| <span class="nd">@When</span><span class="o">(</span><span class="s">"^User query product list$"</span><span class="o">)</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">queryProductList</span><span class="o">()</span> <span class="o">{</span> |
| <span class="n">answer</span> <span class="o">=</span> <span class="n">given</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">when</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">get</span><span class="o">(</span><span class="no">PRODUCT_ADDRESS</span> <span class="o">+</span> <span class="s">"/products"</span><span class="o">)</span> |
| <span class="o">.</span><span class="na">then</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">statusCode</span><span class="o">(</span><span class="n">is</span><span class="o">(</span><span class="mi">200</span><span class="o">))</span> |
| <span class="o">.</span><span class="na">extract</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">body</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">jsonPath</span><span class="o">()</span> |
| <span class="o">.</span><span class="na">getList</span><span class="o">(</span><span class="s">"products"</span><span class="o">,</span> <span class="nc">Map</span><span class="o">.</span><span class="na">class</span><span class="o">);</span> |
| <span class="o">}</span> |
| |
| <span class="nd">@Given</span><span class="o">(</span><span class="s">"^Install the byteman script ([A-Za-z0-9_\\.]+) to Product Price Service$"</span><span class="o">)</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">injectExceptionIntoProductPriceService</span><span class="o">(</span><span class="nc">String</span> <span class="n">bytemanScript</span><span class="o">)</span> <span class="kd">throws</span> <span class="nc">Exception</span> <span class="o">{</span> |
| <span class="n">injectBytemanScript</span><span class="o">(</span><span class="s">"target/test-classes/"</span> <span class="o">+</span> <span class="n">bytemanScript</span><span class="o">);</span> |
| <span class="o">}</span> |
| |
| <span class="nd">@Then</span><span class="o">(</span><span class="s">"^Get following products$"</span><span class="o">)</span> |
| <span class="kd">public</span> <span class="kt">void</span> <span class="nf">compareResult</span><span class="o">(</span><span class="nc">List</span><span class="o">&lt;</span><span class="nc">Map</span><span class="o">&lt;</span><span class="nc">String</span><span class="o">,</span> <span class="nc">String</span><span class="o">&gt;&gt;</span> <span class="n">expected</span><span class="o">)</span> <span class="o">{</span> |
| <span class="n">assertThat</span><span class="o">(</span><span class="n">answer</span><span class="o">).</span><span class="na">containsExactlyInAnyOrderElementsOf</span><span class="o">(</span><span class="n">expected</span><span class="o">);</span> |
| <span class="o">}</span> |
| <span class="o">}</span> |
| </code></pre></div></div> |
| |
| <p>关于<a href="https://cucumber.io/">Cucumber [2]</a>和<a href="https://byteman.jboss.org/">Byteman [3]</a>的更详细的介绍可以见<a href="https://servicecomb.apache.org/cn/docs/saga_with_cucumber/">ServiceComb Saga使用Cucumber做验收测试源码分析 [7]</a>。</p> |
| |
| <h4 id="自动化搭建测试环境">自动化搭建测试环境</h4> |
| |
| <p>我们希望能够在Maven的<code class="highlighter-rouge">integration-test</code> 阶段搭建测试环境、执行上述验收测试脚本。在<code class="highlighter-rouge">pom.xml</code>中添加到<a href="https://dmp.fabric8.io/">Fabric8 docker-maven-plugin [4]</a>：</p> |
| |
| <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt">&lt;plugin&gt;</span> |
| <span class="nt">&lt;groupId&gt;</span>io.fabric8<span class="nt">&lt;/groupId&gt;</span> |
| <span class="nt">&lt;artifactId&gt;</span>docker-maven-plugin<span class="nt">&lt;/artifactId&gt;</span> |
| <span class="nt">&lt;configuration&gt;</span> |
| <span class="nt">&lt;showLogs&gt;</span>true<span class="nt">&lt;/showLogs&gt;</span> |
| <span class="nt">&lt;images&gt;</span> |
| <span class="nt">&lt;image&gt;</span> |
| <span class="nt">&lt;name&gt;</span>msat-product:${project.version}<span class="nt">&lt;/name&gt;</span> |
| <span class="nt">&lt;alias&gt;</span>msat-product<span class="nt">&lt;/alias&gt;</span> |
| <span class="nt">&lt;run&gt;</span> |
| <span class="nt">&lt;wait&gt;</span> |
| <span class="nt">&lt;log&gt;</span>Started [a-zA-Z]+ in [0-9.]+ seconds<span class="nt">&lt;/log&gt;</span> |
| <span class="nt">&lt;time&gt;</span>120000<span class="nt">&lt;/time&gt;</span> |
| <span class="nt">&lt;/wait&gt;</span> |
| <span class="nt">&lt;links&gt;</span> |
| <span class="nt">&lt;link&gt;</span>msat-product-price:msat-product-price<span class="nt">&lt;/link&gt;</span> |
| <span class="nt">&lt;/links&gt;</span> |
| <span class="nt">&lt;ports&gt;</span> |
| <span class="nt">&lt;port&gt;</span>product.port:8080<span class="nt">&lt;/port&gt;</span> |
| <span class="nt">&lt;/ports&gt;</span> |
| <span class="nt">&lt;/run&gt;</span> |
| <span class="nt">&lt;/image&gt;</span> |
| <span class="nt">&lt;image&gt;</span> |
| <span class="nt">&lt;name&gt;</span>msat-product-price:${project.version}<span class="nt">&lt;/name&gt;</span> |
| <span class="nt">&lt;alias&gt;</span>msat-product-price<span class="nt">&lt;/alias&gt;</span> |
| <span class="nt">&lt;run&gt;</span> |
| <span class="nt">&lt;env&gt;</span> |
| <span class="nt">&lt;JAVA_OPTS&gt;</span> |
| -Dorg.jboss.byteman.debug=true -Dorg.jboss.byteman.verbose=true |
| -javaagent:/maven/byteman.jar=port:9091,address:0.0.0.0,listener:true |
| <span class="nt">&lt;/JAVA_OPTS&gt;</span> |
| <span class="nt">&lt;/env&gt;</span> |
| <span class="nt">&lt;wait&gt;</span> |
| <span class="nt">&lt;log&gt;</span>Started [a-zA-Z]+ in [0-9.]+ seconds<span class="nt">&lt;/log&gt;</span> |
| <span class="nt">&lt;time&gt;</span>120000<span class="nt">&lt;/time&gt;</span> |
| <span class="nt">&lt;/wait&gt;</span> |
| <span class="nt">&lt;ports&gt;</span> |
| <span class="nt">&lt;port&gt;</span>product-price.port:8080<span class="nt">&lt;/port&gt;</span> |
| <span class="nt">&lt;port&gt;</span>product-price.byteman.port:9091<span class="nt">&lt;/port&gt;</span> |
| <span class="nt">&lt;/ports&gt;</span> |
| <span class="nt">&lt;/run&gt;</span> |
| <span class="nt">&lt;/image&gt;</span> |
| <span class="nt">&lt;/images&gt;</span> |
| <span class="nt">&lt;/configuration&gt;</span> |
| <span class="nt">&lt;executions&gt;</span> |
| <span class="nt">&lt;execution&gt;</span> |
| <span class="nt">&lt;id&gt;</span>start<span class="nt">&lt;/id&gt;</span> |
| <span class="nt">&lt;phase&gt;</span>pre-integration-test<span class="nt">&lt;/phase&gt;</span> |
| <span class="nt">&lt;goals&gt;</span> |
| <span class="nt">&lt;goal&gt;</span>start<span class="nt">&lt;/goal&gt;</span> |
| <span class="nt">&lt;/goals&gt;</span> |
| <span class="nt">&lt;/execution&gt;</span> |
| <span class="nt">&lt;execution&gt;</span> |
| <span class="nt">&lt;id&gt;</span>stop<span class="nt">&lt;/id&gt;</span> |
| <span class="nt">&lt;phase&gt;</span>post-integration-test<span class="nt">&lt;/phase&gt;</span> |
| <span class="nt">&lt;goals&gt;</span> |
| <span class="nt">&lt;goal&gt;</span>stop<span class="nt">&lt;/goal&gt;</span> |
| <span class="nt">&lt;/goals&gt;</span> |
| <span class="nt">&lt;/execution&gt;</span> |
| <span class="nt">&lt;/executions&gt;</span> |
| <span class="nt">&lt;/plugin&gt;</span> |
| </code></pre></div></div> |
| |
| <p>这样一来就能够在<code class="highlighter-rouge">pre-integration-test</code>阶段启动容器，在<code class="highlighter-rouge">post-integration-test</code>阶段销毁容器了。</p> |
| |
| <h4 id="take-a-run">Take a run</h4> |
| |
| <p>接下来只需要<code class="highlighter-rouge">mvn clean install</code>它就会：</p> |
| |
| <ol> |
| <li>构建： |
| <ol> |
| <li>构建Product Service项目，并为其构建Docker Image</li> |
| <li>构建Product Price Service项目，并为其构建Docker Image</li> |
| </ol> |
| </li> |
| <li>验收测试： |
| <ol> |
| <li>启动Product Service和Product Price Service的容器</li> |
| <li>执行验收测试脚本</li> |
| <li>销毁上述创建的容器</li> |
| </ol> |
| </li> |
| </ol> |
| |
| <p>如果你想自己试试可以下载<a href="https://github.com/chanjarster/microservice-acceptance-test-demo">本项目源码[8]</a>。</p> |
| |
| <p>欢迎开发者朋友们加入ServiceComb社区，一起做些有意思的事情。<a href="http://servicecomb.incubator.apache.org/cn/docs/join_the_community/">加入社区方法[9]</a></p> |
| |
| <h3 id="参考资料">参考资料</h3> |
| |
| <p>[1] Docker https://www.docker.com/</p> |
| |
| <p>[2] Cucumber https://cucumber.io/</p> |
| |
| <p>[3] Byteman https://byteman.jboss.org/</p> |
| |
| <p>[4] Fabric8 docker-maven-plugin https://dmp.fabric8.io/</p> |
| |
| <p>[5] Spotify dockerfile-maven-plugin https://github.com/spotify/dockerfile-maven</p> |
| |
| <p>[6] Dockerfile https://docs.docker.com/engine/reference/builder/</p> |
| |
| <p>[7] ServiceComb Saga使用Cucumber做验收测试源码分析 https://servicecomb.apache.org/cn/docs/saga_with_cucumber/</p> |
| |
| <p>[8] 本项目源码 https://github.com/chanjarster/microservice-acceptance-test-demo</p> |
| |
| <p>[9] 加入Servicecomb社区 http://servicecomb.incubator.apache.org/cn/docs/join_the_community/</p></content><author><name>Qian Jia</name><email>chanjarster@gmail.com</email><uri>https://github.com/chanjarster</uri></author><category term="微服务" /><summary type="html">本文将介绍如何给微服务架构的项目做验收测试</summary></entry><entry xml:lang="cn"><title type="html">Apache ServiceComb Meetup - Shanghai 2019.06.24 Report (PDF Download)</title><link href="/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-KubeCon+CloudNative+OSS-Report/" rel="alternate" type="text/html" title="Apache ServiceComb Meetup - Shanghai 2019.06.24 Report (PDF Download)" /><published>2019-07-02T00:00:00+08:00</published><updated>2019-07-02T12:26:28+08:00</updated><id>/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-KubeCon+CloudNative+OSS-Report</id><content type="html" xml:base="/cn/docs/Apache-ServiceComb-Meetup-2019-Shanghai-KubeCon+CloudNative+OSS-Report/"><p>北京时间2019年6月24日，Apache ServiceComb社区在中国上海世博中心举办的开源业界最负盛名的 KubeCon+CloudNativeCon+Open Source Summit 云原生会议组织了微服务同场活动 Apache ServiceComb Meetup，并圆满落下帷幕。</p> |
| |
| <p>本次活动邀请了Apache Member、Apache Committer、华为云云服务首席工程师、京东数科专家、全球Top10 IT服务提供商开发经理等各行业的资深从业者，携手为大家分享了Apache社区开发经验、企业级PaaS应对复杂网络拓补的案例、汽车品牌数字化营销系统微服务化实践、高性能服务间通信的优化技巧等诸多微服务技术及经验，ServiceComb社区也重磅发布了一系列解决用户应用微服务化痛点的创新新品。</p> |
| |
| <p>在企业向数字化和云化转型过程中，微服务是不二选择，然而它并不是银弹，企业在微服务化过程中会遇到诸多挑战，ServiceComb将继续紧密围绕社区用户和开发者，携手解决微服务痛点问题。</p> |
| |
| <p>秉承“将复杂留给自己，极简留给用户，提供一站式的微服务开源解决方案，致力于帮助企业、用户和开发者将应用轻松微服务化上云，实现对微服务应用的高效运维管理” 的发展理念，社区发起召集令，动员有志者加入社区，一起做点有意思的事情。</p> |
| |
| <p><img src="/assets/images/Community_Summoned_zh.png" alt="1" /></p> |
| |
| <hr /> |
| <p><strong>全场视频回顾:</strong> <a href="https://huaweicloud.bugu.mudu.tv/watch/ym1vkamp">链接</a></p> |
| |
| <hr /> |
| <p><strong>《ServiceComb开源这两年》</strong> <a href="/assets/slides/20190624/1_ServiceComb_Opensource_Way.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>姜宁</strong>，Apache软件基金会会员，华为开源能力中心技术专家，前红帽软件首席软件工程师，有十五年企业级开源中间件开发经验，有丰富的Java开发和使用经验，函数式编程爱好者。从2006年开始一直从事Apache开源中间件项目的开发工作，先后参与Apache CXF， Apache Camel，Apache ServiceMix以及Apache ServiceComb的开发。</p> |
| |
| <p><strong>摘要：</strong> ServiceComb正式开源已经两年了，在这两年中我们经历了代码首发时的激动，由0到1拓展社区的困惑，以及结识到结伴同行的小伙伴的快乐， 如今ServiceComb已经成长为Apache软件基金会顶级项目。本次演讲将总结回顾ServiceComb开源这两年的感悟与收获，希望能够帮助大家了解开源，参与开源，共创美好未来。</p> |
| |
| <hr /> |
| <p><strong>《汽车品牌的数字化营销系统微服务实践》</strong> <a href="/assets/slides/20190624/2_NTTDATA_Microservice_Practices.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>朱小卫</strong>，NTTDATA中国上海分公司Digital Marketing开发经理，15年+研发经验，丰富的电商、CRM等产品服务实践经验，近三年专注于汽车整车的数字化转型解决方案。</p> |
| |
| <p><strong>摘要：</strong> NTTDATA是全球Top10内的IT服务提供商，为汽车、制造、航空、零售、服装等行业提供全渠道整合跨渠道协同、个性化营销及服务、消费者洞察大数据分析等数字化营销解决方案，本主题主要分享NTTDATA向微服务化转型，打造集中化、标准化、智能化、便利化的汽车品牌数字营销平台，帮助企业灵活应对市场需求，支持数字营销快速、多样、变化的业务场景的实践。</p> |
| |
| <hr /> |
| <p><strong>《企业级PaaS中的微服务应用揭秘》</strong> <a href="/assets/slides/20190624/3_Enterprise_PaaS_Microservice_Pratices.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>田晓亮</strong>，10年软件行业经验，现任华为公有云服务ServiceStage首席工程师。2012年进入云计算领域，对PaaS， DevOps，APM等有深入的研究和实践经验。负责公司微服务框架的设计，开发和落地，微服务引擎云服务商用上线公有云。</p> |
| |
| <p><strong>摘要：</strong> 我们在公有云交付PaaS平台，帮助用户管理应用，通过流水线进行持续交付，管领应用的全生命周期，当应用系统的网络拓扑变得不断复杂后，需要引入微服务架构模式，来解决分布式系统的复杂性，本主题将讲述PaaS平台如何使用ServiceComb帮助用户完成微服务转型。</p> |
| |
| <hr /> |
| <p><strong>《微服务创新新品发布》</strong> <a href="/assets/slides/20190624/4_Innovation_New_Project_Release.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>马彬</strong>，ServiceComb 社区成员，华为开源软件能力中心架构师，企业应用微服务化工程师，13+年电信级中间件平台、虚拟化、嵌入式操作系统与开源软件设计开发经验。</p> |
| |
| <p><strong>摘要：</strong> ServiceComb在Aapche毕业已经约半年时间，在这半年里面，社区并未冒进地去迸发新的项目或特性，而是选择了认真听取用户的意见。如今，ServiceComb社区确定了系列解决用户微服务化过程中痛点的方向，并且开始在社区里面继续创新孵化。本主题将和大家分享这些获取到的痛点和孵化项目，期望与用户/开发者一起思考如何一起去摆平微服务中的难题。</p> |
| |
| <hr /> |
| <p><strong>《解密ShardingSphere与ServiceComb联合打造的分布式事务解决方案》</strong> <a href="/assets/slides/20190624/5_ShardingSphere_Distributed_Transaction_Solution.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>潘娟</strong>，京东数科高级DBA，主要负责京东数科数据库中间件开发、数据库运维自动化平台开发、生产数据库运维工作。多次参与京东6.18、11.11等大促活动的护航工作。曾负责京东数科数据库自动化平台设计与开发，现专注于Apache ShardingSphere分布式数据库中间件开发。乐于在数据库、自动化、分布式、中间件等相关领域进行学习和探索。</p> |
| |
| <p><strong>摘要：</strong> 业务层面的微服务架构大行其道，底层分布式数据库&amp;中间件如火如荼。在微服务场景下，各服务之间数据库相互独立，不能依靠单一数据库来实现跨服务的事务一致性；在分布式数据库集群状态下，又如何实现分布式事务呢？ShardingSphere作为首个Apache基金会的分布式数据库中间件项目与首个Apache微服务顶级项目ServiceComb强强联合，共同打造微服务与分布式数据库场景下的分布式事务解决方案。 |
| 本次分享将围绕分布式事务，并以ShardingSphere与ServiceComb联合打造的分布式事务解决方案作为核心内容进行详细阐述和讲解。</p> |
| |
| <hr /> |
| <p><strong>《支持10万TPS的高性能服务间通信解读》</strong> <a href="/assets/slides/20190624/6_Microservice_High_Performance_Communication.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>刘宝</strong>，Apache软件基金会 Commiter，拥有10年以上java开发框架的开发和运维经验。热爱微服务，并持续为它们开发一些常用的工具，比如进行中的servicecomb-fence项目。也喜欢分享开发和软件工程能力建设方面的一些心得，它们都发布在华为云博客和知乎专栏上面。</p> |
| |
| <p><strong>摘要：</strong> 200TPS的处理能力，已经能够满足很大一部分业务系统对于性能的要求。另外一方面，优化服务器间通信的性能的收益，很容易通过优化应用代码实现或者被应用代码状况抵消，还可以低成本的通过水平扩展处理能力等方式获得，因此开发者往往不重视通信能力的优化。本次演讲结合servicecomb-java-chassis的通信优化实践，说明性能优化的一些常见手段，并实践的视角，分享性能优化在系统可靠性、资源规划等其他不容易被开发者直接感知的方面的收益。</p> |
| |
| <hr /> |
| <p><strong>《华为云分布式事务云服务实践》</strong> <a href="/assets/slides/20190624/7_HuaweiCloud_Distributed_Transaction_DTM_Practices.pdf">PDF下载</a></p> |
| |
| <p><strong>主讲人：</strong> <strong>王启军</strong>，华为云PaaS团队，负责java和go微服务框架。曾任当当网架构师，主导电商平台架构设计；曾就职于搜狐负责手机微博的研发。《持续演进的Cloud Native》作者，微信公众号“奔跑中的蜗牛”博主。</p> |
| |
| <p><strong>摘要：</strong> 微服务架构下，服务数量暴涨，一个服务可以完成的工作会被分发到多个服务，按照“服务自治”的原则，数据访问通过接口隔离，原本的单库事务变成了分布式事务，“当你开始考虑一致性问题的时候，才能说明你开始真正的了解微服务了”，本专题通过相关场景说明当你基于华为云构建微服务的时候，如何实现分布式事务？失败如何回退？超时如何处理？详细说明其背后的原理。</p> |
| |
| <hr /> |
| <p><strong>如您有更多问题关于Aapche ServiceComb，欢迎您扫码或微信添加“ServiceComb小助手”，我们将认真对待您的每一个问题</strong> |
| <img src="/assets/images/QRcode.png" alt="1" /></p></content><author><name>Mabin</name></author><category term="微服务" /><category term="Meetup" /><summary type="html">Apache ServiceComb Meetup</summary></entry></feed> |
