Engineering Glossary

A single set of stashed changes in Git, which can be reapplied later to the working directory.

Automated tests or processes that run when changes are proposed in a Git repository, ensuring code quality and compatibility.

Notifications or updates a user receives about activity in Git repositories they're interested in or contributing to.

The main Git repository that contains submodules, managing references to specific versions of nested repositories.

A symbolic reference in Git that points to another reference, most commonly used for HEAD pointing to the current branch.

A Git object containing metadata about a tag, including the tagger, date, and optional message.

A group of users on a Git platform with shared access permissions to repositories within an organization.

A user with administrative privileges for managing a team's membership and access rights in a Git organization.

A chronological display of events and activities in a Git repository or user profile on hosting platforms.

A short-lived Git branch created to develop a specific feature or fix a particular issue.

Keywords or categories assigned to Git repositories to help users discover related projects on hosting platforms.

A visual representation of visitor activity and clone statistics for a Git repository on hosting platforms.

The process of moving Git objects between repositories during push, fetch, or clone operations.

A Git object representing a directory structure, containing references to blobs (files) and other trees (subdirectories).

A Git object that stores the hierarchy of files and directories in a repository at a specific point in time.

A Git term referring to an object that resolves to a tree, such as a commit, tag, or tree.

A state of a Git branch that has no commits yet, typically seen when initializing a new repository.

The state of the Git index containing conflicting changes from different branches during a merge operation.

A Git object not accessible from any reference, potentially subject to garbage collection if not recovered.

The remote branch that a local branch is set to track, used as a reference for pull and push operations.

An individual account on a Git platform, associated with personal repositories and contributions.

An authenticated request from a Git client to a server, typically for operations like push or fetch.

The unique identifier for a user account on Git platforms, used for authentication and mention notifications.

A team in a Git organization that is visible to all members of the organization, as opposed to secret teams.

A feature allowing users to receive notifications about activity in Git repositories they're interested in.

Alerts received for all notable events in a watched Git repository, including issues, pull requests, and releases.

Alerts displayed on Git platforms' web interfaces, notifying users of relevant activity or mentions.

The directory on your local machine where you modify files before staging and committing them in Git.

The set of files and directories in your project that are currently checked out and available for editing.

A Git feature allowing multiple working directories to be associated with a single repository.

Permission to make changes to a Git repository, including pushing commits and modifying branches.

High-density memory architecture using vertically stacked chips, enhancing performance and capacity in cloud server hardware.

Cloud infrastructure optimized for 5G networks, supporting high-speed, low-latency services and applications.

Technique to create multiple virtual networks on a shared physical 5G infrastructure, each optimized for specific use cases.

Integration of 5G networks with edge computing to enable low-latency, high-bandwidth applications closer to end-users.

Future convergence of 6G networks with cloud computing, promising ultra-high speeds and advanced capabilities.

Database transaction properties (Atomicity, Consistency, Isolation, Durability) ensuring data integrity in cloud environments.

Software ensuring AI systems adhere to ethical guidelines and regulations in cloud deployments.

Software for identifying and mitigating ethical issues and biases in AI models deployed in cloud environments.

Solutions for managing ethical considerations and regulatory compliance in cloud-based AI systems.

Structured approaches for managing AI development, deployment, and use in cloud environments.

Comprehensive solutions for managing, monitoring, and controlling AI models in cloud-based systems.

Cloud-based tools for explaining and understanding the decision-making processes of AI models.

Software for analyzing and explaining AI model decisions, crucial for transparency in cloud AI services.

Cloud platforms for discovering, sharing, and monetizing pre-trained AI models and algorithms.

Tools for tracking AI model performance and identifying deviations from expected behavior in cloud environments.

Systems for managing different versions of AI models and enforcing governance policies in cloud deployments.

Cloud-based development environments that use AI to assist programmers in writing and optimizing code.

Integration of AI capabilities into data analytics processes in cloud environments for enhanced insights.

Use of AI algorithms to predict and optimize resource allocation in cloud infrastructures.

Application of AI techniques to improve efficiency, performance, and cost-effectiveness of cloud resources.

Automated distribution of cloud resources using AI to optimize performance and cost-efficiency.

AI-based automation of cloud service selection and integration for complex workflows.

Automated creation of source code using AI models, often integrated into cloud development platforms.

Automated categorization and labeling of data using AI algorithms in cloud storage and processing systems.

Use of AI to improve network performance, efficiency, and security in cloud environments.

Intelligent distribution of computing resources in cloud environments using AI algorithms.

Enhanced SIEM systems using AI for improved threat detection and response in cloud environments.

Use of AI algorithms to identify and analyze potential security threats in cloud systems.

Proactive search for hidden threats in cloud environments using AI-powered analytics and automation.

Cloud infrastructure components designed or configured to enhance AI workload performance.

Database systems tailored for AI workloads, often featuring in-memory processing and distributed architectures.

Use of AI algorithms to identify unusual patterns or behaviors in cloud systems and data.

Intelligent automation of data and application integration processes in cloud environments using AI.

Cloud-based offering of AI capabilities, allowing businesses to leverage AI without extensive in-house expertise.

Cloud-based AI capabilities offered as a service, enabling easy integration of AI into applications.

Application of AI for automating and enhancing IT operations management in cloud environments.

Integrated solutions leveraging AI for automated monitoring, analysis, and management of cloud IT operations.

Use of AI-driven analytics to forecast and prevent system failures in cloud infrastructure.

Service that protects APIs in cloud environments by managing access, monitoring traffic, and preventing attacks.

Dedicated services for securing and managing APIs in cloud environments, including access control and threat protection.

Design approach prioritizing API creation before implementation, common in cloud-native application development.

Integration strategy using purpose-built APIs to connect data, devices, and applications in cloud ecosystems.

Persistent 3D digital content overlaid on the physical world, accessible via cloud infrastructure for augmented reality applications.

Cloud-based tools for analyzing user behavior and performance in augmented and virtual reality environments.

Cloud-hosted services enabling multi-user interaction in shared augmented or virtual reality spaces.

Specialized CDN optimized for delivering AR/VR content with low latency and high bandwidth.

Cloud-based tools and services for creating, testing, and deploying augmented and virtual reality applications.

JSON-based files defining infrastructure and configuration for Azure resource deployment.

Dynamic UIs that adjust based on user behavior, device capabilities, and context in cloud applications.

Techniques to identify and mitigate attacks on ML models in cloud-based AI systems.

Systems for informing administrators or users about important events or issues in cloud environments.

Process of examining AI algorithms for bias, errors, or unintended consequences in cloud-based systems.

Seamless, context-aware interaction methods for accessing cloud services in IoT environments.

Tools for identifying unusual patterns or behaviors in cloud systems, often using machine learning techniques.

Network management approach that optimizes performance based on specific application requirements in cloud environments.

Technique for quickly estimating query results in large-scale cloud databases, trading accuracy for speed.

Low-cost cloud storage for infrequently accessed data with longer retrieval times, e.g., Amazon Glacier, Azure Archive Storage.

Cloud-based storage for software build outputs, dependencies, and related metadata.

Hypothetical cloud offering of human-level AI capabilities across various domains.

Cloud-based environments for developing and testing advanced AI systems approaching human-level intelligence.

Systematic recording of actions and events in cloud systems for security and compliance purposes.

Chronological records of system activities for reconstructing and examining the sequence of events in cloud environments.

Integration of machine learning and natural language processing in cloud-based data analytics workflows.

Shared, persistent digital content overlaid on the physical world, accessible via cloud infrastructure.

Cloud-based systems for managing and delivering AR content and experiences, enabling scalable AR applications.

Cloud-powered generation of AR graphics and content, offloading processing from end-user devices.

Collections of EC2 instances that automatically adjust capacity based on defined conditions.

Automatic adjustment of cloud resources to match workload demands, ensuring optimal performance and cost-efficiency.

Automated machine learning processes for model selection, hyperparameter tuning, and feature engineering in cloud environments.

Cloud-based services automating the machine learning pipeline from data preparation to model deployment and monitoring.

AI-driven tools for improving efficiency and performance of machine learning workflows in the cloud.

Systems that automatically implement and maintain cloud resource policies and compliance.

Continuous, AI-driven assessment of cloud systems against regulatory and security standards.

AI-powered tools for identifying, categorizing, and mapping data assets in cloud environments.

AI-driven systems for managing data quality, security, and compliance in cloud environments.

Cloud-based tools using AI to clean, transform, and prepare data for analysis, streamlining data preparation processes.

AI-powered generation and selection of features for machine learning models in cloud environments.

AI-driven coordination of security incident detection and resolution in cloud systems, automating response workflows.

Cloud services that automate the process of creating and optimizing machine learning models, from data prep to deployment.

Cloud-based systems that automate the end-to-end machine learning model development process, including feature engineering and model selection.

AI-driven tools for simulating cyberattacks to identify vulnerabilities in cloud systems and applications.

AI-powered analysis of cloud architectures to identify potential security risks and attack vectors.

Self-managing, self-healing cloud services requiring minimal human intervention, leveraging AI for operations.

Ultra-low latency edge computing extensions of Azure for 5G networks, bringing cloud resources closer to users.

Service for creating, assigning, and managing policies to control Azure resources and ensure compliance.

Cloud-based services facilitating data exchange and process integration between business partners.

Architectural approach creating backend services tailored to specific frontend application needs in cloud environments.

Physical server dedicated to a single tenant, offering direct hardware access in cloud environments.

Dedicated physical servers without virtualization, offered as a cloud service for high-performance workloads.

Execution of series of jobs without user interaction, often for large-scale data processing in the cloud (e.g., AWS Batch, Azure Batch).

Distributed computing environments for processing and analyzing massive datasets in the cloud.

Interface for monitoring and managing cloud service usage and costs, providing detailed breakdowns and forecasts.

Use of cloud resources for computational biology and genomics research, enabling large-scale analysis and modeling.

Evaluation of cloud data center effects on local ecosystems and wildlife to ensure sustainable operations.

Cloud storage that provides fixed-size raw storage volumes, typically used for databases or file systems.

Cloud services providing persistent block-level storage volumes for use with compute instances.

Cloud-based tools for analyzing and visualizing blockchain data and transactions, offering insights into network activity.

Distributed databases using blockchain technology for enhanced security and immutability in cloud environments.

Software for managing and enforcing rules, permissions, and consensus mechanisms in blockchain networks deployed on cloud platforms.

Cloud-based solutions for connecting blockchain networks with existing enterprise systems and applications.

Object storage gateway for Ceph, providing S3-compatible API for container storage needs in Kubernetes.

Linux kernel feature for limiting, prioritizing, and isolating resource usage of container groups.

Technique for tracking and capturing changes in databases, useful in microservices architectures.

Practice of intentionally injecting failures in CI/CD pipelines to improve system resilience.

Platform for simulating various abnormal scenarios in Kubernetes environments to test reliability.

Static code analysis tool for detecting misconfigurations in Infrastructure as Code deployments.

Open-source networking, observability, and security solution for container workloads based on eBPF.

eBPF-powered service mesh offering high-performance traffic management and security for microservices.

Observability platform for Kubernetes providing deep visibility into container network flows.

High-performance networking mode in Cilium using extended Berkeley Packet Filter for packet processing and security.

Continuous integration and delivery platform supporting containerized application testing and deployment.

Fault tolerance pattern preventing cascading failures in distributed containerized systems.

Technique to detect failures and prevent system overload in microservices architectures, enhancing resilience.

Design pattern for handling large payloads in microservices by storing data externally, improving efficiency.

Open-source tool for static analysis of vulnerabilities in container images, enhancing security.

Kubernetes component managing interactions between cluster and cloud provider APIs, enabling cloud integration.

Specification for packaging and managing distributed applications across different environments.

Tooling for building container images from source code without Dockerfiles, adhering to best practices.

Architectural patterns specifically tailored for distributed, containerized applications in cloud environments.

Specification for describing event data in common formats, facilitating event-driven architectures in cloud environments.

Isolation technique in containerized microservices to prevent failure propagation across the system.

Group of servers or other resources that work together as a single system to provide high availability.

Kubernetes project for declarative management and provisioning of clusters using Kubernetes-style APIs.

Implementation of Cluster API for specific infrastructure providers, enabling cluster lifecycle management.

Kubernetes component that automatically adjusts the size of a cluster based on resource demands.

Process of estimating and allocating resources needed for container workloads in a cluster.

Mechanism for coordinating multiple Kubernetes clusters, enabling multi-cluster application deployment and management.

Interconnected network of container clusters, enabling cross-cluster communication and resource sharing.

Network configuration and management within and between container clusters, enabling inter-container communication.

Procedure for updating the Kubernetes version and components of a cluster while minimizing disruptions.

Centralized logging solution capturing logs from all containers and nodes in a cluster, aiding in troubleshooting.

Kubernetes component that automatically adjusts the number of nodes in a cluster based on resource utilization.

Kubernetes service type that exposes the service on an internal IP within the cluster, facilitating internal communication.

Kubernetes services accessible only within the cluster, used for internal communication between pods.

Kubernetes RBAC resource defining permissions across an entire cluster, not limited to a single namespace.

Kubernetes RBAC resource that binds a ClusterRole to users, groups, or service accounts across all namespaces.

Custom resource in Operator Lifecycle Manager describing a specific version of an Operator.

GitOps platform for managing and automating containerized application deployments, streamlining CD workflows.

Techniques to reduce initialization time of containers, particularly important in serverless environments.

Design pattern for handling failures in distributed container-based systems by reversing or compensating actions.

Kubernetes API object used to store non-confidential data in key-value pairs, accessible by pods.

Service mesh feature of Consul providing secure service-to-service communication with automatic TLS encryption.

Standardized unit of software that packages code and all its dependencies for quick, reliable deployment.

Methods used by attackers to escape container isolation and access the host system, posing security risks.

Software responsible for managing container lifecycle, including creation, execution, and destruction.

Security vulnerability allowing a process to break out of container isolation and access the host system.

Security measures and best practices to prevent containers from breaking out of their isolation.

Weaknesses in container runtimes or configurations that could allow processes to escape isolation.

Mechanisms to verify the health and readiness of containerized applications, ensuring service availability.

Physical or virtual machine running the container runtime and hosting containers, providing the execution environment.

Process of moving container images through different environments (e.g., dev, test, prod) in a controlled manner.

Cryptographic process of digitally signing container images to ensure their integrity and authenticity during distribution.

Stages a container goes through from creation to termination, including running, paused, and stopped states.

Processes and tools for managing containers throughout their lifecycle, from creation to deletion.

Process of capturing and managing log output from containerized applications for monitoring and troubleshooting.

Configuration file specifying how to build a container image, including base image, commands, and environment setup.

Quantitative measures of container performance, resource usage, and health, used for monitoring and optimization.

Specification and libraries for configuring network interfaces in Linux containers, standardizing networking.

Standard for developing plugins to configure network interfaces in Linux containers, ensuring interoperability.

Architecture and principles governing how containers communicate within and across hosts in orchestrated environments.

Automated arrangement, coordination, and management of software containers, crucial in large-scale deployments.

Kubernetes mechanisms (liveness, readiness, startup) for checking container health and controlling lifecycle.

Technique for capturing and analyzing real user interactions with containerized applications.

Rules defining how containers should be restarted in case of failures or exits, enhancing application resilience.

Software responsible for running containers, managing their lifecycle from creation to deletion.

Measures and tools to protect containers during execution, preventing unauthorized access or malicious activities.

Lightweight processes that manage the lifecycle of containers and provide abstraction between runtimes.

Standardized interface for container orchestration platforms to interact with storage systems.

Standard for developing storage plugins for container orchestration platforms, enabling storage extensibility.

Process of identifying security vulnerabilities in container images and their dependencies.

Mechanism for verifying the integrity and authenticity of container images before deployment.

Automated process of releasing container images to production environments after passing tests.

Ongoing process of validating deployed containers against defined policies and expectations.

Container networking solution using VPP (Vector Packet Processing) for optimized performance.

Approach prioritizing API definition before implementation, crucial for microservices architecture.

Linux kernel feature for limiting, prioritizing, and isolating resource usage of container groups.

Components managing the overall state of a container cluster, including API server, scheduler, and controllers.

Process of updating the core components of a container orchestration system while maintaining cluster stability.

Kubernetes component running controller processes to regulate the state of the cluster, maintaining desired state.

Software framework for building Kubernetes controllers and operators, simplifying custom resource management.

Kubernetes feature allowing custom resource API version conversions via external webhooks.

Storage optimization technique used in container filesystems to reduce duplication and improve efficiency.

Process of marking a node as unschedulable in Kubernetes, preventing new pods from being assigned to it.

Flexible, extensible DNS server used for service discovery in Kubernetes clusters, replacing kube-dns.

Horizontally scalable, multi-tenant, long-term storage for Prometheus metrics, enhancing monitoring capabilities.

Use of Cortex to provide isolated Prometheus monitoring for multiple users or teams in shared environments.

Kubernetes object for creating time-based jobs, running containers on a schedule for automated tasks.

Kubernetes patterns for running batch processes and scheduled tasks in containerized environments.

Kubernetes operators capable of managing resources across multiple namespaces, enabling broader automation.

Kubernetes API extension allowing pods to consume custom metrics for autoscaling and monitoring.

Extension of the Kubernetes API that defines new, custom resource types specific to a cluster's needs.

Process of converting custom resources between different API versions in Kubernetes, enabling API evolution.

Kubernetes API extension allowing the definition of custom resources, enabling cluster customization.

Kubernetes feature for extending the API with custom resources, enabling cluster customization.

User-defined API objects in Kubernetes, extending the core functionality of the platform for specific use cases.

Alternative or additional scheduler implementation for Kubernetes, allowing custom pod placement logic.

Alternative scheduling implementations in Kubernetes for custom pod placement strategies, enabling specialized scheduling logic.

Kubernetes feature providing DNS-based service discovery for containers within the cluster.

Use of Data Plane Development Kit for high-performance packet processing in container networks.

Kubernetes object ensuring that all (or some) nodes run a copy of a specific pod, useful for cluster-wide services.