KubeCon_NA_2021
0 likes147 views
Vitess is a cloud-native storage solution that can scale indefinitely. In this session, we will first cover a high level overview of Vitess features, the architecture, and what database workloads are a good fit. Then we will demonstrate how to get started with Vitess on Kubernetes. This will be followed by VTAdmin, the next generation of tooling and UIs for managing large-scale, multi-cluster Vitess deployments, built for developers and operators alike. We will demo resharding using VTAdmin, and will talk about improvements to performance and scalability along the way.
More Related Content
What's hot (20)
Similar to KubeCon_NA_2021 (20)
More from Alkin Tezuysal (17)
Recently uploaded (20)
KubeCon_NA_2021
- 1. Deepthi Sigireddi - PlanetScale @ATechGirl Alkin Tezuysal - PlanetScale @ask_dba Andrew Mason - Slack Corp. @andrew_mason1 Malcolm Akinje - Slack Corp. @LESkidd113 Vitess: Introduction and New Features
- 2. Agenda @vitessio ❖ Introduction - Deepthi Sigireddi ❖ VTOP (Vitess Operator) + Demo - Alkin Tezuysal ❖ VTAdmin Overview + Demo - Andrew Mason ❖ VDiff Coordinator Demo - Malcolm Akinje
- 3. Vitess @vitessio A database clustering system for horizontal scaling of MySQL / MariaDB • CNCF graduated project • Open source, Apache 2.0 license • Contributors from around the community • Written in Golang
- 4. Vitess Cloud-native distributed database - Runs in Kubernetes Scalable Highly available Durability guarantees Illusion of “single database” - Single dedicated connection - MySQL 5.7 or 8.0 - Compatible with frameworks / ORMs etc. t @vitessio
- 5. Vitess serves millions of QPS in production @vitessio
- 6. Concepts Keyspace - Logical database Shard - Subset of logical database Cell - Failure domain @vitessio
- 7. Vitess Architecture basics A common replicated database cluster with primary and replicas @vitessio
- 8. Vitess Architecture basics Each MySQL server is assigned a vttablet - A daemon/sidecar - Controls the mysqld process - Interacts with the mysqld server - Typically on same host as mysqld @vitessio
- 9. Vitess Architecture basics In production you have multiple clusters @vitessio
- 10. Vitess Architecture basics User and application traffic is routed via vtgate - A smart, stateless proxy - Speaks the MySQL protocol - Impersonates a monolithic MySQL server - Relays queries to vttablets @vitessio
- 11. Vitess Architecture basics A vitess deployment will run multiple vtgate servers for scale out @vitessio
- 12. Vitess Architecture basics vtgate must transparently route queries to correct clusters, to relevant shards app app commerce shard 0 commerce shard 1 internal unsharded ? @vitessio
- 13. Vitess Architecture basics Queries route based on schema & sharding scheme app app commerce shard 0 commerce shard 1 internal unsharded USE commerce; SELECT order_id, price FROM orders WHERE customer_id=4; @vitessio
- 14. Vitess Architecture basics topo: distributed key/value store - Stores the state of vitess: schemas, shards, sharding scheme, tablets, roles, etc. - etcd/zookeeper/kubernetes - Small dataset, mostly cached by vtgate commerce shard 0 commerce shard 1 internal unsharded @vitessio
- 15. Vitess Architecture basics vtctld: control daemon - Runs ad hoc operations - API server - Reads/writes topo - Uses locks - Operates on tablets commerce shard 0 commerce shard 1 internal unsharded @vitessio
- 17. New and Upcoming Features - 12.0 release GA Oct 26 2021 - Gen4 planner - experimental in 12.0 - Continuous Benchmarking - since 11.0 - Performance Improvements - ongoing - More supported query constructs - ongoing - VTAdmin - Multi-column vindexes - Automatic failure detection - Collations - Distributed transactions @vitessio
- 18. VTOP - Vitess Operator for Kubernetes Operator Functions and Automation of Vitess functions - Automation of Vitess functions - Deploy Clusters - Deploy Shards - Failover nodes - Recover pods - Replicate data cross AZ @vitessio The Vitess Operator is open source on GitHub.
- 19. VTOP - DEMO Use of Operator - Deploying a test cluster with Operator (Already deployed) - Creating Sharding Workflow (Already created) - Create a database load (Live) - Failover during OnlineDDL on Sharded cluster (Live) @vitessio
- 20. VTOP - DEMO Workflow @vitessio Run 101 Example Create a Load Graph Execute Online DDL Perform Failover Graph https://github.com/planetscale/vitess/tree/kcna21-demo
- 22. VTAdmin - Overview - Single control plane for many Vitess deployments (“clusters”) - gRPC/http API and UI components - Golang backend with react frontend - (Eventual) replacement for the existing vtctld UI @vitessio
- 23. VTAdmin - Architecture (single cluster) @vitessio
- 24. VTAdmin - Architecture (multi cluster) @vitessio
- 26. VDiff @vitessio - Runs a diff between the source and target shards - One VDiff per workflow - This is a blocking call
- 27. VDiff (Work mainly happens in a vtctld) @vitessio
- 28. VDiff @vitessio
- 30. VDiff Future Goals (diffs done on tablet layer) @vitessio
- 31. Resources Docs: vitess.io/docs/ Code: github.com/vitessio/vitess Slack: vitess.slack.com Thank you! @vitessio