Altibase Inc. has been positioned by Gartner, Inc. in the NEW Magic Quadrant for Operational Database Management Systems 2014.

“Altibase’s inclusion in Gartner’s Magic Quadrant for Operational DBMSs 2014 is a testament to our tireless dedication to customer satisfaction, 24×7 support, product maturity and wide use-case applicability. In-Memory databases and hybrid databases are redefining the way data is managed. In-Memory computing is becoming mainstream and Altibase is poised and ready to fortify your business now. We strive day in and day out to be the best database now and into the future by harnessing our maturity, performance, flexibility and stability.” - Chris Chung, CEO of Altibase

Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

Why In-Memory Computing and how does an In-Memory Database Help Business?

In-Memory Prelude:

The speed of business is changing fast. Blink and your business becomes legacy. Blink and your database is legacy.

How to Choose Your In-Memory Database

Recently, Gartner’s CEO indicated in a keynote speech that the “Internet of Things” is redefining the world as we now know it. Further, he noted that the current vendors that are leading the database space and ERP space will no longer be the leaders in 6 years – “Oracle and SAP.” As with anything else, catch up is not the way to play the technology game. The best databases for the future are the ones that have been preparing for technology trends far before they become mainstream.

The conclusion is that companies will live or die on three things: In-Memory databases, CEP and real-time sensor data. Altibase, for over 20 years, has led the way in all three areas with its In-Memory database computing prowess. In-Memory computing and its effect on traditional relational databases are reinventing the way business is done.

The massive influence of the best In-Memory databases both in OLTP and OLAP are incredible. The speed and amount of data flow is breathtaking and the power of In-Memory (RAM) allows business processes, predictive analysis, modeling, forecasting and risk mitigation to act, react and take action on this data. The end goal of In-Memory computing is to take all data, both structured and unstructured (BLOB and CLOB – Big Data) and allow all of these to converge into the pinnacle of business efficiency.

Please do not let lightning quick data streams that are now measured in petabytes scare you. Properly managed, where In-Memory computing and In-Memory databases come directly into play, our world is armed with the data management systems to identify, prepare for and act on both threats and opportunities.

How Does an In-Memory Database Handle Large Storage Volume and Scale?

Hybrid In-Memory Database:

A hybrid In-Memory database that combines the speed of In-Memory and the storage capacity of physical disk is the answer. With ALTIBASE HDB (Hybrid DB), enterprises no longer have to compromise between data speed or data size.

Replication and Scalability

Altibase has the only true hybrid database that combines both RAM and disk in a single unified engine. We refer to this as 1+1=1 because 1 database has 1 In-Memory component and 1 on-disk component.

The net result is the ability to store data In-Memory, on-disk or a combination of both. Through Altibase’s MOVE technology, any DBA can literally move data bidirectionally between In-Memory or on-disk with a simple proprietary SQL command, “MOVE.”

The net result is extreme flexibility and ability to handle an unsurpassed variety of use-cases. Altibase products are built for both vertical and horizontal scalability.

Altibase can scale through replication across multiple nodes, table /distributed partitioning and can also handle Big Data through its Hadoop Connector. Traditional on-disk relational databases are overwhelmed by the growth of big data and the need for high-performance. As a result, In-Memory databases are now becoming mainstream.

Altibase takes In-Memory one significant step further by marrying the benefits of both an In-Memory database and on-disk database in one tidy SQL standard traditional relational database. Welcome to the new paradigm in database management systems. Simply, deploy the best solution that was designed to future-proof your data management strategies.

The relational database management model is still the standard by which every other type of database is measured. Although there are always new flavors and types of best databases, which include NoSQL, NewSQL, Key-Value, Document Stores, and more, veering from the relational and SQL standard compliant foundation proves time-consuming, costly and are still largely unsupported for enterprise-level demands.

In-Memory databases that follow the traditional relational data management model with SQL standards, data durability and native replication are turn-key and are designed to seamlessly handle these data demands.

In-Memory databases that follow the relational model, are SQL standards compliant and support all common connectors propose a new paradigm of database management systems that take what works (relational) and makes it better with higher speed, quicker realization of ROI and vast horizontal value-add.

Altibase can process upwards of 1.5 million transactions per second (TPS). For on-disk databases, this type of performance is physically impossible. Pure on-disk database management systems are quickly becoming relegated to legacy because of their intrinsic design that cannot eliminate slow disk I/O.

Additionally, although disk-resident databases can use caching to speed up relatively small data sets by utilizing In-Memory (RAM), this is only a viable solution for read operations while writes are still subject to I/O. Caching temporarily maintains frequently-accessed data but is not an In-Memory database or even a quasi In-Memory database. In sum and substance, even the best caching solution is no match for a true RAM database.