What does the Altibase architecture look like?#
Overview#
This FAQ gives an overview of the main components of the Altibase server and how they work together.
Version#
All versions of Altibase
Altibase architecture#
Altibase is a hybrid DBMS that manages memory tables and disk tables in a single server process.
| Area | Component | Role |
|---|---|---|
| Session / Query | Dispatcher | Accepts client connections and assigns them to service threads. |
| Service Thread Pool / Manager | Service threads process client requests; the manager adjusts the pool. | |
| SQL Plan Cache | Caches execution plans so they can be reused by identical SQL statements. | |
| Memory table | Memory Tablespaces | Keep all memory table data resident in main memory. |
| Checkpoint Images | Disk copies of the memory tablespaces, loaded into memory at startup. Two images are written alternately (ping-pong). | |
| Disk table | Disk Bufferpool | Caches pages of disk tables in memory. |
| Buffer Flusher | Writes dirty pages of the bufferpool to the datafiles, including on flush requests from the checkpoint thread. A page is written only after its log has been flushed (WAL). | |
| Datafiles | Store disk table data. Pages are read into the bufferpool and written by the buffer flusher. | |
| Logging | Log Buffer | Records every change before it is applied (log first). |
| Redo Log Files | Logs flushed from the log buffer by the log flush thread or at commit. Used for recovery. | |
| Archive Thread | Copies redo log files to archive log files. Runs only in archive log mode, where a redo log file is deleted only after it has been archived. | |
| Checkpoint | Checkpoint Thread | Writes memory tablespaces to the checkpoint images and requests the buffer flusher to flush dirty pages of the bufferpool. |
| Replication | Replication Sender / Receiver | Send XLogs built from the logs to a remote Altibase server, and apply XLogs received from it. |
For more information on each component, see Structure of Altibase in the Administrator's Manual.