Engineering Glossary

A variation of Git pull that fetches remote changes and rebases local commits on top of them instead of merging.

A safer alternative to force push, which only updates the branch if it hasn't been modified since your last fetch.

A command that compares the changes between two commit ranges, useful for reviewing rebased branches.

A low-level command that reads tree objects into the index, used in complex merging scenarios.

A log of all reference updates in a repository, useful for recovering lost commits or branches.

Same as Git Reflog, logs that record when the tips of branches and other references were updated in the repository.

The system Git uses to store references (like branches and tags) as files in the .git directory.

A string that specifies the mapping between remote and local references when fetching or pushing.

Adds a new remote repository to your local Git configuration, associating a name with a URL.

A command that removes remote-tracking branches that no longer exist on the remote repository.

Removes a remote repository from your local Git configuration, deleting its associated references.

A feature allowing one Git object to be transparently used in place of another, useful for history rewriting.

A feature that remembers how you resolved merge conflicts and automatically reapplies the resolution.

A command used to undo changes by moving the current branch head to a specific commit.

A Git reset option that updates the working directory and staging area to match the specified commit.

A Git reset option that moves the HEAD to a specified commit without changing the working directory or staging area.

A command that lists commit objects in reverse chronological order, often used as a basis for other commands.

A command used to parse Git revision syntax and return the corresponding object name.

A command that creates a new commit that undoes the changes made by a previous commit.

A command to remove files from both the working directory and the Git repository.

A clone that only fetches a limited number of commits, reducing download size and time for large repositories.

A command that summarizes git log output, typically used to create release announcements.

Commits that are cryptographically signed to verify the identity of the committer and ensure integrity.

Tags that are cryptographically signed to verify the identity of the tagger and ensure the tag's integrity.

The process of combining multiple commits into a single commit, often used to simplify history before merging.

A command that applies a stored stash to the working directory without removing it from the stash list.

A command that applies a stored stash to the working directory and removes it from the stash list.

A command that displays the state of the working directory and the staging area.

A repository embedded within another repository, allowing you to keep a Git repository as a subdirectory of another Git repository.

A command that executes a specified shell command for each initialized submodule in a Git repository.

A feature for managing nested repositories as subdirectories of a parent repository, an alternative to submodules.

A low-level Git command that manipulates the staging area, updating file information and preparing changes for commit.

The communication protocol used between Git clients and servers for efficient data transfer.

A feature allowing multiple working trees to be attached to the same repository, useful for working on different branches simultaneously.

Creates a new working tree associated with the repository, allowing work on multiple branches simultaneously.

A command to list details of each working tree associated with the repository, showing paths and branch information.

A low-level Git command that creates a tree object from the current index, representing a directory structure.

A Git command used to create an archive (zip or tar) of files from a specified commit, useful for creating release packages.

Agreed-upon patterns for naming branches to improve organization and clarity in collaborative projects.

A command to examine the contents and type of Git objects, useful for inspecting repository internals.

A command to resume the cherry-pick process after resolving conflicts in a paused cherry-pick operation.

Levels at which Git configuration can be set: system (all users), global (user), and local (repository).

A command providing detailed statistics about the number and size of objects in a Git repository.

Mechanisms to securely store and retrieve credentials for Git operations, reducing manual authentication.

Custom scripts that determine how Git should generate diffs for specific file types.

A versatile tool for rewriting Git repository history, offering more power and flexibility than git filter-branch.

A more thorough garbage collection process in Git, optimizing repository storage and performance.

A low-level Git command that computes the object ID (SHA-1 hash) for a given file or string, used in Git's internal storage.

Scripts triggered by specific events in Git workflows, used to automate tasks or enforce policies.

The intermediate area in Git where changes are prepared before committing, also known as the staging area.

Individual, uncompressed Git objects stored separately in the object database before being packed.

A command to list the contents of a tree object in Git, showing files and subdirectories.

Custom scripts defining how Git should handle merges for specific file types or patterns.

A low-level Git command that creates a tree object from a specific index or tree listing.

The four fundamental object types used by Git to store repository data and history.

A command to pack references into a single file for improved performance in repositories with many references.

Compressed files containing multiple Git objects, optimizing storage and transfer efficiency in repositories.

Server-side scripts that run after commits have been accepted, often used for notifications or deployments.

Server-side scripts that run before pushed commits are accepted, used to enforce policies or checks.

An improved version of the Git transfer protocol, offering better performance and feature negotiation.

A command to move a series of commits to a new base commit, useful for changing the parent of a branch.

A command to remove old entries from the reflog, useful for cleaning up Git history and freeing space.

A command to combine all loose objects in a repository into packfiles, improving storage efficiency.

Commands to undo changes in Git, with varying impacts on the working directory and staging area.

Techniques and tools for securely storing and accessing sensitive information in Git repositories.

A command that lists references in a Git repository along with their associated commit hashes.

A feature allowing users to check out only a subset of files from a repository, saving space and time.

A command to validate the contents of Git pack files, ensuring data integrity in the object database.

An application that can be installed directly on organizations and user accounts to extend GitHub's functionality.

A version of Markdown with additional features specifically supported on GitHub.

A tool for importing repositories to GitHub from other version control systems or source code hosts.

A feature in GitHub for tracking tasks, enhancements, and bugs for a project.

A platform for posting and finding software development jobs, integrated with GitHub profiles, that was discontinued in 2021.

A platform for developers to sell and buy integrations for GitHub, enhancing workflow and productivity.

A static site hosting service that takes files directly from a GitHub repository to publish websites.

A collaborative documentation feature in GitHub repositories, allowing easy creation and editing of project documentation.

A lightweight, branch-based workflow that supports teams and projects where deployments are made regularly.

A version control workflow that combines feature-driven development and feature branches with issue tracking.

Branching model for Git that defines a strict branching model designed around project releases.

A graphical interface for viewing Git repositories, providing a visual representation of commit history.

Query language for APIs and a runtime for executing those queries with existing data.

A pointer in Git that refers to the latest commit in the current checked-out branch.

A simple program often used as an introduction to a new programming language or environment, including Git tutorials.

A method for quickly patching production releases by branching directly from the main branch or a tag.

Also known as the staging area, where changes are prepared before committing in Git.

Predefined structures for creating new issues in Git repositories, ensuring consistent and complete information.

A static site generator often used with GitHub Pages to create websites from Markdown files in a Git repository.

A tool in GitHub Pages that allows users to easily select and apply pre-designed themes to their Jekyll sites.

Git Large File Storage, an extension for versioning large files in Git repositories.

A library used by GitHub to detect the programming languages used in repositories.

A lightweight markup language commonly used for documentation in Git repositories.

Formerly the default name for the primary branch in Git repositories, now often replaced by 'main'.

The process of combining changes from different branches into a single branch, integrating multiple lines of development.

An application that uses the OAuth protocol to access Git platform APIs on behalf of users.

A secure string used for authentication in Git operations, allowing access to resources without sharing passwords.

The default name for the remote repository from which a local repository was cloned.

A file describing changes between versions, used to share and apply modifications across different Git repositories.

A Git command that fetches changes from a remote repository and merges them into the current branch.

A method of submitting contributions to a Git project, proposing changes from a forked repository or branch.

Customizable files that automatically populate the body of new pull requests, guiding contributors.

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.

Custom, cluster-level resources in Kubernetes that can be allocated to containers, such as GPUs or FPGAs.

Kubernetes component allowing custom logic to be added to the scheduling process for advanced pod placement strategies.

HTTP callbacks that receive admission requests and can modify or reject objects before persistence in Kubernetes.

Incorporation of external secret management systems like HashiCorp Vault with container platforms.

Kubernetes service type that maps a service to a DNS name, useful for representing external services within a cluster.

Kubernetes services that reference external resources by DNS name, facilitating access to external dependencies.

Allocation and management of Field-Programmable Gate Arrays as resources in container orchestration platforms.

Implementation of Function-as-a-Service platforms on Kubernetes, enabling serverless architectures in container environments.

Open-source cloud-native runtime security project, providing real-time threat detection for containerized environments.

Use of Falco to monitor and alert on unexpected behavior in running containers and Kubernetes clusters.

Technique of intentionally introducing failures in containerized systems to test resilience and error handling capabilities.

Flags in Kubernetes used to enable or disable specific features, allowing for fine-grained control over cluster functionality.

Implementation of service mesh across multiple Kubernetes clusters, enabling cross-cluster service communication.

Technique for managing multiple Kubernetes clusters from a single control plane, useful for multi-cloud or hybrid deployments.

Kubernetes feature allowing controllers to implement asynchronous pre-delete hooks, ensuring proper resource cleanup.

Use of finalizers in Kubernetes operators to perform cleanup operations before custom resource deletion.

Lightweight virtualization technology used for creating and managing secure, multi-tenant container environments.

Minimal virtual machines used by Firecracker to provide strong isolation for containers or functions.

Open-source, Kubernetes-native serverless framework for running functions, supporting multiple languages and event triggers.

Progressive delivery tool for Kubernetes, automating canary releases and A/B testing of containerized applications.

Network fabric for containers designed to give a consistent, easily configured layer 3 network across multiple hosts for Kubernetes.

CNI plugin providing a simple overlay network for container communication across hosts, enabling basic networking.

Out-of-tree plugin mechanism in Kubernetes for interfacing with third-party storage systems, predating CSI.

Open-source data collector for unified logging layer, enabling efficient data collection and consumption for better use of data.

Kubernetes deployment ensuring Fluentd log collectors run on every node for comprehensive log aggregation.

Modular components in Fluentd for ingesting logs from various sources in containerized environments.

Modular components in Fluentd for sending processed logs to various destinations from containerized environments.

GitOps toolkit for deploying applications to Kubernetes, automating the deployment pipeline from Git repositories.

Next generation of Flux, providing a set of continuous delivery solutions for Kubernetes with improved modularity and features.

Automatic adjustment of function instances based on demand in serverless container environments.

Standardized way of building function containers, abstracting away infrastructure concerns for developers.

Process of allocating and managing GPU resources for containers running machine learning workloads.

Tool facilitating development and testing of Kubernetes applications in remote clusters.

Kubernetes feature allowing for dynamic provisioning of short-lived volumes for containers.

Network virtualization technology used in some container networking solutions for multi-tenant environments.

Integrated CI/CD platform with native container and Kubernetes support for building, testing, and deploying applications.

Set of composable APIs and specialized tools for building continuous delivery systems on top of Kubernetes.

Operational model where the desired state of a Kubernetes cluster is version controlled and automated from a Git repository.

Distributed file system that can be used for providing persistent storage to containerized applications in Kubernetes.

Kubernetes operators written in Go, leveraging the client-go library for interacting with the Kubernetes API.

Tool that provides recommendations for resource requests and limits for Kubernetes deployments.

Managed compute platform for deploying containerized applications in a serverless environment.

Managed Docker registry service by Google for storing, managing, and securing container images.

Customizable visualization panels for monitoring containerized environments and applications.

Configurable backends in Grafana for retrieving metrics and logs from various container monitoring systems.

Horizontally-scalable, multi-tenant log aggregation system designed for use in containerized environments.

Automated setup and configuration of Grafana dashboards and data sources in container deployments.

Implementation of GraphQL APIs in microservices architectures for flexible data querying and manipulation.

Kubernetes Quality of Service class ensuring pods receive the exact amount of requested resources, ideal for critical workloads.

Open-source container registry providing content trust, vulnerability scanning, and RBAC for storing and distributing container images.

Continuous Delivery platform supporting various deployment strategies for containerized applications in Kubernetes environments.

Kubernetes services that don't allocate a cluster IP, used for direct pod-to-pod communication in stateful applications.

Package manager for Kubernetes that helps you define, install, and upgrade even the most complex Kubernetes applications.

Packages of pre-configured Kubernetes resources, facilitating the deployment and management of complex applications.

Helm feature allowing custom actions to be performed at specific points in a release's lifecycle, enhancing deployment flexibility.

Kubernetes operator that manages Helm releases, automating the deployment and lifecycle of Helm-based applications.

Storage locations for packaged Helm charts, enabling version control and distribution of containerized application configurations.

Mechanism in Helm for parameterizing chart templates, allowing for customization of deployments across different environments.

Kubernetes operators leveraging Helm charts for managing the lifecycle of complex, stateful applications.

Kubernetes feature allowing nested namespaces, providing finer-grained resource isolation and multi-tenancy capabilities.

Kubernetes controller that automatically adjusts the number of pods in a deployment based on observed metrics.

Metrics used by HPA to determine when to scale containerized applications, including CPU, memory, and custom metrics.

Extended HPA functionality allowing scaling decisions based on application-specific or external metrics.

Kubernetes resource defining the behavior for automatically scaling the number of pods in a replication controller or deployment.

Container networking mode where pods use the host's network namespace, bypassing virtual networks for improved performance.

Linux kernel feature for managing large memory pages, improving performance for memory-intensive containerized applications.

IP Virtual Server, a transport-layer load balancing technology used in Kubernetes for efficient service proxying and load distribution.

Implementation of IPsec protocols to secure container-to-container communications across hosts and clusters.

Kubernetes feature enabling pods and services to be assigned both IPv4 and IPv6 addresses, facilitating transition to IPv6.

Support and configuration for using IPv6 addressing in Kubernetes clusters, enabling large-scale container deployments.

Approach to designing APIs that can be called multiple times without changing the result, crucial for reliable microservices.

Lightweight, standalone, executable package that includes everything needed to run a piece of software.

Unique identifiers for container images, ensuring consistency and integrity across different environments and registries.

OCI specification for multi-architecture container images, allowing a single image to support multiple platforms.

Technique for reusing unchanged layers when building or pulling container images, improving build and deployment speed.

Strategies for reducing the size and number of layers in container images, improving storage efficiency and pull times.

Metadata file describing the contents and configuration of a container image, crucial for image distribution and deployment.

Standardized format for container image manifests, supporting multi-architecture images and content-addressable layers.

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

Process of downloading container images from a registry to a local environment or container runtime.

Process of uploading locally built container images to a remote registry for distribution and deployment.

Rules defining how long container images are kept in a registry, balancing storage costs with availability needs.

Automated process of analyzing container images for vulnerabilities, misconfigurations, and compliance issues.

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

End-to-end process of cryptographically signing container images and verifying their authenticity before deployment.

Technique of combining multiple layers of a container image into a single layer, potentially reducing image size and complexity.

Process of assigning human-readable labels to container images, facilitating version management and deployment workflows.

Automated security analysis of container images to identify known vulnerabilities in installed packages and dependencies.

Component in container runtimes responsible for managing image-related operations like pulling, pushing, and local storage.

Practice of replacing entire container instances instead of modifying existing ones, enhancing consistency and reliability.

Approach to deploying containerized applications by directly specifying the desired actions, as opposed to declarative methods.

Distributed data management systems optimized for high-performance data processing in containerized environments.

Technique for updating containerized applications or infrastructure components without full redeployment, minimizing downtime.

Built-in plugins in Kubernetes for various functionalities, as opposed to out-of-tree or external plugins.

Technique for optimizing container image distribution by allowing partial and on-demand loading of image layers.

Automated testing of infrastructure definitions, ensuring consistency and reliability in container deployments.

Kubernetes API object managing external access to services in a cluster, typically HTTP, providing load balancing and SSL termination.

Components implementing the Ingress resource in Kubernetes, managing the routing of external traffic to internal services.

Entry point for external traffic in service mesh architectures, providing routing, security, and observability for incoming requests.

Design pattern using specialized containers that run before app containers in a pod, used for setup or dependency management.