History[05]

Atlibase was the first company in the world to develop and commercialize a hybrid database. Altibase started off as an in-memory database research project at a government-funded research organization in Seoul, South Korea. In 2000, its first version was released for commercial use and by 2003, it entered the Chinese market. By 2011, Altibase received multiple awards and even introduced certification services. IN 2018, Atlibase went open source. Many of their clients are from the telecommunications, finance, manufacturing and utilities sectors.

Checkpoints[06]

Altibase uses fuzzy & ping-pong checkpoint methods to safely back up the most recent state of the database.

Concurrency Control[06]

Altibase has Multi-version Concurrency Control (MVCC) which provides high throughput with consistency and isolation.

Data Model[06]

Altibase is a relational database that is also ACID and SQL compliant. Atlibase is compatible and interoperable with Oracle and migrating from another database to Altibase is less complex than majority of other migrations. Altibase also uses sharding technology which allows minimal use of coordinators.

Foreign Keys[07]

Altibase allows for foreign keys

Hardware Acceleration[07]

Altibase has less CPU utilization than most legacy databases.

Indexes[06]

Altibase supports two types of indexes: B-tree indexes and R-tree indexes. The R-tree index is a multi-dimensional index type for use with spatial queries.

Isolation Levels[06]

Altibase provides “read committed” (0), “repeatable read” (1), and “no phantom read” (2), which can be selected appropriately depending on the user’s requirements.

Joins

Altibase does not have any optimizations for joins.

Logging[06]

Altibase keeps logs for changed database contents. Altibase optimizes the way logs are created in order to achieve the best possible replication performance.

Query Execution[08]

The parser checks the syntax of the SQL text, and if no errors are detected in the SQL, the parser generates a Parse Tree which is used in the validation step. The parser does not have access to the database. The validator accesses various system tables in the database to verify that all database objects referenced by the SQL exist, such as tables, columns, views, types, PSMs, etc. If there are no errors, the validator generates a Checked Parse Tree. After checking validity of the SQL, Optimizer tries to find out the best way to execute the given Checked Parse Tree, and then it generates a Plan Tree. The last phase executes the query. The executor executes the SQL using the given Plan Tree.

Query Interface[06]

Altibase compiles with SQL92 and SQL99 standard, and also provides extended features. Altibase also supports ODBC, JDBC and C/C++ Precompiler.

Storage Architecture[06]

Altibase is a hybrid database. It can access both memory-resident and disk-resident tables. It offers ACID compliance and can support both synchronous and asynchronous replication.

Storage Model

Stored Procedures[06]

System Architecture[06]

The structure of the Altibase server consists of the main thread, the dispatcher, the load balancer, the service thread pool, the service thread, the checkpoint thread, the garbage collection thread, the log flush thread, the buffer flush thread, and the archive-log thread. The Altibase physically consists of log anchol files, log files, and data files.

Views[06]