Curve integrate to Cloud NativeCurve intro • Curve is an distributed storage system • High performance • Easiser operation • Cloud native • Curve is composed of two parts • Curve Block Storage (CurveBS) • CurveBS: a high performance cloud native distributed block storage • Curve File System (CurveFS) • CurveFS: a high performance cloud native file system (Based on CurveBS / S3 compatible Support horizontal/vertical scaling, auto config tuning, abnormal detection, schedule tuningCloud native Feature list • Features for Cluster • Features for CurveBS • Features for CurveFS • Features

C++ in the Cloud One NIF at a Time with Elixir Sakshi Verma | Senior Software Engineerhttps://www.linkedin.com/in/sakverma Functional, concurrent language built for scalability. Ideal for managing managing large-scale cloud applications. Built on the Erlang VM, ensuring resilience and fault tolerance. What is Elixir?https://www.linkedin.com/in/sakverma The Smooth Sailing…https://www.linkedin linkedin.com/in/sakverma Enter Native Operations Option 1: Rewrite all the native functionality in Elixir. Option 2: Use already existing functionality from Native Code.https://www.linkedin.com/in/sakverma

Curve High performance Cloud native Distributed storage system https://www.opencurve.io/Agenda • What is Curve • Use Cases • CurveBS • Key Features • Comparing to Ceph • CurveFS • Comparing (CurveBS) • CurveBS: a high performance cloud native distributed block storage • Curve File System (CurveFS) • CurveFS: a high performance cloud native file systemUse Cases • Container • Database Aggregates underlying storage in the cloud (AWS EBS, AWS S3, AWS Glacier, aliyun EBS, aliyun OSS) or on-prem (baremetal, HDFS, OSS) and turns it into container-native storageDatabase • Database services

CURVE: a High-performance Software-Defined storage for Cloud Native applications Xiang Dong Architect, Netease Hangzhou Research InstituteAgenda � Why develop storage Design objectives Achievements for elastic block storage ● Requirements for file systemopen-source storage ● Requirements ○ Cloud Native ○ Easy operation and maintenance ○ High performance ● CEPH ○ Complex and Large amount of codes Design objectives ● Thin provisioning storage pools ● High performance ● Easy maintenance ● Cloud NativeAgenda Why develop storage Design objectives � Achievements in CURVE Key designs used by

Internal Combustion Engine Flight Synthetic Fertilizer Transistors PCs Internet Smartphones Cloud12 …Technology Compounding Over Fifty-Plus Years = Better + Faster + Cheaper → More Note: PC units base as of 2010. Mobile internet units are the installed based of smartphones & tablets in 2020. Cloud & data center capex includes Google, Amazon, Microsoft, Meta, Alibaba, Apple, IBM, Oracle, Tencent Trillion Enterprise Impact’ via Morgan Stanley (10/23) Enabling Infrastructure CPUs Big Data / Cloud GPUs Computing Cycles Over Time – 1960s-2020s, per Morgan Stanley Note: Axis is logarithmic;

High performance Cloud native Distributed storage system https://www.opencurve.io/Agenda • CurveBS Architecture • CurveBS Topology • CurveBS Data Organization • MetaData Server (MDS) • ChunkServer ChunkServer • Client • CurveBS IO processing flow • CurveBS Performance considerations • Cloud NativeAgenda • CurveFS Architecture • CurveFS Data Organization • CurveFS file Organization • polardb for postgresql using CurveBS • Cloud-native support for CurveBS • CurveBS clusters and related monitoring services can be configured using CRDs in public cloud and on- premises environments •

From Istio OSS to Enterprise Service Mesh 宋净超（Jimmy Song） September 24, 2022 Shanghai, China Cloud Native Application Networking Secure, Observe and manage microservices Outline ● Background ● Enterprise security ● R&D on Next Generation Access Control (NGAC) ● Exclusively co-host annual zero trust multi-cloud conference Best in Class Team ● Creators of the service mesh Istio, gRPC, Apache SkyWalking, Zipkin complexity and lack of operational agility ● You can't be Cloud Native at scale without a modern application- aware network Cloud!=Cloud Native Bare metal VMs Kubernetes VMs ● Monolith was decoupled

ServiceMesh发展趋势（续） 蚂蚁金服 敖小剑 棋到中盘路往何方Part 0：前言 5月底，我在Cloud Native Meetup上做了一个“ServiceMesh 发展趋势：云原生中流砥柱”的演讲，当时主要讲了三块内容： - Service Mesh产品动态 - Service Mesh发展趋势 - Service Mesh与云原生 今天的内容可以视为是上次演讲部分内容的深度展开，如社区 DirectorPart 3：ServiceMesh灵魂拷问三：要不要支持虚拟机？ 理想（云原生普及）和现实（虚拟机大量存在）的差距 理想很丰满，现实很骨感。Cloud Native虽 然令人向往，然而现实中，有多少企业是真 的做好了Cloud Native的准备？ 问题：到底该先容器/k8s，再上微服务 /servicemesh；还是先微服务/servicemesh， 再上容器/k8s？ 每个公司都会有自己的实际情况和选择。

Segmented
 Stream streamnative.io 基础决定上层：Cloud-Native • State / Scale / Storage https://github.com/apache/pulsar-helm-chart streamnative.io 基础决定上层：Cloud-Native https://streamnative.io/blog/release/2 io/blog/release/2020-08-18-announcing-streamnative-cloud https://console.streamnative.cloud/?defaultMethod=singup • Pulsar 的根本不同 • Apache Pulsar 简介 • Pulsar 的⽣态和社区 streamnative.io Pulsar 和周边⽣态 streamnative

● TiDB Operator 简介 ● 扩展 Kubernetes 的几种方式 ● TiDB Operator 实现 TiDB Operator 是什么 PingCAP.com Cloud Native Era: Portable, Scalable, Automated Full lifecycle management of TiDB cluster - Deployment - Upgrading will increase the replicas by the number of failed replicas PingCAP.com - TiDB Operator 简介 - Cloud Native Era: Full Automation - Kubernetes Pattern: Declarative Model - Operator Pattern: Extending Kubernetes