ORACLE 产品介绍 MySQL 企业版 全球广受欢迎的开源数据库 重要特性  Oracle MySQL 服务云  MySQL 数据库  MySQL 企业级备份  MySQL 企业级高可用性  MySQL 企业级可扩展性  MySQL 企业级身份验证  MySQL 企业级 TDE  库应用 成为全球使用广泛的开源数据库。它是一种事务安全、符合 ACID 标准的集成式数据库，支持全 面的提交、回滚、崩溃恢复和行锁定功能。MySQL 不仅简便易用、易于扩展、性能卓越，而且 还提供了一整套数据库驱动程序和可视化工具，可帮助开发人员和 DBA 自主构建和管理 MySQL 应用。MySQL 数据库具备以下特性： ORACLE 产品介绍 2 MySQL 企业级加密 为在整个生命周期全程保护敏感数据，MySQL 企业级加密提供非对称加密（公钥加密）的行业 标准功能。MySQL 企业级加密提供加密、密钥生成、数字签名和其他加密特性，帮助企业保护 机密数据，满足 HIPAA、Sarbanes-Oxley 和 PCI 数据安全标准等法规的要求。 ORACLE 产品介绍 3 MySQL 企业级防火墙

@TwitchiH & @fredbrancz Prometheus Deep Dive Introduction Intro 2.0 to 2.2.1 2.4 - 2.6 Beyond Outro ACID ACID databases... Atomicity - since 1.x Consistency - since 1.x Isolation - will happen within 2 @TwitchiH & @fredbrancz Prometheus Deep Dive Introduction Intro 2.0 to 2.2.1 2.4 - 2.6 Beyond Outro ACID Isolation Each append action gets a write ID (64 bit monotonic counter) Every sample’s write ID

2 Distributed Transaction 3.2.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations transactions based on XA standard just as local transactions. XA standard can strictly guarantee ACID features of transactions. That guarantee can be a double‐edged sword. It is more proper in the implementation

3 Distributed Transaction 4.3.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations transactions based on XA standard just as local transactions. XA standard can strictly guarantee ACID features of transactions. That guarantee can be a double‐edged sword. It is more proper in the implementation

. MySQL Wire Protocol heartbeat meta TiDB is not a database middleware Sharding middleware TiDB ACID Transaction Support Mostly Elastic Scaling Complex Query (Join, Sub query, GROUP BY) Failover Manual specifying sharding rules ● Full-featured SQL layer which is designed for distributed computing ● ACID sementics, transaparent to application layer ● MySQL compatiblity Cons: ● Not 100% MySQL compatibility

4 Distributed Transaction 4.4.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations transactions based on XA standard just as local transactions. XA standard can strictly guarantee ACID features of transactions. That guarantee can be a double‐edged sword. It is more proper in the implementation

2 Distributed Transaction 3.2.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity: transactions are executed as database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations impact on performance in concurrent sce‐ narios. BASE Transaction If a transaction that implements ACID is called a rigid transaction, then a transaction based on a BASE transaction element is called a

2 Distributed Transaction 3.2.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity: transactions are executed as database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations impact on performance in concurrent sce‐ narios. BASE Transaction If a transaction that implements ACID is called a rigid transaction, then a transaction based on a BASE transaction element is called a

4 Distributed Transaction 4.4.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity guarantees that each transaction database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations transactions based on XA standard just as local transactions. XA standard can strictly guarantee ACID features of transactions. That guarantee can be a double‐edged sword. It is more proper in the implementation

2 Distributed Transaction 8.2.1 Background Database transactions should satisfy the features of ACID (atomicity, consistency, isolation and dura‐ bility). • Atomicity: transactions are executed as database has provided perfect native ACID support, it can become an obstacle to the system performance under distributed situations. How to make databases satisfy ACID features un‐ der distributed situations impact on performance in concurrent sce‐ narios. BASE Transaction If a transaction that implements ACID is called a rigid transaction, then a transaction based on a BASE transaction element is called a