Unverified50% confidenceFactExact time
Representative HTAP implementations include TiDB, OceanBase and SingleStore, among others, and the core idea is to use the same storage with different execution engines to serve transactional and analytical queries respectively.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/14/2026
First Seen
Valid until: 1/12/2027
Sources
Related Entities
Related Claims
UnverifiedTraditional HTAP systems achieve parallel transactional and analytical processing by maintaining two data copies—row-store and column-store—within the same database engine; Oracle, TiDB, and SingleStore all adopt this approach.77% similarUnverifiedHTAP (Hybrid Transactional/Analytical Processing) is a database architecture concept that attempts to support both high-concurrency transaction processing and analytical queries in a single system.68% similarUnverifiedNew-generation databases such as TiDB and CockroachDB attempt to simultaneously support both OLAP and OLTP workloads within a single system (HTAP).67% similarUnverifiedTiKV, the storage engine of TiDB, uses a Multi-Raft architecture where each data shard (Region) runs an independent Raft group64% similarUnverifiedStorage-disaggregation architecture is well suited for Lakehouse scenarios, enabling unified handling of both transactional and analytical workloads.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1030911API
curl https://kongchang.com/api/v1/knowledge/claims/1030911MCP
get_claim(id=1030911)