apache.org [Github ] https://github.com/apache?q=servicecomb Apache ServiceComb Introduction of Microservice Innovation Project [Website] http://servicecomb.apache.org [Github ] https://github.com/apache environment Heterogeneous communication in the service center Microservice authentication Distributed system configuration center Microservice contract tools Apache ServiceComb Helps enterprise users domain using multiple programming languages. Enables collaboration and governance between microservice applications developed based on multiple technology stacks. Meets performance and security

HUAWEI CLOUD Microservice Tool Improves Development Efficiency Department: Application Platform Service Author: Wang Qijun Date: 2019-09-20 Security Level: Contents 1. Tool for Splitting Monolithic into Microservices 2. Contract Management Tool 3 Advantages of the Microservice Architecture Factor Monolithic Architecture Microservice Architecture Delivery speed Slow Fast Fault isolation scope Thread-level Dependency on tools Low Relatively high O&M complexity Low High 4 Major Difficulty in Building the Microservice Architecture: How to Split an Application into Microservices? • Factors > Team size > Delivery

HUAWEI.COM Security Level: Practice Sharing: Hybrid Deployment of ServiceComb-based Microservice Practice of MedSci Miao Yanjie Chief Architect, MedSci Service Mesh-based Microservices and Those new services DB Cluster ... Huawei Open- Source ServiceMesh Solution Mesher iDrugSafety Microservice Selection Principles • The architecture is stable and can be evolved. • Multiple languages full control. • A complete ecological stack is available, covering mainstream open-source microservice O&M and security domains. • Learning costs are low. Users with the basic knowledge of programming

Challenges to Microservice Development • ServiceComb Project Introduction • ServiceComb Community Development History • Latest ServiceComb Roadmap Huawei Confidential 4 Challenges to Microservice Architectures monitoring • Route management Huawei Confidential Current Microservice Framework 5 Service framework Service Mesh ServiceComb Microservice Solution Java programming (POJO/SpringMVC/J AX-RS) Golang consistency Service contract Smooth cloud migration Open-source ecosystems Processing chain Microservice scaffolding Service security Governance UI Automated deployment Monitoring and O&M

target specific infrastructure platforms with limited code portability across clouds and edge Microservice building blocks Cloud + Edge Sidecar architecture Sidecar architecture Standard APIs accessed between services State management Create long running, stateless and stateful services Microservice building blocks Service-to- service invocation Perform direct, secure, service- to-service State management Microservice building blocks { "data": { "sku":"v100", "quantity":"50" } } Post http://localhost:3500/v1.0/bindings/myDatabase Resource bindings: Output Microservice building blocks

Application Runtime State of Enterprise Developers Being asked to develop resilient, scalable, microservice-based apps Functions and Actors are powerful programming models They write in many languages Make it easy for developers to create microservice applications without being an expert in distributed systems, including migrating existing code Microservice Building Blocks Developer first, standard framework Any code or framework… Functions S e r v i c e s w r i t t e n i n .NET Core Microservice application Service-to- service invocation State management Publish and subscribe Resource

Mesher Drives Enterprise Transformation Towards MicroserviceArchitectures Huawei Confidential Microservice System Is Demanding But Is Hard to Create 3 Huawei Confidential Service Mesh - Proposed by Physical Huawei Confidential Service Mesh Evolution in Huawei - 2013: IR component in the microservice development platform - 2015: Sidecar component 5 Huawei Confidential 6 Mesher - Implementation Instance Cache Management Service center Huawei Confidential 9 Route Management Based on Microservice Metadata • Matches the request header of the request. • Matches metadata information of the

a single microservice repository that bundles the microservice's code with its deployment YAML manifest files. YAML files, if you recall, are what define or declare how the microservice runs in the

applica�ons: deathstar, �efighter, and xwing. In this case, we are only going to use our xwing microservice to secure communica�ons to exis�ng AWS instances. $ kubectl create -f https://raw.githubusercontent The productpage microservice calls the details and reviews microservices to populate the page. details. The details microservice contains book informa�on. reviews. The reviews microservice contains book calls the ra�ngs microservice. ra�ngs. The ra�ngs microservice contains book ranking informa�on that accompanies a book review. In this demo, each specific version of each microservice is deployed into

our electronic trading business, it is important to thoroughly test algo behaviors. Although microservice components can easily be unit tested, it is often non-trivial to automate the system-level tests A controller layer: This layer provides a set of APIs (interfaces) to interact with the microservice system. It sets up an internal test version of the system with a collection of components, a