HTAPs have many benefits. HTAP creates a simpler architecture because the two different types of databases as well as the ETL process are replaced by a single database. And data duplication is eliminated. Instead of data being stored in OLTP for transaction processing and then replicated to OLAP (possibly multiple times) for analysis, the single source of truth resides in an HTAP database.

SingleStore was conceived as an HTAP database long before Gartner coined the term. The company was founded in 2011 to create SQL-enabled general-purpose databases while combining transactions and analytics into one fast, distributed database.

And, we continue to push the HTAP database forward to facilitate the development of real-time applications.

Increasingly, with common storage, a single table type can serve both transactional and analytical needs. Any needed performance boost is provided by scalability, simply by adding servers. Future plans for Universal Storage include higher levels of convergence.

HTAP databases are available for analytical queries once created, so organizations can capture value from transient opportunities that would be lost in the time it takes to transfer data from OLTP to the OLAP database.

Simplified data architecture reduces operating costs

HTAP only needs to manage one system, reducing operational complexity and cost. The HTAP database architecture simplifies data management, freeing IT and data professionals to focus on higher-level, value-added tasks.

How we built an HTAP database to simplify your data platform

TiDB is an open-source distributed NewSQL database that supports hybrid transaction/analytical processing (HTAP) workloads. In May 2020, TiDB 4.0 was fully launched and has since become a true HTAP database.

In this article, I will share with you what HTAP is and how TiDB can make full use of HTAP architecture.