What are the benefits of Altibase’s hybrid architecture?

Working in a true hybrid environment provides significant benefits over both in-memory and disk-resident databases.

To fully understand why, it is important to understand the respective benefits of in-memory and disk-resident databases.

In-memory databases are almost always significantly faster than any disk-resident database. In addition, the fact that the data resides directly in RAM means that response times and latency are extremely low (microsecond scale). However, the downside is that RAM is significantly more expensive than traditional hard disks, and also has smaller storage capacity.

In contrast, disk-resident databases generally have fairly poor performance. This is because disk I/O is very expensive, and the architecture of the database often spends a lot of CPU resources optimizing disk access patterns. However, disk-resident databases have immense storage capacity and this storage is fairly cheap.

This is why a hybrid engine is so attractive. By combining an in-memory database and a disk-resident database into one solution, you effectively get all the benefits and eliminate all the disadvantages. Need high performance? Use a memory table. Need lots of storage? Use a disk table. Other database solutions try to emulate this architecture, sometimes by using a different IMDB as a caching layer for their disk database. But the implementation is often complex, buggy and expensive due to the need to maintain multiple disparate database licenses. With Altibase, you get all of these advantages in one easy-to-use solution. In addition, the engine is truly unified in the sense that you can perform operations such as joins between memory tables and disk tables.

This functionality is at the heart of why Altibase has so many satisfied customers worldwide. Once customers see the performance and flexibility of a hybrid database, they rarely want to use anything else.

Following case studies have hybrid architecture usages of Altibase.

 

Altibase vs. Bundled Solution (In-Memory DB & On-Disk DB)

Category

Altibase

Bundled Solution

# of Engines

1

2 (databases and servers)

Management

Easy

Complex (problems with data synchronization)

Cost

Low

High(>double)

 

1 Altibase

VS.

1 (In-Memory DB & On-Disk DB) bundled

   6_What are the benefits of ALTIBASE HDB's hybrid architecture-1-1  6_What are the benefits of ALTIBASE HDB's hybrid architecture-1-2

Hybrid Benefits

  • In-memory and on-disk in a single unified engine
  • Data management efficiency and optimization
  • Altibase’s Storage Manager combines and handles all data on in-memory database and on-disk database, providing transparency for direct management of multi-temperature data
  • Reduced point of failure
  • Reduced CPU use
  • Reduced license and maintenance costs by purchasing one database vs. two
  • Reduced operational costs and human resources
  • Lower TCO from reduction in hardware investment

Problems with Bundling an In-Memory DB and an On-Disk DB:

  • Bundling requires vendors to utilize a separate caching layer between an in-memory database and an on-disk database, which leads to many synchronization and latency issues.
  • Moving multi-temperature data is complex and risky.
  • Other vendors have predominantly acquired their in-memory DBMSs. As such, the underlying codebases for their memory and disk databases are different, complicating data management between the two database engines.
  • Since two separate technologies that were not designed to work together are conjoined, a simpler way of looking at bundling is a commercial workaround.

6_What are the benefits of ALTIBASE HDB's hybrid architecture-2-1

Comments are closed.