HTAP Query Routing Between OLTP and OLAP Engines

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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, featuring a query router within the OLTP engine that considers user input, cost score, data freshness, and syntax support to route queries effectively to the most suitable engine for execution.

Engineering Contradictions & Design Principles

VSEngineering 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 accuracy deteriorates

Engineering Contradiction:
Improvequery submission convenienceVSAvoidquery routing accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

A query router component is introduced as an intermediary between the unified query interface and the OLTP/OLAP engines. The router analyzes query characteristics (complexity, data volume, resource requirements) and automatically determines the most appropriate engine for execution, thereby maintaining ease of operation while improving routing accuracy through intelligent mediation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If OLAP and OLTP engines are integrated in a single database, then adaptability is improved, but system complexity increases

Engineering Contradiction:
Improveprocessing capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The database system is segmented into distinct OLTP and OLAP engines, each optimized for specific workload types. The OLTP engine handles transactional operations with simple, fast processing, while the OLAP engine handles analytical queries with complex, data-intensive operations. This segmentation allows each component to be independently optimized while maintaining overall system versatility through the unified interface and intelligent routing mechanism

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260044505A1Smart query routing in hybrid database
Publication Date: 2026.02.12 LEMON INC(GB)
  • US20260044505A1 patent drawing
  • US20260044505A1 patent drawing
  • US20260044505A1 patent drawing

AI summary

A hybrid transactional/analytical processing (HTAP) database is provided. The HTAP database includes a shared storage holding data, an online analytical processing (OLAP) engine, and an online transaction processing (OLTP) engine provided separately from the OLAP engine. The OLTP engine includes a query router configured to route a query received by the OLTP engine to either the OLAP engine or the OLTP engine for execution.