Online Transaction Processing (OLTP) and Online Analytical Processing (OLAP) are often separated in common architectures. The reason for this is the different system requirements. However, it is also possible to combine OLTP and OLAP in one system. This saves costs and resources. Dr. Andreas Weininger shows possible solutions for Hybrid Transactional and Analytics Processing (HTAP).
What is meant by "Hybrid Transactional and Analytics Processing" - HTAP for short? According to Wikipedia, Gartner offers the following definition:
"Hybrid transaction/analytical belize telegram screening processing (HTAP) is an emerging application architecture that "breaks the wall" between transaction processing and analytics. It enables more informed and "in business real time" decision making"
So it's about creating an architecture that combines the two most important database applications - transaction processing and analytical applications. The goal is to enable improved and faster business decisions, largely in real time. To understand the goal of HTAP, let's first look at what is meant by transaction processing (often also called "Online Transaction Processing" (OLTP)) and analytical processing, why they weren't always integrated, and what has changed that HTAP is now becoming a major topic.
We then examine what approaches there are to meet the requirements of a HTAP system, focusing on some particularly interesting approaches.