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.

System for collecting, processing, and storing performance metrics from containerized applications and infrastructure.

Kubernetes add-on that collects resource metrics from kubelets for use in autoscaling and monitoring.

Techniques for improving the performance and efficiency of the Kubernetes Metrics Server for better monitoring.

Lightweight, CNCF-certified Kubernetes distribution designed for developer workstations, IoT devices, and CI/CD.

Reusable base structure for building microservices, providing common functionalities like logging and monitoring.

High-performance, S3-compatible object storage system, often used for persistent storage in container environments.

Feature allowing containers to share mounted volumes, enabling advanced storage scenarios in Kubernetes.

Design patterns for deploying multiple containers within a single pod, such as sidecar, ambassador, or adapter patterns.

Container images supporting multiple CPU architectures, enabling deployment flexibility across diverse hardware.

Tools and practices for administering and orchestrating multiple Kubernetes clusters as a unified system.

Technologies and configurations enabling network connectivity and service discovery across multiple Kubernetes clusters.

Coordinated management and deployment of containerized applications across multiple Kubernetes clusters.

Mechanisms for locating and accessing services deployed across multiple Kubernetes clusters.

Implementation of service mesh functionalities spanning multiple Kubernetes clusters for unified traffic management.

Dockerfile technique using multiple stages to create optimized, smaller container images by separating build and runtime environments.

Performance and isolation tests for evaluating the effectiveness of multi-tenant Kubernetes cluster configurations.

CNI plugin enabling attachment of multiple network interfaces to pods in Kubernetes, supporting advanced networking scenarios.

Container Network Interface plugin allowing multiple CNI plugins to be used simultaneously, enabling multi-network support for pods.

Use of Multus to attach pods to multiple networks, enabling complex networking scenarios in Kubernetes.

Admission controller webhooks that can modify resource requests before they are persisted, enabling dynamic resource manipulation.

Security protocol ensuring both client and server authenticate each other, commonly used in service mesh implementations.

Observability platform offering performance monitoring and analytics for containerized applications and infrastructure.

Cloud-native approach to solving L2/L3 use cases and service chain provisioning in Kubernetes.

Kubernetes feature considering Non-Uniform Memory Access topology for optimal pod placement.

Kubernetes abstraction for creating multiple virtual clusters within a physical cluster, providing a scope for names and resources.

Kubernetes feature for partitioning clusters into virtual sub-clusters, enabling resource isolation and access control.

Process of modifying network address information in packet headers for routing in container networks.

Concept of replacing dedicated network appliances with virtualized functions, often containerized.

Security technique dividing networks into isolated zones, enhancing container and microservices security.

Kubernetes resources specifying how groups of pods are allowed to communicate with each other and other network endpoints.

Specification of how groups of pods are allowed to communicate with each other and other network endpoints.

Feature enabling logging of allowed and denied network connections based on Kubernetes Network Policies.

Practice of dividing a network into smaller segments or subnets, improving security and performance in container environments.

Cloud-native solution providing layer 2/3 network services to Kubernetes workloads, enhancing networking capabilities.

Kubernetes resource defining rules for pod-to-pod and pod-to-external communication, implementing network segmentation.

Security platform providing real-time container firewall, vulnerability management, and compliance for Kubernetes.

Observability platform offering performance monitoring and analytics for containerized applications and infrastructure.

Basic unit of a distributed application in many systems, often referring to individual machines or processes.

Kubernetes feature allowing pods to be scheduled on nodes with specific characteristics based on labels.

Kubernetes authorization mode controlling kubelet access to the API server, enhancing cluster security.

Feature automatically adjusting the number of nodes in a Kubernetes cluster based on workload demands.

Prometheus exporter for hardware and OS metrics exposed by *NIX kernels, used for node-level monitoring in Kubernetes.

Kubernetes add-on detecting hardware features and system configuration, facilitating hardware-aware scheduling.

Unique identifier for a node in a Kubernetes cluster, used in various operations and configurations.

Process of removing pods from a node when it experiences resource pressure, ensuring stability.

Kubernetes add-on monitoring and reporting node health issues, enhancing cluster reliability.

Kubernetes plugin limiting node and pod modifications to increase security and prevent privilege escalation.

Kubernetes feature for constraining pods to nodes with specific labels, enabling basic scheduling control.

Procedure for updating the software stack on Kubernetes nodes while minimizing disruption to running workloads.

Capture and management of system and container logs at the node level in a Kubernetes cluster.

Kubernetes controller managing the lifecycle of nodes, handling node registration and decommissioning.

Kubernetes add-on running a dns caching agent on cluster nodes to improve DNS performance.

Kubernetes service type exposing the service on each node's IP at a static port, enabling external access.

Kubernetes services that expose applications on a static port on each node, facilitating external access.

Security practice of running containers with non-privileged users to reduce potential attack surface.

Network communication between external clients and services within a Kubernetes cluster, typically through ingress.

Open-source project providing secure content distribution and verification for container registries.

Implementation of Notary to ensure the integrity and authenticity of container images, enhancing supply chain security.

Open Container Initiative specification defining an API protocol for distributing container images.

Open Container Initiative specification defining the format of container images, ensuring interoperability.

Detailed standard for container image format, ensuring interoperability between different container technologies.

Standard defining the configuration, execution environment, and lifecycle of containers, ensuring compatibility.

Linux kernel mechanism for terminating processes when the system runs out of memory, affecting container reliability.

Integration of Open Virtual Network with Kubernetes for advanced software-defined networking.

Open-source developer-centric web interface for visualizing Kubernetes cluster state and workloads.

Industry standard for container runtime implementations, ensuring compatibility across platforms.

General-purpose policy engine for cloud-native environments, often used for Kubernetes admission control.

OPA-based system for declaring, managing, and enforcing policies in Kubernetes environments.

Container-attached storage solution providing persistent storage for stateful workloads in Kubernetes.

OpenEBS feature for provisioning local persistent volumes, optimizing performance for I/O intensive workloads.

Framework for building serverless functions with Docker and Kubernetes, simplifying the deployment of event-driven workloads.

JSON Web Tokens used for authentication in Kubernetes, often integrated with external identity providers.

Vendor-agnostic way to receive, process, and export telemetry data in various formats for observability.

Vendor-neutral API for distributed tracing, facilitating the instrumentation of microservices for observability.

Kubernetes extension designed for edge computing scenarios, enabling efficient management of edge nodes.

Kubernetes extension that oversees installation, upgrades, and management of Operators in a cluster.

Feature for usage reporting and billing in Kubernetes clusters, often used with Operators.

Performance and health indicators exposed by Kubernetes Operators for monitoring and alerting.

Kubernetes extension pattern for automating application-specific operational knowledge and tasks.

Framework for building Kubernetes Operators, simplifying the development process with high-level APIs.

Tool for validating Operators against best practices and providing suggestions for improvements.

Public registry for finding and sharing Kubernetes Operators, facilitating discovery and distribution.

Kubernetes plugins developed and maintained outside the main Kubernetes repository, enabling extensibility.

Design pattern ensuring consistency between database and message broker in distributed systems.

Process of identifying abnormal behavior in containerized applications or infrastructure for troubleshooting.

Additional resource consumption introduced by container runtimes and orchestration systems.

Layered filesystem used by container runtimes to efficiently manage image layers and container writes.

Virtual networks created on top of existing networks, enabling container-to-container communication across hosts.

Base container image upon which other images are built, providing foundational layers for child images.

Service mesh feature ensuring mutual authentication between services using mTLS, enhancing security.

Kubernetes resource representing a request for storage by a user, abstracting storage implementation details.

Kubernetes abstraction for a piece of storage in the cluster, managed independently of individual pods.

Kubernetes resource representing a piece of storage in the cluster that has been provisioned by an administrator.

Kubernetes resource representing a request for storage by a user, abstracting the details of the underlying storage implementation.

Practice of defining CI/CD pipelines using code, often stored alongside application code for version control and review.

Open-source observability tool for Kubernetes, providing automatic data collection and real-time debugging capabilities.

Use of Pixie to gain deep insights into Kubernetes cluster performance and application behavior without code changes.

Smallest deployable unit in Kubernetes, consisting of one or more containers sharing storage and network resources.

Kubernetes scheduling constraint that allows pods to be co-located with other pods based on labels.

Kubernetes features for influencing pod scheduling based on the topology of the cluster and other pods.