HTAP Query Routing Between OLTP and OLAP Engines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing hybrid transactional/analytical processing (HTAP) databases struggle to efficiently route queries to the appropriate OLTP or OLAP engine based on various factors, leading to potential interference and suboptimal performance.
Innovation Solution
A hybrid transactional/analytical processing (HTAP) database with separate OLTP and OLAP engines, utilizing a query router within the OLTP engine to route queries based on user input, cost score, data freshness, and compatibility, ensuring queries are directed to the most suitable engine for execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a unified query interface is used for both OLTP and OLAP engines, then ease of operation is improved, but query routing efficiency deteriorates
Solution Approach 1:
The patent introduces a query router as an intermediary component between the unified query interface and the OLTP/OLAP engines. The router analyzes incoming queries using multiple strategies (cost-based optimization, query pattern matching, machine learning models) to determine the most appropriate engine, thereby maintaining ease of use while improving routing efficiency and reducing interference between workloads.
2Adaptability or versatility
If OLTP and OLAP engines are integrated in a single database, then adaptability is improved, but system complexity worsens
Solution Approach 1:
The patent segments the database system into distinct OLTP and OLAP engines with specialized architectures, each optimized for their respective workloads. The OLTP engine handles transactional operations with ACID guarantees, while the OLAP engine handles analytical queries with parallel processing capabilities. This segmentation maintains adaptability for different query types while managing system complexity through clear separation of concerns.
Solution Approach 2:
The patent creates a universal HTAP database system that can handle both transactional and analytical workloads through a single unified interface. The system provides multi-functionality by routing different query types to appropriate engines, allowing the database to serve diverse purposes (OLTP, OLAP, and hybrid workloads) without requiring separate systems, thereby managing complexity while maintaining versatility.
3Measurement precision
If queries are manually routed to engines, then routing precision is improved, but ease of operation worsens
Solution Approach 1:
The patent implements self-service query routing where the system automatically analyzes incoming queries and routes them to the most appropriate engine without requiring manual user intervention. The query router employs cost-based optimization, pattern matching, and machine learning to make intelligent routing decisions, achieving high routing accuracy while maintaining ease of operation for users.
4Device complexity
If a proxy performs rudimentary sorting, then device complexity is reduced, but query routing efficiency deteriorates
Solution Approach 1:
The patent implements dynamic query routing that adapts to different query characteristics, workload patterns, and system conditions. The router can switch between multiple routing strategies (cost-based, pattern-based, ML-based) and adjust its behavior based on real-time performance metrics and data distribution, thereby improving query processing efficiency without significantly increasing system complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A hybrid transactional/analytical processing, HTAP, database (10) is provided. The HTAP database includes a shared storage (26) holding data, an online analytical processing (OLAP) engine, and an online transaction processing, OLTP, engine provided separately from the OLAP engine (14). The OLTP engine (12) includes a query router configured to route a query received by the OLTP engine (12) to either the OLAP engine (14) or the OLTP engine (12) for execution.