Glossary

Docker image that can be mounted inside projects using one of the integrated technologies. Persistent storage can be assigned to an app to keep data in a defined volume path when the app is stopped.

Container-native workflow engine for orchestrating parallel jobs on Kubernetes. For more information, see the Argo documentation.

Rights granted to groups through the Security module. These rights include access to specific features of the app, access to datasets, and editing rights on individual projects.

Component created by Saagie to import files for jobs and apps. Files are managed on a Kubernetes platform and accessible across that platform. Conf’o’rama’s API is exposed and can be used by Saagie users working with Kubernetes clusters.

Collection of data accessible on the Governance data portal.

Set of rules defining which groups can access which datasets in Saagie.

Login information stored in projects allowing you to pull Docker images from private registries when creating apps.

Entity in the Governance module that groups datasets. Domain organization is flexible to fit the company’s data organization (for example, by geography, branch, or team).

Dynamic values that can be referenced in jobs, limiting the need to modify job execution code each time the value of the variable changes.
Environment variables can be created at the platform (global) or project level to ensure proper control over who can access and use the variables.

Multi-platform log processor and forwarder that collects data and logs from different sources, then unifies and sends them to multiple destinations. For more information, see the Fluent Bit documentation.

RedHat tool used for Identity Management. For more information, see FreeIPA.

Entity in which a selection of users is placed. Groups are granted authorizations in the Projects and Governance modules. When an administrator grants authorizations to a group, each user in that group receives those authorizations.

Helm Charts help you define, install, and upgrade Kubernetes applications. For more information, see the Helm documentation.

A single run of a job or pipeline in a project. The execution information and app and job logs for all instances are saved on your platform.

Computation task performed inside projects on Saagie using one of the integrated technologies. Jobs run through a command line and can be launched individually (in both manual and scheduled modes) or as part of a data pipeline.

Also called Apache Kafka, it is a distributed streaming platform used to facilitate communication between systems and applications. It must be used with ZooKeeper. In Saagie, Kafka is used to manage communication between Saagie components. For more information, see the Kafka documentation.

Security-oriented federation and identity provider (IdP) server. In Saagie, Keycloak is used with LDAP to get security tokens. For more information, see the Keycloak documentation

Legacy user interface of Saagie. It allows the creation of extraction, processing, and smart app jobs, as well as access to data lake and data mart services. In the Manager module, all jobs are listed in a single menu, while in the Projects module, they are organized by project to sort them more easily.

Tool used in Saagie legacy orchestration. Chronos schedules jobs in Mesos. Marathon ensures that jobs restart automatically if a job fails in Mesos.

Object storage server. It is compatible with Amazon S3 cloud storage service. In Saagie, MinIO is installed in the Kubernetes cluster to store files. For more information, see the MinIO documentation.

Document-oriented NoSQL database that uses JSON-like documents with optional schemas. Queries are made in JavaScript. For more information, see the MongoDB documentation.

Relational database management system. For more information, see the MySQL documentation.

End-to-end process encompassing multiple jobs that are connected and executed within projects. A pipeline can include advanced orchestration logic, such as conditions or parallel job executions.

Kubernetes controller created by Saagie to manage CRD platforms in a Kubernetes cluster.

Relational database management system. For more information, see the PostgreSQL documentation.

Kubernetes controller created by Saagie to manage CRD projects in a Kubernetes cluster.

Component created by Saagie to manage projects and their elements, such as jobs, apps, or pipelines. Projects-and-jobs' API is exposed and can be used by all Saagie users.

Secures and manages security isolation for a given Saagie customer. In Saagie, it is a string used in the application URL and request headers.

Component created by Saagie to store Docker credentials used for private images in jobs and apps.

Persistent storage that can be allocated to an app to retain data in a defined volume path.

Single Saagie account created on one or more platforms. Authorizations are granted to users by administrators.

Single iteration of a job, pipeline, or app. Each new update is stored as a version, enabling you to roll back to previous iterations and keep track of successive changes.

Kubernetes resource created by Argo that facilitates the creation and management of workflows. In Saagie, we use it to operate pipelines and jobs.

Centralized service used to maintain configuration information and provide distributed synchronization and group services. In Saagie, ZooKeeper is mainly used to maintain and operate a Kafka cluster. For more information, see the ZooKeeper documentation.