System Architecture

Shared-Everything

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.

Foreign Keys

Supported

Altibase allows for foreign keys

Indexes

B+Tree R-Tree

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.

Stored Procedures

Supported

Isolation Levels

Read Committed Serializable Repeatable Read

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

Checkpoints

Fuzzy

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

Storage Model

N-ary Storage Model (Row/Record)

Concurrency Control

Multi-version Concurrency Control (MVCC)

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

Data Model

Relational

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.

Query Interface

SQL

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

Views

Virtual Views Materialized Views

Storage Architecture

In-Memory Hybrid

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.