Appendix A Glossary
The terms used in this document are listed in the following table.
| Term | Definition |
|---|---|
| at‑least‑once delivery | In case of failures that lead to message loss or taking too long to recover from a failure, messages are retransmitted to assure they are delivered at least once. |
| benchmarking | Process of testing and evaluating the performance of a system or component. |
| change capture | Process of identifying and capturing changes made to a data source. |
| Cloud events | Specification for describing event data in a common way. |
| delta database | Database that stores and manages changes (deltas) to data over time. |
| event | Record of a state change in the system. |
| event hubs | Multi‑protocol event streaming engine provided by Microsoft as part of its Azure Cloud Service. |
| event schema | Structure and format definition for events in a streaming system. |
| Event Schema Generator (ESG) | Utility for generating Event Schema files for a Jade Event class. |
| Event Stream Producer (ESP) | Component that generates and sends events into a streaming system. |
| event streaming | Practice of capturing, processing, and storing real‑time data streams. |
| event structure | Defined format and composition of an event in a streaming system. |
| external storage provider | System or service that provides storage capabilities outside the main event streaming infrastructure. |
| Jade event | Specific type of event structure used in the system described in the document. |
| JSON (JavaScript Object Notation) |
Lightweight data interchange format that is easy for humans to read and write and easy for machines to parse and generate. Used for serializing objects before transmission over the web. |
| JSON schema | Defines the structure and validation rules for JSON data. |
| Kafka | Distributed event streaming platform and API provided and defined by the Apache Software Foundation. |
| Proof of Concept (PoC) | Realization of a certain method or idea in order to demonstrate its feasibility. |
| RSA (Rivest–Shamir–Adleman encryption algorithm) | Validates the signature of a JSON Web Token. |
| schema caching | Practice of temporarily storing schemas in memory for quick access and improved performance. |
| schema registry | System for storing and retrieving schemas, often used in event streaming architectures. |
| serialization | Process of converting data structures or objects into a format that can be easily stored or transmitted. |
| serialization error handling | Process of managing and responding to errors that occur during the serialization of data. |
| topic | Category or feed name to which records are published in a streaming system. |
| URI (Uniform Resource Identifier) | Generic term for all types of names and addresses that refer to objects (for example, a URL) on the Internet. Commonly used term when talking about REST. |
