How to Choose the In-memory Database Management System

Hybrid Database Complete Flexibility


ALTIBASE is a hybrid in-memory database and is a viable database option for extremely fast data processing while also having large storage capabilities. ALTIBASE is the perfect database management system for a wide-array of use cases that span all verticals. The hybrid database provides enterprises with both of speed and storage volume.

A real hybrid database combines an in-memory database with an on-disk database in a single unified engine.

So what does that really mean?

Today’s data needs extreme speed and large storage capacity. As such, to tackle the most wide-array of use cases, a database should be easy to use (SQL standards compliant, supports all common interfaces, requires minimal application programming for implementation, DBA’s can learn it in less than a day, etc.) and should be able to process data quickly (RAM database) and store large data sets (on-disk database) all in a single database. This is what true hybrid architecture is – any exceptions are simply pseudo-hybrids. Altibase is recognized as the worldwide leader for this particular hybrid technology. ALTIBASE is the perfect database management system for future proofing enterprise level use cases that span all verticals. The hybrid database provides companies with the best of both worlds – speed and storage volume.

ALTIBASE can also be used as in-memory only database: fastest database processing on earth

ALTIBASE can be in-memory database and has many advanced features such as Direct Attach/Direct Call Interface (DCI) mode that results in the fastest data processing speeds possible. If your use case requires the most demanding speeds and you want to break the thought barrier, an in-memory only database is the way to go.

An in-memory only database stores and manipulates data in main memory (RAM) alone. Because of the very nature of RAM, which is extremely fast processing capabilities, an in-memory only database management system is ideal for blazing data processing needs. So why not choose the fastest database — an in-memory only database for everything?

  1. RAM is still extremely expensive and therefore, it is not practical for very large data size.
  2. RAM is by nature ‘volatile’ so even if there are highly advanced durability protocols through Log Files and Checkpoint images, replication, etc., it is possible to lose some data in the event of a power failure.
  3. NVRAM (Non-Volatile RAM), which in simplest terms is RAM with a battery backup, can protect data in the event of a power loss but if the battery does not last long enough, it may also lead to some potential data loss.

However, in-memory only databases are ideal for the correct use case. When extreme performance is the highest priority for a specific application, there really is no substitute.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *