Engineering Glossary

A feature in Git platforms that allows users to notify specific team members or reference issues by using the @ symbol followed by a username.

A feature allowing developers to test and provide feedback on new Git API functionality before it's officially released.

A Git repository containing version control information without a working directory, typically used as a central repository for collaboration.

A Git command used to perform a binary search through a repository's history to identify the commit that introduced a bug or issue.

An integrated CI/CD service in Bitbucket for automating builds, tests, and deployments.

A Git feature that shows which user last modified each line of a file, helping developers trace changes and understand code history.

A collaborative process of analyzing Git blame information to identify the source of bugs or issues in a codebase.

A parallel version of a repository, allowing developers to work on different features or experiments without affecting the main codebase.

Rules enforced on Git branches to ensure code quality, require reviews, or restrict certain actions before merging.

A premium subscription tier offered by Git hosting services, providing advanced features and support for enterprise users.

A digital certificate issued by a Certificate Authority, used in Git to establish secure HTTPS connections and verify server identities.

A temporary storage area that holds frequently accessed data for quick retrieval, improving system performance.

A Git command used to switch between different branches or restore files from a specific commit in a repository's history.

A Git operation that applies the changes from a specific commit to the current branch, useful for selective code integration.

The practice of selecting and applying specific commits from one branch to another in Git, often used for targeted bug fixes.

The process of creating a local copy of a remote Git repository, allowing developers to work on the codebase independently.

A file specifying individuals or teams responsible for code in different parts of a repository.

Operation in version control systems that saves changes to the local repository, creating a new revision with a unique identifier.

A situation in Git where incompatible changes have been made to the same part of a file, requiring manual resolution before merging.

Practice of merging all developer working copies to a shared mainline several times a day.

Directed Acyclic Graph, the underlying data structure used by Git to represent the commit history and relationships between commits.

A Git operation that moves the HEAD pointer to a specific commit, allowing for temporary exploration of historical states.

A Git command or operation that shows the differences between two commits, branches, files, or other Git objects.

Refers to the direction of change propagation in Git, typically from a parent branch to its child branches or forks.

A feature in Git platforms for browsing repository contents, viewing files, and navigating through different branches.

A Git pattern where each new feature is developed in a dedicated branch, then merged back to the main branch.

A Git command that retrieves changes from a remote repository without automatically merging them into the local branch.

A Git push operation that overwrites the remote branch's history with the local branch, potentially causing data loss if used carelessly.

A personal copy of another user's repository on a Git hosting platform, allowing independent development without affecting the original project.

A no-cost tier offered by Git hosting services, typically with limited features and storage for individual users or small projects.

An encryption software used with Git for signing commits and tags, enhancing security and verification.

A simple way to share code snippets, notes, or small files using Git, often integrated into Git platforms.

Distributed version control system for tracking changes in source code during software development.

A custom shortcut command defined by users to simplify complex or frequently used Git operations.

A mechanism in Git allowing a repository to borrow objects from another repository, useful for saving disk space in large projects.

A Git command that shows the author and commit information for each line in a file, similar to the "blame" feature.

A Git feature that tells the system to temporarily ignore changes to a tracked file, useful for local configuration files.

A mechanism in Git for defining attributes on a per-path basis, controlling how Git handles certain files or directories.

A Git command used to perform a binary search through the commit history to find the commit that introduced a bug.

An automated version of Git Bisect that uses a script to determine if each checked-out commit is "good" or "bad".

An enhanced version of Git Blame that detects lines moved or copied from other files, providing better change tracking.

A Git command that creates a single file containing all the data needed to recreate a repository's branch or history.

Commands to create and verify Git bundles, useful for transferring repository data without using a network.

A quick reference guide summarizing common Git commands and their usage, helpful for both beginners and experienced users.

A Git command used to find commits that haven't been merged upstream, useful for identifying changes to be applied to another branch.

A command to remove untracked files from the working directory, helping to maintain a clean repository state.

A command that allows you to modify the most recent commit, adding new changes or updating the commit message.

A command that allows you to modify the most recent commit, changing its message or contents, and update it without creating a new commit.

Scripts that run automatically before or after a commit, allowing you to enforce rules, format code, or perform checks on changes.

Predefined structures for commit messages, helping maintain consistency and include necessary information in commits.

Metadata added to the end of commit messages, often used for things like issue references or sign-offs.

A file format used to store commit graph structure, improving performance for operations that traverse commit history.

A command to check the integrity and validity of the commit-graph file in a Git repository.

A low-level Git command used to create a new commit object from an existing tree object.

A command and system for setting configuration options for Git on a global, local, or repository level.

A diagnostic command that provides statistics about the number and size of objects in a Git repository.

A system that securely stores and retrieves credentials for Git operations, reducing the need for manual authentication.

A lightweight server for the Git protocol, allowing anonymous read access to Git repositories.

Objects in Git that are not reachable from any reference, often created during rebasing or other history-altering operations.

A command that generates a human-readable name for a commit based on the most recent tag and additional commit information.

A command that shows changes between commits, branches, files, or the working directory and the index.

Various methods used by Git to compute differences between versions of files, optimizing for different scenarios.

An external program or interface used to visualize differences between files or commits in a more user-friendly manner.

A command that fetches updates from all remote repositories configured in a Git project.

A powerful tool for rewriting Git history, allowing for large-scale changes across many commits.

A branching model for Git that defines a strict branching structure designed to support multiple parallel developments.

The process of creating a personal copy of someone else's project, allowing for independent development without affecting the original.

A command that verifies the connectivity and validity of objects in the Git database.

Verifies the integrity of objects in the Git database, checking for corruption and inconsistencies.

A security feature in Git that uses GPG to sign and verify commits and tags, ensuring authenticity.

A process that optimizes the Git repository by removing unnecessary files and compressing objects.

Short for Git Garbage Collection, a command to clean up unnecessary files and optimize the repository.

A command for searching files in a Git repository using regular expressions or simple string matching.

A script that Git automatically runs before or after specific events, like commits or merges, to customize workflows and enforce rules.

Same as Git Hook, scripts triggered by various Git actions to automate tasks or enforce policies.

A mechanism to specify intentionally untracked files that Git should ignore, typically defined in a .gitignore file.

The internal format used by Git to store the staging area information, representing the next commit to be made.

A command used to initialize a new Git repository, creating the necessary directory structure for version control.

A feature allowing users to modify commits in their branch history, useful for cleaning up before merging.

The underlying data structures and mechanisms Git uses to store and manage version control information.

A command to parse and manipulate the trailer lines typically found at the end of commit messages.

A system that manages large files by storing them outside the main repository, replacing them with lightweight pointers to improve performance and efficiency.

An extension that replaces large files with text pointers in Git, while storing the file contents on a remote server.

A command to display the commit history of a repository, showing details like author, date, and commit message.

A set of tasks performed to keep a Git repository in good condition, including garbage collection and optimization.

Different algorithms used by Git to combine separate development histories when merging branches.

External programs or interfaces used to resolve merge conflicts in a more visual and user-friendly manner.

A command that finds the best common ancestor between two commits, useful for determining the point where branches diverged.

A feature that improves performance for repositories with many pack files by creating an index across multiple packs.

A feature allowing multiple references (like branches or tags) with the same name to coexist by separating them into different namespaces.

A way to add or inspect object notes, allowing additional information to be attached to Git objects without changing their SHA-1 hash.

The system Git uses to store all the versions of files, commits, and other objects in a content-addressable filesystem.

Compressed files containing Git objects, used to efficiently store and transfer repository data.

The internal format used by Git to store multiple objects efficiently in a single file, reducing disk usage and improving performance.

A feature allowing users to clone a repository without downloading all of its objects, saving bandwidth and storage.

A file format representing changes between versions, used for sharing and applying modifications across different repositories.

Low-level Git commands that expose the internal workings of Git, primarily used for scripting and advanced operations.

User-friendly commands for everyday tasks, like git status and git commit, designed for ease of use and clear output.

The native network protocol used by Git for efficient data transfer between repositories.

A command that removes objects that are no longer reachable from any references in the repository.

Distributed sites hosting cloud services closer to end-users for reduced latency and improved performance.

Machine learning models deployed and executed on edge devices, often with cloud-based training or updates.

Techniques for reducing the size of AI models to run efficiently on resource-constrained edge devices.

Performing text analysis and language understanding tasks on edge devices with cloud support.

Managing and coordinating distributed edge computing resources and their interaction with the cloud.

Using AI on edge devices to forecast equipment failures, with cloud-based model updates and analysis.

Training AI agents on edge devices through interaction with the environment, supported by cloud resources.

Measures to protect data, devices, and applications at the network edge in cloud-connected systems.

Distributed network layer for managing service-to-service communication in edge computing environments.

Data storage systems designed for edge devices with intermittent connectivity to cloud backends.

Applying knowledge from pre-trained cloud models to new tasks on edge devices with limited data.

Creating applications specifically designed to run on edge devices with cloud integration capabilities.

Software development paradigms optimized for creating applications that run on edge devices.

Seamless integration of edge computing resources with centralized cloud infrastructure and services.

Cloud networking component allowing outbound internet communication while blocking inbound traffic.

Fully managed service for deploying and scaling web applications and services on AWS infrastructure.

Static public IP address that can be dynamically assigned to cloud resources, providing consistent access points for applications.

Virtual network interface that can be attached to instances in a VPC, providing flexible networking capabilities.

Virtual network cards that can be attached, detached, and moved between cloud instances.

Integration of analytical capabilities directly into cloud-based applications and workflows.

Cloud-based platforms for analyzing and responding to human emotions in various applications.

Cloud services using AI to detect and respond to user emotions for enhanced interactions.

Protecting data by encoding it both when stored and while moving between cloud systems.

Techniques for securing data both when stored in cloud systems and while being transmitted.

Cloud resource scaling that considers energy consumption alongside performance metrics.

Allocating cloud resources to tasks with consideration for energy consumption and efficiency.

Computing methods designed to minimize energy consumption in cloud environments.

Allocating cloud resources to optimize energy efficiency while meeting performance requirements.

Documenting cloud providers' sustainability and ethical practices for stakeholder transparency.

Open-source edge and service proxy designed for cloud-native applications, providing features like load balancing and observability.

Adherence to principles ensuring fair and responsible use of AI in cloud environments.

Fully managed event routing service for building event-driven applications in Azure.

Storing the state of a system as a sequence of events in cloud-based applications.

Real-time analysis of data streams in cloud environments for immediate insights.

System design where actions are triggered by events in cloud environments, enabling responsive and scalable applications.

Connecting cloud services and applications based on event occurrences, enabling real-time data flow and processing.

APIs that trigger or respond to events in cloud-native applications, enabling real-time data processing and integration.

Developing cloud applications that respond to and generate events, enabling reactive and scalable architectures.

Serverless event bus for building event-driven applications in AWS, facilitating communication between various services.

Data consistency model where all replicas eventually reach a consistent state in distributed cloud systems.

Cloud systems capable of at least one exaFLOPS, or a billion billion calculations per second.

The runtime context in which cloud functions or applications operate, including libraries, dependencies, and configurations.

Monitoring and recording parameters and results of machine learning experiments in cloud environments.

Cloud services for making AI decision-making processes more transparent and interpretable.

Tools for developing AI models with transparent decision-making processes in cloud environments.

Cloud services offering tools to make AI models' decision-making processes more understandable.

Service for creating private connections between Azure datacenters and on-premises infrastructure.

Data integration process where transformation occurs after loading data into the cloud target system.

Process of extracting data from sources, transforming it to fit operational needs, and loading into a target database in the cloud.

Extending cloud capabilities to devices at the extreme edge of the network, like IoT sensors.

Tools for dynamically enabling or disabling features in cloud applications without code deployments.

Centralized repository for storing, managing, and serving machine learning features in cloud environments.

Analyzing data across multiple cloud or edge locations without centralizing the raw data.

System allowing integrated data access across multiple autonomous database management systems in the cloud.

Machine learning technique that trains algorithms across decentralized devices or servers holding local data samples.

Coordinating federated learning processes across multiple edge devices or cloud nodes.

Cloud-based systems for implementing and managing federated learning across distributed datasets.

Applying federated learning techniques to train models on edge devices connected to cloud systems.

Tools for executing queries across multiple distributed databases or data sources in cloud environments.

Cloud service for storing and accessing file data through shared file systems, providing scalable and manageable data storage.

Cloud services providing scalable file storage accessible from multiple compute instances.

Tools and processes for automating financial operations and optimization in cloud environments.

Framework for managing and optimizing cloud costs across an organization, aligning financial and operational goals.

AI-driven tools for continuously optimizing cloud spend and resource allocation.

Security system that monitors and controls incoming and outgoing network traffic in cloud environments.

Open-source, Kubernetes-native serverless framework for building microservices in the cloud, simplifying application deployment.

Extending cloud computing to the edge of the network, bringing processing closer to data sources.

Using historical data and algorithms to predict future trends or values in cloud-based analytics.

Cloud-based encryption allowing computations on encrypted data without decryption.

Tools for building complex serverless applications by combining multiple cloud functions.

Cloud computing model where developers run and manage application functionalities without complex infrastructure.

Adhering to EU data protection regulations in cloud-based data processing and storage.

Cloud compute instances equipped with Graphics Processing Units for parallel processing tasks.

Cloud-based services for creating AI models that can generate new content or data.

Cloud-based systems for analyzing large volumes of location-based data efficiently.

User interfaces that interpret hand or body movements to interact with cloud services.

Methodology using Git repositories as the source of truth for declarative infrastructure and applications in the cloud.

Service that improves availability and performance of applications by optimizing traffic routing across cloud regions.

Database systems that replicate and distribute data across multiple geographic locations in the cloud.

Rules and constraints applied to resources within a Google Cloud organization, enforcing governance and compliance.

Cloud services for analyzing and visualizing complex relationships in large datasets using graph structures.

NoSQL databases designed to store and query data with complex relationships in cloud environments.

Practices and technologies aimed at reducing the environmental impact of cloud data centers and operations.

Practices for developing cloud software that minimizes energy consumption and environmental impact.

Techniques for developing cloud applications that optimize resource usage and reduce environmental impact.

Adhering to US healthcare data protection regulations in cloud-based systems and applications.

Transmitting touch and motion sensations through cloud-connected devices for immersive experiences.

Automated tests to verify the availability and proper functioning of cloud resources and services.

Utilizing excess heat generated by cloud data centers for other purposes, improving energy efficiency.

Packages of pre-configured Kubernetes resources for deploying applications in cloud environments.

Systems managing data across diverse database types and locations in cloud environments.

Using cloud resources for solving complex computational problems requiring significant processing power.

Advanced 3D visualization interfaces for interacting with cloud services and data.

Conceptual cloud data centers using holographic technology for data storage and processing.

Experimental technology using holograms to store data in cloud environments, potentially offering high density.

Experimental data storage technique using holograms in cloud systems for high-density, long-term preservation.

Cloud-based offerings that enable computations on encrypted data without decryption.

Cloud-based service offering encryption that allows computations on encrypted data.

Encryption technique allowing computations on encrypted data without decryption in cloud environments.

Adding more machines to a cloud system to distribute load and increase capacity.

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.