The low-level API section covers the native engine layer directly. It is the right place when you want byte-oriented storage control, server access to the engine, replication/runtime behavior, or history and rollback primitives.
Components
Section titled “Components”| Component | What to read |
|---|---|
AkkEngine | Core byte key/value operations, scans, options, stats, storage behavior, and direct engine lifecycle. |
| API Server | HTTP, TCP, and gRPC access to an AkkEngine instance from another process. |
| Cluster | Primary/replica runtime, replication, routing, and node configuration. |
| VersionLog | Historical values, point-in-time reads, rollback, file layout, and operational limits. |
Read By Goal
Section titled “Read By Goal”| Goal | Page |
|---|---|
Use AkkEngine directly | AkkEngine Usage |
| Understand the engine storage path | AkkEngine Architecture |
| Configure engine options | AkkEngine Options |
| Inspect runtime counters | AkkEngine Stats |
| Expose the engine over a network API | API Server |
| Run primary/replica replication | Cluster |
| Use history and rollback | VersionLog |
Use the high-level API instead when your application mainly wants typed C++ structs and table-like operations.