Service Mesh的延伸 之论道Database Mesh 分享人：张亮 日期：2018年07月25日Service Mesh风头正劲Service Mesh产品多样化Service Mesh的优势 云原生 零入侵 可观察性 面向运维服务化之后，数据库怎么办？ 服务 • 无状态 • 根据规则路由 • 业务方处理事务 数据库 • 有状态 • 根据SQL路由 • 数据库自动处理事务数据库的进化趋势 • SQL • ACID+BASE • 分布式 NewSQLNewSQL的分类 New Architecture Transparent Sharding Middleware Database-as-a-Service What's Really New with NewSQL?数据库中间层的优势 系统 •事务 运维 • DBA 开发 • SQL数据库中间层应具备的能力 Sidecar 数据库 任意 单一 单一 连接数 高 低 高 异构语言 仅Java 任意 任意 性能 损耗低 损耗略高 损耗低 无中心化 是 否 是 静态入口 无 有 无 Sidecar的优势Database Mesh架构图Sharding-Sphere 核心功能 数据分片 分布式事务 数据库治理 弹性伸缩 管控界面 实现方案 Sharding-JDBC Sharding-Proxy Sharding-Sidecar

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another

thrift client(cross-language support, both tcp and http), a Java Database Connectivity(JDBC) interface over thrift, or an Open Database Connectivity (ODBC) interface over a JDBC-to-ODBC bridge to communicate able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ another connection, the engine will be reused. You may notice that the time cost for connection here is much shorter than the last round. If you use a different user to create a new connection, another