Glossary
These definitions describe how terms are used across the Exaloop guides, API references, and deployment workflows.
| Term | Meaning in Exaloop |
|---|---|
| ABI | Application binary interface: calling conventions, layouts, and symbols that allow native components to work together |
| Distribution | A matched release of the compiler, CLI, SDKs, code generators, and supporting native tools |
| SDK | An integration's Codon modules, native libraries, and build tools |
| Native application | A compiled executable that runs directly on the host; explicit Python interoperability may add a Python dependency |
| Runtime package | An application and its collected non-system native libraries, without the development compiler |
| UDF | User-defined function, such as a Codon function registered with a database |
| Server extension | Native code loaded into a database process, subject to that host's ABI and privileges |
| Owned data | Storage whose lifetime is retained by the returned object or handle |
| Borrowed data | A view into storage owned elsewhere; the owner must keep it valid while the view is in use |
| PGO | Profile-guided optimization: compiler decisions informed by execution counts from representative training runs |
| Holdout workload | Inputs reserved for evaluating a selected candidate, rather than selecting that candidate |
| XRay | The native function-instrumentation backend used for call tracing |
| RSS | Resident set size: memory currently resident for the process, including native libraries and runtime state |
| Idempotency | A property that allows repeating an operation without duplicating its externally visible effect |
| Kafka committed offset | The position from which a consumer group resumes in a partition; committing a message records its offset plus one |