12.3. Linux Base Libraries¶
To facilitate clean and regular updates and to minimize container sizes, GEISA applications are encouraged to take advantage of libraries provided by the base GEISA environment whenever possible.
The GEISA API is defined at the protocol / transaction level and does not mandate a specific application SDK, programming language, or application implementation. GEISA does define a baseline set of runtime and application libraries provided by the platform for use within the GEISA Linux Execution Environment. Applications MAY include additional libraries that are not part of this baseline.
12.3.1. C Language and Toolchain-provided Runtime Libraries¶
The following runtime libraries are part of the GEISA baseline. The specific implementation may vary by platform and toolchain.
libc - Core runtime support
libgcc - GNU C Compiler Collection (low-level runtime support)
libstdc++
libatomic - Atomic operations
libcrypt - Password hashing
libdl - Dynamic loading
libm - Math library
libpthread - POSIX Threads
libresolv - DNS resolution and name services
librt - Real-time
libcap - POSIX capabilities
12.3.2. Common Application Libraries¶
The following common application libraries, or function-compatible alternate implementations as described below, MUST be provided by the platform and available to applications within the GEISA execution environment:
libcrypto - OpenSSL (hashing, encryption, digital signatures, random numbers, certs/keys)
libnsl - Network Services Library
libz - Compression
libmosquitto - MQTT client implementation
A platform implementation MAY provide an alternate library implementation in place of one of the named libraries above, provided that the alternate implementation is function-compatible with the named library.
12.3.3. Optional Application Libraries¶
Platform implementations MAY provide additional commonly used libraries in the base GEISA environment. When provided as part of that environment, these libraries MUST be available to GEISA applications within their execution environment.
Examples include:
libasyncns - Asynchronous Name Service
libutil - Users, groups, pseudo-ttys (pty), etc.
libprotobuf - C++ protobuf implementation
Applications MAY include additional libraries or alternate implementations when needed.
Note
Applications MAY use a platform-provided libprotobuf when suitable, or another protobuf implementation such as one listed in Third-Party Add-ons for Protocol Buffers.