We try to make Apache Ignite reasonably modular in order to simplify unit and integration testing. Each module provides an exposed API which should be used by external modules. Not exposed APIs must not be used by external modules. At the time of writing we do not use Java JIGSAW modules system, but it is likely that we will at some point, which will help us to control the exported API contract.
We prohibit cyclic dependencies between modules in order to simplify JIGSAW migration in the future.
| Module Name | Description |
|---|---|
| api | Ignite public API. |
| bytecode | Ignite Bytecode module. |
| cli | Ignite CLI implementation |
| cli-common | Shared interfaces definitions for pluggable CLIng |
| configuration | Ignite configuration classes and configuration management framework |
| configuration-annotation-processor | Tooling for generating Ignite configuration model classes from configuration schema definition |
| core: causality tokens | Causality tokens |
| core: local state recovery | Local state recovery |
| network | Networking module: group membership and message passi |
| rest | REST server and Open API spec generation |
| rest-api | REST API interfaces |
| runner | Ignite server node runner. The module that wires up the Ignite components and handles node lifecycle. |
| schema | Ignite schema API implementation and schema management classes. |
| table | Ignite table API implementation. |
| vault | Ignite local persistent key-value storage. |