availability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. ## Agenda infrastructure adaptation The challenges to storage module on HTAP scenario ## I solation between OLTP and OLAP workloads • Isolation is difficult if we mix them in the same node • TP and AP scale separately requirements • Different best data structures. • Row based vs column based • Index ## I solation between OLTP and OLAP workloads SQL Layer TiDB / TiSpark Placement Driver PD 1 PD 1 ![Image](/uploads/do

TiDB to power your application without changing a single line of code in most cases. ## • Focus on OLTP ☐ There are lots of OLAP system( Spark, Presto, Impala...) ## TiDB Features ## • Multiple storage

Greenplum扩展规划 ## 业务数据与数据使用归类 时间维度：过去 - 现在 - 未来 （数据的生命周期） “现在”的数据 —— OLTP “过去”的数据 —— OLAP “未来”的数据 —— 趋势分析 ## 业务数据与数据特点 • 现在的数据 —— OLTP 实时，在线系统，客户使用 事务小，频率高，并发高 · 过去的数据 —— OLAP 非实时（T+1，或小时级），离线系统，分析决策 实时与延时需求的权衡 ## 数据流转过程 • 1 业务数据的产生 —— OLTP • 2 业务数据的中转 —— ETL服务器 • 3 数据的存储和计算 —— OLAP集群 · 4 结果数据的展现 —— 数据集市 • 5 访问接口的封装 —— API接口服务器 • 6 最终数据的显示 —— 前端界面 · 7 结果数据的交互 —— OLTP，趋势分析 • 8 OLAP数据流转 —— dbsync平台 dbsync平台 ## 数据仓库体系架构 ## 数据架构示意图 ## OLAP体系架构示意图 业务数据源端：OLTP环境 csv文件 数据展示端： Mis界面访问系统 图形化展示 OLAP数据统一入口 ETL服务器 OLAP集群统一存储与计算 数据接收端：OLTP系统趋势分析 备份节点 OLAP master 管理节点 OLAP数据统一出口 OLAP segment数据节点 OLAP

ShardingSphere-JDBC adopts decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java; ShardingSphere-Proxy provides static entry and all languages support increase the system capacity by removing database connection restrictions. It is also applicable to OLTP operation, which usually has sharding keys and can be routed to a single shard. So it is a wise choice circumstance, two requests waiting for each other will not happen, so there is no need for locking. Most OLTP operations use sharding keys to route to the only data node, which will make the system in a totally

|性能|损耗低|损耗略高|损耗低| |无中心化|是|否|是| |静态入口|无|有|无| #### 1.1.4 混合架构 ShardingSphere-JDBC 采用无中心化架构，适用于 Java 开发的高性能的轻量级 OLTP 应用；ShardingSphere-Proxy 提供静态入口以及异构语言的支持，适用于 OLAP 应用以及对分片数据库进行管理和运维的场景。 Apache ShardingSphere 是多接入端共同组成的生态圈。通过混合使用 这样即可以防止对一次请求对数据库连接占用过多所带来的问题。该模式始终选择内存归并。 内存限制模式适用于 OLAP 操作，可以通过放宽对数据库连接的限制提升系统吞吐量；连接限制模式适用于 OLTP 操作，OLTP 通常带有分片键，会路由到单一的分片，因此严格控制数据库连接，以保证在线系统数据库资源能够被更多的应用所使用，是明智的选择。 ## 自动化执行引擎 ShardingSphere 最初将 的并发。因此，ShardingSphere 在这里进行了 2 点优化： 1. 避免锁定一次性只需要获取 1 个数据库连接的操作。因为每次仅需要获取 1 个连接，则不会发生两个请求相互等待的场景，无需锁定。对于大部分 OLTP 的操作，都是使用分片链路由至唯一的数据节点，这会使得系统变为完全无锁的状态，进一步提升了并发效率。除了路由至单分片的情况，读写分离也在此范畴之内。 2. 仅针对内存限制模式时才进行资源锁定。在

d45a/p6_2.jpg)  OLTP DBs  ![Image](/u point / short access ☐ Row format for OLTP ☐ Columnar format for OLAP • Workload Interference A single large analytical query might cause disaster for your OLTP workload ## A Popular Solution • Use Use different types of databases ☐ For live and fast data, use an OLTP specialized database or NoSQL ☐ For historical data, use Hadoop / analytical database - Offload data via the ETL process into your

Syntax (MySQL 互换) ✓ Distributed Transactions (分散トランザクション) Cloud Native (クラウドネイティブ志向) ☑ Minimize ETL (OLTP と OLAP のサポート) High Availability (高可用性)  ✓ Distributed Transactions (分散トランザクション) Cloud Native (クラウドネイティブ志向) ☑ Minimize ETL (OLTP と OLAP のサポート) High Availability (高可用性) ## TiDB の特徴 (Horizontal Scalability)  ✓ Distributed Transactions (分散トランザクション) Cloud Native (クラウドネイティブ志向) Minimize ETL (OLTP と OLAP のサポート) High Availability (高可用性) ## TiDB の特徴 (MySQL Compatible Syntax) ![Image](/uploads/

ShardingSphere-JDBC adopts a decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java. ShardingSphere-Proxy provides static entry and all languages support ShardingSphere-JDBC adopts a decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java. ShardingSphere-Proxy provides static entry and all languages support brought more complex situations to the database. Apache ShardingSphere wants to solve massive data OLTP problem first and complete relevant OLAP support problem little by little. SQL ## SQL Supporting

ShardingSphere-JDBC adopts a decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java. ShardingSphere-Proxy provides static entry and all languages support ShardingSphere-JDBC adopts a decentralized architecture, applicable to high-performance light-weight OLTP application developed with Java. ShardingSphere-Proxy provides static entry and all languages support brought more complex situations to the database. Apache ShardingSphere wants to solve massive data OLTP problem first and complete relevant OLAP support problem little by little. SQL ## SQL Supporting