Skip to main content

Glossary

How to use the Glossary

Here are the technical terms used in StackSpot and examples of usage. Before using a term, check how it should be used according to the documentation standards.

Account

  • Definition: An organization (Enterprise) account connected to GitHub.
  • Example: “The Enterprise Account allows the organization to configure and manage specific functionalities“.

Account Admin

  • Definition: A person with administrative privileges in a StackSpot account.
  • Example: “Set specific access permissions for different users as an Account Admin“.

Account Holder

  • Definition: A person responsible for an account or with broad administrative permissions on the platform.
  • Example: “Grant administrative privileges to an account holder to manage accounts on the platform“.

Action

  • Definition: Executes automation remotely or locally to optimize processes.
  • Example: “Actions allow automating repetitive processes and integrating different systems, making it easier for developers to execute commands and tasks efficiently“.

Application

  • Definition: A code project created and managed in an Environment through StackSpot.
  • Example: “Applications use StackSpot resources and Plugins to create projects quickly and in a standardized way“.

Appearance

  • Definition: Customization options such as light and dark modes and language selection on the platform.
  • Example: “Customize the platform's appearance, including light and dark modes, for a comfortable experience“.

Cloud

  • Definition: Remote computing that offers storage and processing via the internet.
  • Example: “Connect a Cloud account to deploy applications on StackSpot“.

Cloud Provider

  • Definition: Companies that offer computing, storage, and application services over the internet, such as AWS, Microsoft Azure, and Google Cloud.
  • Example: “Set up a Cloud Provider account to deploy your applications on StackSpot“.

Cloud Services

  • Definition: A solution for running and managing applications in the cloud, offering analysis, security, and optimization.
  • Example: “StackSpot Cloud Services provides a complete solution for running and managing your applications in the cloud“.

Connection Interface

  • Definition: Defines the necessary parameters for cloud resources to connect and be compatible.
  • Example: “Create a Connection Interface in the Workspace to connect an existing cloud resource“.

Connection Interface Type

  • Definition: Defines a standard set of attributes to ensure compatibility between cloud components.
  • Example: “Using Connection Interface Types facilitates resource integration, ensuring compatibility“.

Content

  • Definition: Items created by the StackSpot Engine, such as Stacks, Starters, Plugins, and Actions, focused on reusability.
  • Example: “Develop Content like Plugins and Stacks in Studios and use them to create applications in Workspaces“.

Context

  • Definition: Predefined Plugin and Action input values are configured to standardize development.
  • Example: “Set the Context of a Python Stack at the Account level to standardize inputs“.

Workflow Context

  • Definition: In the StackSpot EDP Portal, the Workflow Context defines the input values for Actions in a Workflow.
  • Example: “When creating an application in the Portal, the input values for Actions are configured by the Workflow Context specific to application creation“.

Dashboard

  • Definition: A visual interface that presents summarized information and key metrics.
  • Example: “Use a dashboard to monitor Cloud performance in real-time“.

Deploy

  • Definition: The process of putting an application or update into production.
  • Example: “Deploy your application on StackSpot to make it available in a production environment with all infrastructure resources provisioned“.

Dev

  • Definition: Short for developer, responsible for creating and maintaining Applications and systems.
  • Example: “Devs are working on new features for the next Application version“.

Drift

  • Definition: The difference between a system's current and planned configuration, usually caused by unrecorded changes in the central code.
  • Example: “Drift occurs when an urgent change is made directly on the production server without updating the code in the central repository, creating differences between environments“.

DynamoDB Repository

  • Definition: A NoSQL storage mechanism using Amazon DynamoDB, known for its scalability and low latency.
  • Example: “The project uses a DynamoDB Repository to store and query data in a scalable and efficient way“.

Environment

  • Definition: Groups applications and cloud resources to facilitate organization and identification.
  • Example: “Creating Environments is essential to organize and isolate different phases of the development cycle, ensuring that the configurations and data of one Environment do not interfere with another“.

Guard Rails

  • Definition: Policies and configurations in cloud environments to ensure security and compliance.
  • Example: “Guard rails to ensure that cloud operations follow security and compliance best practices“.

Infrastructure

  • Definition: A set of resources created by Stacks and Infrastructure Plugins to manage and scale applications.
  • Example: “Infrastructure in StackSpot optimizes resources and facilitates management across multiple applications“.

Insights

  • Definition: A customizable data panel that facilitates the visualization and analysis of information.
  • Example: “Use insights from the panel to identify trends and make strategic decisions“.

Mandatory

  • Definition: Something required by regulations, standards, or organizational policies.
  • Example: “All operations must comply with security standards“.

Permissions

  • Definition: Defines which actions can be performed on resources within the platform.
  • Example: “To create a Plugin, you need specific permissions in a Studio.“

Plugin

  • Definition: Adds capabilities to an Application, following standards and best practices.
  • Example: “Plugins extend the application's functionalities, allowing for modular customization“.

Reconciliation

  • Definition: The comparison and adjustment of records to ensure data accuracy.
  • Example: “Compare database records to reconcile data between servers“.

Relational Repository

  • Definition: A data storage system in relational tables, using SQL for manipulation and querying.
  • Example: “The project involves creating a Relational Repository to store and access data efficiently using SQL“.

Required

  • Definition: Something necessary or obligatory to achieve a specific goal.
  • Example: “Filling in the required fields is necessary to complete the registration successfully“.

Rollback

  • Definition: The process of reverting a system or application to its previous state after a failed update or deployment.
  • Example: “After a failed deployment, perform a Rollback to restore the application to its previous state“.

Saving Plans

  • Definition: Programs that offer discounts in exchange for a commitment to regular spending with cloud providers.
  • Example: “Saving Plans help save money in the cloud with discounts for spending commitments“.

Slug

  • Definition: A user-friendly version of the text for a URL used to make web addresses more readable.
  • Example: “Create meaningful slugs for the content URLs in StackSpot“.

Spring Boot Microservice

  • Definition: An independent component developed with Spring Boot, focused on a single functionality within a microservices architecture.
  • Example: “The team is creating a Spring Boot Microservice to manage user authentication“.

Stack

  • Definition: A set of Plugins that provide the necessary technologies to create an Application.
  • Example: “The Stack groups the necessary technologies and Plugins, making it easier to create Applications“.

StackSpot AI Assistant

  • Definition: An AI-first tool that enhances code quality and accelerates development, offering direct support in the IDE.
  • Example: “Those using the StackSpot AI Assistant perform code analysis more efficiently“.

StackSpot Cloud Services

  • Definition: Provides tools for high-performance and scalable cloud processing.
  • Example: “StackSpot Cloud Services simplifies cloud infrastructure management, allowing developers to focus on development“.

StackSpot Runtime Engine

  • Definition: Manages the provisioning of cloud resources and configures the necessary infrastructure for applications.
  • Example: “The StackSpot Runtime Engine reduces complexity by managing infrastructure configurations“.

Starter

  • Definition: A predefined set of Plugins that serves as a starting point for creating an Application.
  • Example: “Use a Starter to apply a pre-configured combination of Plugins when creating an Application“.

Studio

  • Definition: Allows the centralized creation and distribution of software, such as Plugins and Actions.
  • Example: “To distribute content on StackSpot like Plugins and Actions, use a Studio to manage the content published in your StackSpot account“.

Teams

  • Definition: Groups of people designated to create and use content in spaces like Studios and Workspaces.
  • Example: “Teams collaborate and produce content in Studios and Workspaces“.

User

  • Definition: A person who uses a product or service.
  • Example: “Conduct usability tests as a user to find improvements in StackSpot“.

Username

  • Definition: A unique name used to identify and authenticate a person in the system, essential for access and security.
  • Example: “The username is essential to access your account and perform activities on the platform“.

Workspace

  • Definition: A configurable environment where developers access and use specific content to create and deploy applications.
  • Example: “Creating Workspaces allows standardizing and organizing the development and deployment of Applications, making it easier for developers and SREs to use pre-configured content“.