With the introduction of containerized AtScale, there are many new concepts and terms used. Note that the following terms are used interchangeably: containerized AtScale, container-based AtScale, containers, C-AtScale, C-Releases.
The purpose of this glossary is to help Customers improve their understanding.
API Service
A collection of proprietary AtScale application programming interfaces that allow developers to communicate and/or integrate functionality with AtScale.
Catalog
The result of a Deployed repository. This is known as a ‘published project’ in the installer-based AtScale.
Commit
This is a valid command for a ‘repo’. It propagates your data model changes to Git (source control). This does not deploy anything in the engine service.
Data Model
An AtScale data service consisting of measures and dimensions (queryable via ODBC, JDBC, XMLA and HTTP protocols using SQL, MDX or DAX query languages). Not a completely new term, but the term ‘cube’ is retired in favor of ‘data model’.
Deploy
A command that propagates the catalog to the AtScale engine service, based on the selected repository. This enables BI Tool(s) to query the data model(s) contained in the catalog.
Engine Service
The AtScale engine service is responsible for holding an active data model for which it receives queries. Query planning, parsing, delivery to underlying data platform, retrieve return, query response work and delivery to analytics applications.
Git Token
This is the password token that allows AtScale to connect to source control (e.g. Git).
Helm Chart
A package that contains all the necessary resources to deploy an application to a Kubernetes cluster. This includes YAML configuration files for deployments, services, secrets, and config maps that define the desired state of your application.
Identity Broker Service
An intermediary service that connects multiple service providers with different identity providers. As an intermediary service, the identity broker is responsible for creating a trust relationship with an external identity provider in order to use its identities to access internal AtScale services.
Ingress Controller
Acts as a reverse proxy and load balancer. It implements a Kubernetes ingress. The ingress controller adds a layer of abstraction to traffic routing, accepting traffic from outside the Kubernetes platform and load balancing it to AtScale services running inside the platform.
Log Storage
Raw telemetry data will be stored in an object store. AtScale provides an object store service or the customer can opt to store this data in an existing S3 object store.
Logging Agent
A program that reads logs from one place and delivers them to another.
Message Broker Service
Software that enables applications, systems and services to communicate with each other and exchange information.
Object Store
A data storage architecture for storing unstructured data, which sections data into units—objects—and stores them in a structurally flat data environment.
Observability Dashboarding Service
A graphical representation of aggregated metrics to monitor the health of a system. Measuring events, latency and resource allocation / usage are key metrics to give the administrator a view into system performance and potential issues.
Package
A package is an additional Git repository whose objects can be used in the current repository. It enables you to share objects between multiple repositories and models.
Repo
A nickname for a Git repository. This is known as a ‘draft project’ in the installer-based AtScale.
Row Security
Part of the data model. Also known as the AtScale security dimension in the installer-based product.
Secrets Broker Service
Manages, retrieves, and stores system credentials and other secrets throughout their lifecycles. Secrets managers help you improve your security posture, because you no longer need hard-coded credentials in application source code. The secret broker can act as it’s own manager or broker to a third-party secrets manager like HashiCorp Vault, or AWS Secrets Manager.
Service Mesh
A tool that inserts security, observability, and reliability features to applications at the platform layer instead of the application layer.
Services Database
Internal database used by all AtScale services for internal purposes.
SML
An acronym for Semantic Modeling Language - an AtScale-provided modeling language that data engineers can use to create projects and models to be used within AtScale.
Telemetry Collector Service
A service for gathering, processing and exporting telemetry data to pre-configured destinations.
Tracing Storage Service
Raw tracing telemetry data will be stored in an object store. AtScale provides an object store service or the customer can opt to store this data into an existing S3 object store.
Web UI Service
This is the AtScale data modeling front-end user interface (UI).