TiDB 101

下载 0

寒冰

发布于

1660

人观看

#信息技术

由嘉宾，皮蒂安的费尔南多·伊帕尔介绍
关于作者
Fernando Ipar
Fernando Ipar is a MySQL Principal Consultant who works remotely from his family home in Montevideo, Uruguay. Initially, Fernando began using GNU/Linux in 1998 and MySQL in 2000, and his journey led him to become active in the technical community, contributing and at times leading open source projects as well as founding the Montevideo MySQL Meetup. Before coming to Pythian, he spent seven years at Percona, where he contributed to the Percona Toolkit and TokuMX Toolkit, among other endeavors. Fernando helped scale and troubleshoot the back-ends for businesses of all sizes including financial institutions, telcos, and other IT companies while also supporting their full stack needs.

展开查看详情

1 .TiDB 101 Fernando Ipar / Percona University Montevideo / April 2019

2 .About me ●Internal Principal Consultant @ Pythian. ●Pager-carrying, buck stops at my team. ●OSDB Practice (MySQL/MariaDB, MongoDB, Cassandra, …). ●19 years of MySQL experience. © The Pythian Group Inc., 2019 "2

3 . TiDB Created by PingCAP (Founded in April 2015 by 3 Infrastructure Engineers) © The Pythian Group Inc., 2019 "3

4 .TiDB Overview ●SQL-based (MySQL[0] protocol). ●Distributed (ACID). ●Transactional (Snapshot Isolation, advertised as REPEATABLE-READ). ●Inspired on Google’s Spanner and F1. ●HTAP workloads. ●Open Source (Open Core). ●RocksDB for storage (though Storage Engine API exists)[1]. ●“15+ Petabytes in 300+ Companies”[2] [0] https://github.com/pingcap/docs/blob/master/sql/mysql-compatibility.md [1] https://blog.pythian.com/tag/myrocks/ [2] https://www.pingcap.com/success-stories/https://www.pingcap.com/success-stories/ © The Pythian Group Inc., 2019 "4

5 .Good Use Cases ●You need a sharded MySQL. ●You have a sharded MySQL but have found out the shard key does not match all query use cases (who would have thought?!). ●Your data set does not fit on a single machine and your query volume is rather low. © The Pythian Group Inc., 2019 "5

6 .Poor Use Cases ●Your workload is very latency-sensitive. ●Your data fits in a single server. ●You’re closer to OLTP than OLAP. ●You have very large transactions. © The Pythian Group Inc., 2019 "6

7 .TiDB Overview - Architecture Image Credit: https://github.com/pingcap/docs/blob/master/architecture.md © The Pythian Group Inc., 2019 "7

9 .TiDB: OLTP + Ad Hoc OLAP Image Credit: https://www.slideshare.net/morgo/tidb-introduction © The Pythian Group Inc., 2019 "9

10 .TiDB: SQL Parser and Coprocesor. Image Credit: https://www.slideshare.net/morgo/tidb-introduction © The Pythian Group Inc., 2019 "10

11 .TiDB: Replicating from MySQL Image Credit: https://github.com/pingcap/docs/blob/master/tools/syncer.md © The Pythian Group Inc., 2019 "11

12 . https://pingcap.com/tidb-academy/ I have certification vouchers for questions I can’t answer right now or otherwise interesting questions. © The Pythian Group Inc., 2019 "12

0点赞

0收藏

0下载