CurveBS I/O processing flow Before introducing IO processing flow, we first describe the overall architecture, data organization and topology structure of CURVE. CurveBS uses the central sockets. l Nebdserver: Accepts requests from NEBDClient and calls Curve Client for corresponding processing. it can receive requests from different NEBDClients.3. Through the above splitting, NebdClient NebdClient replaces Curve Client and directly interfaces with upper services. There is no logical processing in NEBDClient, it just proxy requests and has limited retries, which ensuring that NEBDClient

CURVE Roadmap CURVE Community You can take awayDesign objectives App scenario & requires ● Database scenario ● Elastic block Storage for KVM / Kubernetes / iSCSI Design objectives ● Thin provisioning take awayPerformance in database scenario Solution architecture ● CURVE provides underlying distributed shared storage services ● Polardb for PostgreSQL provides database services Solution features seperation between storage and computation ● The call method is the same as that of the standalone database Performance test vs CEPH ● BenchmarkSQL transactions per minute increased by 39% ● In PGBench

System (CurveFS) • CurveFS: a high performance cloud native file systemUse Cases • Container • Database • Data apps(middleware/bigdata/ai) • Data backupContainer • Aggregates underlying storage container-native storageDatabase • Database services orchestrated in the cloud • Curve can backup / sync data to slave cloud • When master cloud failure happens, Database service can move to the slave

• CurveBS Data Organization • MetaData Server (MDS) • ChunkServer • Client • CurveBS IO processing flow • CurveBS Performance considerations • Cloud NativeAgenda • CurveFS Architecture •

storage lifecycle(backup, failure, recovery) DEEP INSIGHTS Plan to Support metrics, alerts, log processing and workload analysis AUTO PILOT Plan to Support horizontal/vertical scaling, auto config tuning