ServiceComb-based Microservice Practice of MedSci Miao Yanjie Chief Architect, MedSci Service Mesh-based Microservices and Those Based on a Traditional Architecture Two network platforms, covering stable and can be evolved. • Multiple languages are supported. The hybrid deployment of Service Mesh-based microservices and those bases on a traditional architecture is supported. • There are many open-source ecosystem Zipkin Prometheus Skywalking ... Go-SDK Registration and discovery Service Mesh is compatible with the Istio ecosystem. Istio functions as the data- plane proxy. Mesher interworks

#IstioCon Your laptop as part of the service mesh by Lorenzo Fundaró SRE @ Omio #IstioCon What’s on the menu today ● EnvoyFilter in practice ● Demo ● Inspiration #IstioCon Questions #istiocon request_handle:respond(response) 13 end #IstioCon Ouch ! ● Your laptop is not part of the mesh club #IstioCon A dummy proxy for the mesh ● Called by Lua code ● Parses the contract header and makes http call #IstioCon call chain #IstioCon Demo time #IstioCon Thank you ! ● Your laptop as part of the service mesh @ Medium ● Reference implementation and run-it-yourself-demo at github.com/omio-labs/devro ute

Joshi Istio Service Mesh at Enterprise Scale Feb, 2021 Who are we? Founded 5,000 Developers 50M Customers 1993 IPO $6.8B FY19 Revenue 20 Locations 1983 Why Service Mesh? Microservices Kubernetes Kubernetes Service Mesh Istio Monolith Era Intuit Statistics ● 900+ Teams ● 5000+ Developers ● 200+ Clusters ● 7000+ Namespaces ● ~9200 Nodes varies with autoscaling Hub and Spoke API Gateway Info ✓ Security ✓ Visibility ✓ Traffic Shaping ✘ Latency ✘ Single Point of Failure Service Mesh API Gateway Book Info Payments Product Info Proxy Proxy Proxy Proxy +

OpenShift Container Platform 4.8 Service Mesh Service Mesh 的安装、使用和发行注记信息 Last Updated: 2023-04-07 OpenShift Container Platform 4.8 Service Mesh Service Mesh 的安装、使用和发行注记信息 法律通告 法律通告 Copyright © 2023 property of their respective owners. 摘要 摘要 本文档提供了有关如何在 OpenShift Container Platform 中使用 Service Mesh 的信息. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 目录 录 第 第 1 章 章 SERVICE MESH 2.X 1.1. 关于 OPENSHIFT SERVICE MESH 1.2. SERVICE MESH 发行注记 1.3. 了解 SERVICE MESH 1.4. 服务网格部署模型 1.5. SERVICE MESH 和 ISTIO 的不同 1.6. 准备安装 SERVICE MESH 1.7. 安装 OPERATOR 1.8.

HUAWEI.COM ServiceComb’s Exploration of Service Mesh Security Level: Tian Xiaoliang Huawei Cloud BU 2018-10-12 Contents 1. Service Mesh Evolution in Huawei 2. Mesher Practice 3. How Mesher Drives Confidential Microservice System Is Demanding But Is Hard to Create 3 Huawei Confidential Service Mesh - Proposed by William Morgan in 2017 - An infrastructure layer that enables communications between cloud-native applications 4 Application Service Mesh Transport Network Physical Application Transport Network Physical Huawei Confidential Service Mesh Evolution in Huawei - 2013: IR component in

#IstioCon Moving large scale consumer e-commerce Infrastructure to Mesh Rajath Ramesh Principal Software Engineer @Carousell Harshad Rotithor Software Architect @Carousell #IstioCon About Carousell isolation helps reduce Istio proxy resources #IstioCon Next Steps ● Move stateful components in to mesh discovery and routing ● Expose gateway services via Istio Gateway ● Towards RESTRICTED network policy

#IstioCon Extending service mesh capabilities using a streamlined way based on WASM and ORAS 王夕宁 | 阿里云服务网格ASM 2 Envoy’s Filter Chain Listener Downstre am Filter Filter Filter Cluster Upstrea

resilient systems inside the mesh: abstraction and automation of Virtual Service generation Vladimir Georgiev, Thought Machine #IstioCon Sync calls failures inside the mesh ● Everyone says to fail

服务代理（service broker）是实现应用程序的编程发现和部署的一个步骤。但它并非一个长时间运行 的进程，所以无法执行第 2 天操作，如升级、故障转移或扩展。它在安装时提供对可调参数的自定义 和参数化，而 Operator 则可持续监控集群的当前状态。非集群服务仍非常适合于 Service Broker，但 也存在合适于这些服务的 Operator。 2.1.2. Operator Framework Operator 元数据的发布。 Operator 捆绑包代表 Operator 的单一版本。磁盘上的捆绑包清单是容器化的，并作为捆绑包镜像提供， 第 第 2 章 章 了解 了解 OPERATOR 7 Operator 捆绑包代表 Operator 的单一版本。磁盘上的捆绑包清单是容器化的，并作为捆绑包镜像提供， 该镜像是一个不可运行的容器镜像，其中存储了 Kubernetes 清单和 Operator 创建基于文件的目录的说明，请参阅管理自定义目录。 有关管理基于文件的目录的 opm CLI 命令的参考文档，请参阅 CLI 工具。 2.2.2.7. 自 自动化 化 建议 Operator 作者和目录维护人员使用 CI/CD 工作流自动化其目录维护。目录维护人员可通过构建 GitOps 自动化以完成以下任务来进一步改进： 检查是否允许拉取请求 (PR) 作者进行请求的更改，例如更新其软件包的镜像引用。 检查目录更新是否通过