Engineering Glossary

A record in Git's index file representing the state of a file in the repository.

A connection between Git and other tools or services to enhance functionality and workflow.

A short sequence of bytes used to identify a longer public key in Git's GPG signing process.

A secure storage system for passwords and keys, often integrated with Git clients for credential management.

A reserved word in Git commands or configurations with a specific meaning or function.

A way to categorize and organize issues and pull requests in GitHub repositories.

A document in a Git repository specifying how the project can be used, modified, and distributed.

A feature in Git platforms allowing users to comment on specific lines of code in pull requests or commits.

Characters marking the end of a line, which can cause issues in Git when collaborating across different operating systems.

A GitHub account that has been restricted due to a violation of terms of service or suspicious activity.

The default name for the primary branch in many Git repositories, replacing 'master' in recent conventions.

An administrative interface for managing Git hosting services, often used in enterprise environments.

A system of annotation used to format text, often used in Git documentation and comments.

A visual representation of an organization's membership on Git hosting platforms.

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

A way to track progress on groups of issues or pull requests in GitHub projects.

A complete copy of a repository, including all branches and history, often used for backup or as a full replica.

A team within a GitHub organization that is a subset of a larger team, inheriting its permissions.

A visual representation of the commit history and branch structure of a Git repository.

A personalized list of recent activity on Git platforms, showing updates from followed users and repositories.

A Git push that introduces new commits to the remote branch that aren't direct descendants of the current remote HEAD.

An alert system on Git platforms to inform users about relevant activities and mentions.

A fundamental unit in Git's data model, representing content, commits, trees, or tags, identified by a unique SHA-1 hash.

The storage system in Git that contains all versions of project files and metadata, organized by SHA-1 hashes.

A unique SHA-1 hash that identifies a Git object, ensuring data integrity and enabling content-addressable storage.

Another term for the SHA-1 hash that uniquely identifies a Git object in the repository.

The classification of Git objects, including blob (file content), tree (directory structure), commit, and tag.

A Git merge involving more than two branches simultaneously, creating a commit with multiple parents.

A shared account on Git hosting platforms where businesses and open-source projects can collaborate across many projects.

A user with administrative privileges for an organization account on Git hosting platforms.

A branch in Git with no parent commit, typically used to start a new history unrelated to existing branches.

A user granted access to a repository but not a member of the organization that owns the repository.

A Git feature that allows files from one branch to temporarily override files in another branch without merging.

The user or organization with administrative rights to a Git repository, controlling access and settings.

A compressed file format used by Git to store multiple objects efficiently, reducing repository size.

A file that provides fast random access to objects stored within a packfile in Git.

A commit from which another commit is derived, establishing the hierarchical relationship in Git history.

A team in a Git platform that grants its permissions to nested sub-teams within an organization.

Alerts received when you're directly involved in repository activities like being assigned or mentioned.

A pattern used in Git commands to limit the scope of operations to specific files or directories.

The process of recursively dereferencing a Git object to reveal its underlying object type.

A reference specific to a particular working tree in a Git repository with multiple worktrees.

A URL that points to a specific version of a file or directory in a Git repository, ensuring consistent reference.

An individual account on Git platforms, used for personal projects and contributions.

A Git feature for searching the repository history to find when a particular change was introduced.

A featured repository prominently displayed on a user's or organization's profile page on their Git hosting platform of choice.

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

High-level Git commands designed for everyday use, providing a user-friendly interface to common version control tasks.

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

The main email associated with a Git account, used for communications and commit author identification.

Contributions made to private repositories, typically only visible to repository collaborators.

A Git repository with restricted access, visible only to the owner and explicitly granted collaborators.

A Git branch that represents the stable, deployed version of a project, often protected from direct changes.

A user's public page on a Git platform, displaying information about their activity and repositories.

An image representing a user on a Git platform, displayed alongside their contributions and activities.

A kanban-style board in Git platforms for organizing and prioritizing project issues and pull requests.

A branch with rules enforcing certain conditions before changes can be pushed, merged, or deleted.

A Git reference that doesn't follow the standard refs format but is treated similarly, like HEAD or MERGE_HEAD.

Contributions made to public repositories, visible on a user's profile and activity feed.

A Git repository that is openly accessible to anyone, allowing viewing and often cloning without authentication.

Permission level in Git allowing a user to clone a repository and fetch updates, but not push changes.

The process of examining proposed changes in a pull request before they are merged into the main codebase.

A visual representation of a GitHub repository's recent activity, including commits, issues, and pull requests.

A visualization of commit frequency over time, often displayed as a heatmap on Git platforms.

The act of uploading commits from a local branch to a corresponding branch in a remote Git repository.

Permission to upload local changes to a remote Git repository, allowing direct modification of shared branches.

Data structures used to optimize Git operations by quickly determining which objects are reachable from a given commit.

Git objects that can be accessed by following the commit history from a given reference point.

Permission to view and clone a Git repository without the ability to make changes or push commits.

A backup method for accessing a Git account if two-factor authentication is enabled but unavailable.

A name that points to a specific Git object, typically a commit, such as branches or tags.

The collection of references in a Git repository, including branches, tags, and other named pointers to commits.

The address of a remote Git repository, used for fetching and pushing changes between local and remote repositories.

A version of a Git project hosted on a server, serving as a central point for collaboration and backup.

A local reference that represents the state of a corresponding branch in a remote repository.

A copy of a Git repository, often used in distributed systems for redundancy and load balancing.

A local storage of repository data used to improve performance in Git operations.

A visual representation of the commit history and branch structure in a Git repository.

A person responsible for managing a Git repository, reviewing contributions, and maintaining project quality.

A protection rule requiring one or more reviewers to approve changes before merging in Git platforms.

A condition that must be met, such as passing tests, before changes can be merged into a protected branch.

The process of addressing and fixing merge conflicts in Git, typically done manually by the developer.

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

The process of examining proposed changes in a pull request before merging them into the main codebase.

A specific version of a file, directory, or entire repository in Git, often referenced by a commit hash.

The act of moving a branch pointer to an earlier commit in Git, effectively undoing more recent commits.

The top-level directory of a Git repository, containing all project files and the .git subdirectory.

The base filesystem of a Git repository, from which all other directories and files are organized.

A pre-written response that can be quickly inserted into issues or pull request comments on Git platforms.

The range of access or permissions granted to a token or application in Git-based systems.

A licensed user in enterprise Git hosting plans, typically representing a single user account.

A team in a Git organization that is hidden from non-members and other teams within the organization.

A record of security-related events and actions in a system, used for monitoring and auditing purposes.

An authenticated request between Git servers, often used in integrations or automated processes.

A mechanism for Git platforms to send event notifications to external services or applications.

A Git repository with an intentionally truncated history, often created through shallow cloning.

An authentication process allowing users to access multiple Git-related services with one set of credentials.

A Git reference with a specific meaning or function, such as HEAD or FETCH_HEAD.

A deployment environment used for testing changes before releasing to production in Git-based workflows.

A feature on Git hosting platforms allowing users to bookmark repositories of interest.

Policies and processes for ensuring data quality, security, and compliance in cloud environments.

Cloud-based tools for combining data from various sources into a unified view, enabling comprehensive data analysis.

Centralized repository storing structured and unstructured data at scale in its native format.

Large-scale storage repository for raw data in various formats in cloud environments.

Hybrid architecture combining data lake storage with data warehouse query capabilities in cloud environments.

Tracking the origin, movement, and transformations of data throughout its lifecycle in cloud systems.

Monitoring data origins, transformations, and usage across cloud environments for compliance and analysis.

Subset of a data warehouse focused on specific business functions or departments in cloud environments.

Techniques to protect sensitive information by obscuring or replacing identifiable data in cloud storage.

Decentralized approach to data management, treating data as a product owned by domain teams in cloud environments.

Tools supporting implementation of data mesh principles in cloud-based data architectures.

Process of transferring data between storage types, formats, or systems in cloud environments.

Automated process for extracting, transforming, and loading data between cloud systems or services.

Systematic analysis of how data processing activities affect privacy in cloud environments.

Cloud-based tools for assessing, improving, and maintaining the quality of data assets.

Specifying the physical location where cloud-stored data resides for compliance with regulations.

Controls for protecting intellectual property and sensitive information in cloud-based data sharing.

Platforms for sharing and monetizing data science models and algorithms in the cloud.

Tools for tracking changes and collaborating on data science projects in cloud environments.

Techniques for managing uneven data distribution in cloud-based parallel processing.

Concept that data is subject to the laws of the country in which it is stored in cloud environments.

Cloud-based tools for replacing sensitive data with non-sensitive equivalents for security purposes.

Capability to access and restore previous versions of data in cloud storage systems.

Technology that provides a unified view of data from multiple cloud and on-premises sources without moving it.

Tools and techniques for creating visual representations of data stored in cloud environments.

Centralized repository optimized for analytics and business intelligence in cloud environments.

Process of collecting, storing, and managing data from varied sources in a central cloud repository for analysis.

Monitoring and recording database activities in cloud environments for security and compliance purposes.

Process of creating copies of databases and recovering them in cloud environments for data protection.

Technique to store frequently accessed data in memory for faster retrieval in cloud databases.

Process of encoding data to protect sensitive information in cloud-based databases.

Automatic switching to a redundant database when the primary system fails in cloud environments.

Techniques ensuring continuous database operation in cloud environments, minimizing downtime.

Process of moving databases from on-premises or other cloud environments to a target cloud platform.

Managed service for migrating databases to cloud platforms with minimal downtime.

Optimizing database operations for improved speed and efficiency in cloud environments.

Intermediary service managing connections between applications and cloud databases for improved security and performance.

Adjusting database resources vertically (more powerful hardware) or horizontally (more instances) in cloud environments.

Distributing data across multiple database instances for improved performance and scalability in the cloud.

Process of updating database software to newer versions in cloud environments, improving performance and security.

Managed cloud service providing database functionality without the need for infrastructure management.

Storage for messages that can't be processed successfully in cloud-based message queuing systems.

Distributed cloud computing model leveraging blockchain technology for increased security and user control.

Blockchain-based platforms for trading compute resources across distributed cloud networks.

Self-sovereign identity management using blockchain technology in cloud environments.

Systems for user authentication and authorization using blockchain in cloud environments.

Distributed file storage systems using peer-to-peer networks in cloud computing environments.

Security approach using decoys to detect, deceive, and deflect attackers in cloud environments.

Subset of machine learning using neural networks with multiple layers for complex pattern recognition in cloud environments.

Tools and practices for automatically releasing and updating applications in cloud environments.

Service for declaratively managing and deploying cloud resources on Google Cloud Platform.

Automated, end-to-end pipelines for software delivery in cloud environments, streamlining development and deployment processes.

Collaborative approach integrating development and operations teams for efficient cloud-based software delivery.

Measurements for assessing the performance and efficiency of DevOps processes in cloud environments.

Integration of security practices into DevOps processes using automated tools in cloud environments.

Integrated tools for implementing security throughout the DevOps lifecycle in cloud environments.

Tools and practices for configuring, monitoring, and securing IoT devices connected to cloud platforms.

Process of setting up and configuring IoT devices for secure connection to cloud platforms.

Cloud-based tools for adding noise to data to protect individual privacy while maintaining overall accuracy.

Tools for tracking and optimizing user interactions with cloud-based applications and services.

Virtual representations of physical objects or systems, often leveraging cloud resources for simulation and analysis.

Virtual models of physical assets or processes, often using cloud computing for data processing and simulation.

Cloud-based virtual representations of physical entities for monitoring, simulation, and optimization.

Dedicated network connection between on-premises infrastructure and cloud service providers.

Cloud infrastructure designs separating compute, storage, and networking for flexible resource allocation.

Cloud storage architecture separating storage management functions from physical storage devices.

Strategies and tools for recovering data and systems after a catastrophic event in cloud environments.

Process of training machine learning models across multiple cloud nodes for improved speed and efficiency.

Cloud services distributed across multiple physical locations but managed centrally.

Techniques for solving complex problems across multiple cloud nodes while satisfying various constraints.

Cloud-based systems for running data analysis and machine learning tasks across multiple nodes.

Cloud-based security systems deploying decoys across multiple points to detect and mislead attackers.

Process of training AI models across multiple edge devices and cloud resources, enabling decentralized learning at scale.

Technique for tuning machine learning models across multiple cloud nodes for improved performance.

Managing and coordinating blockchain networks across multiple cloud environments.

Tracking and analyzing requests as they flow through cloud-based microservices architectures.

Specialized programming languages designed for efficient cloud resource management and deployment.

Monitoring and identifying unauthorized or unintended changes in cloud infrastructure configurations.

Extension of Azure Functions that enables stateful operations in serverless compute environments.

Adaptive security measures that adjust permissions based on context in cloud environments.

Responsible disposal and recycling of outdated or decommissioned cloud hardware.

Strategies for sustainably disposing of and recycling obsolete cloud computing hardware.

Process of moving data from source systems into a data warehouse in cloud environments.

Approaches to moving to the cloud that minimize environmental impact and energy consumption.

Artificial intelligence algorithms running on devices at the network edge, often integrated with cloud backends.

Methods for reducing the size of AI models to run efficiently on edge devices with cloud support.

Managing and updating AI model versions across distributed edge devices and cloud systems.

Measures to protect AI models and data on edge devices connected to cloud networks.

Artificial intelligence and machine learning capabilities deployed on edge devices, often with cloud integration.

Processing and analyzing data near its source on edge devices before sending insights to the cloud.

Software platforms for developing and deploying analytics applications on edge devices with cloud connectivity.

Identifying unusual patterns or behaviors in data at the network edge before sending alerts to the cloud.

Storing frequently accessed data on edge devices or servers to reduce latency and cloud bandwidth usage.

Network architectures optimized for connecting edge computing devices to cloud resources.

Processing and analyzing visual data on edge devices before sending results to the cloud.

Distributing and caching content on edge servers to reduce latency and cloud bandwidth consumption.

Database systems designed to run on edge devices with intermittent connectivity to cloud backends.

Creating AI-generated content on edge devices with potential cloud-based model updates and synchronization.

Techniques to improve AI model performance on edge devices, reducing latency and cloud dependence.

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

Integration of 5G mobile edge computing with container platforms for low-latency applications and services at network edges.

Application of AI and machine learning for automated operations, monitoring, and management of containerized environments.

Guidelines for phasing out older API versions in Kubernetes, ensuring smooth transitions for users.

Mechanisms to extend the Kubernetes API with custom resources and functionalities, enhancing platform capabilities.

Containerized service that acts as a single entry point for all client requests to a microservices architecture.

Core component of Kubernetes that exposes the cluster's API and handles all administrative operations.

Kubernetes feature allowing the API server to be extended with additional APIs without modifying core Kubernetes code.

Approach prioritizing API design before implementation, crucial for developing scalable containerized microservices.

Serverless compute engine for containers, allowing you to run containers without managing the underlying infrastructure.

Design pattern in containerized microservices that wraps a service's interface to make it compatible with other services.

Plugins that intercept requests to the Kubernetes API server before object persistence, enforcing policies or modifying objects.

Admission controllers specifically focused on enforcing security policies and validating security-related configurations.

HTTP callbacks that receive admission requests and can modify or validate objects before they are persisted.

Use of admission webhooks within Kubernetes operators to enforce custom policies or modify resources.

Kubernetes feature providing detailed logging of all requests processed by the API server for security and compliance.

Extension of the Kubernetes API server to include custom resources and functionalities without modifying core Kubernetes.

Combination of multiple ClusterRoles into a single role, simplifying RBAC management in Kubernetes.

Container registries isolated from public networks, used in secure or restricted environments.

Open-source project for exposing heterogeneous leaf devices as resources in Kubernetes clusters.

Setup and management of Prometheus Alertmanager for handling alerts from monitoring systems.

Fully managed Docker container registry provided by AWS for storing, managing, and deploying container images.

Microservices design pattern where a dedicated service acts as an API gateway for other services.

Service mesh implementation that doesn't require sidecars, reducing resource overhead and simplifying deployment.

Open-source tool for deep inspection of container images, including vulnerability scanning and policy enforcement.

Kubernetes operators implemented using Ansible for automating application lifecycle management.

Network policies specific to the Antrea CNI plugin, offering fine-grained control over pod-to-pod communication.

Kubernetes networking solution using Open vSwitch for improved performance and advanced networking features.

Open-source serverless platform that executes functions in response to events or direct invocations.

Security profiles for Linux that restrict program capabilities, enhancing container isolation and security.

Logging implemented within applications, providing detailed insights into application behavior and performance.

Platform providing security and compliance for container-based and cloud-native applications throughout their lifecycle.

Comprehensive security solution for containerized and cloud-native environments, offering vulnerability management and runtime protection.

GitOps continuous delivery tool for Kubernetes, automating application deployment and lifecycle management.

Kubernetes controller for advanced deployment strategies like canary and blue-green deployments.

Declarative GitOps tool for Kubernetes, automating application deployment and synchronization with Git repositories.

Process of storing, organizing, and managing container images and related artifacts in container registries.

Open-source platform for fine-grained access control and authentication in distributed systems.

Access control paradigm where authorization decisions are based on attributes of users, resources, and environment.

Additional metadata added to Kubernetes audit events for enhanced context and analysis, improving audit trails.

Components responsible for processing and storing Kubernetes audit logs, supporting various storage and analysis options.

Records of requests and activities within a Kubernetes cluster, used for security monitoring and compliance.

Configurable detail levels for Kubernetes audit logs, ranging from metadata-only to full request and response details.

Process of recording API server requests and responses for security, troubleshooting, and compliance purposes.

Detailed records of activities and operations within a Kubernetes cluster, used for security and compliance monitoring.

Configuration defining which events should be recorded in Kubernetes audit logs and at what level of detail.

Predefined set of audit policy rules for common use cases in Kubernetes, simplifying audit configuration.

Different phases of request processing where audit events can be generated in Kubernetes, providing comprehensive auditing.

Setup for sending Kubernetes audit events to external webhook endpoints for processing or analysis.

Process of systematically recording and examining activities within a Kubernetes cluster for security and compliance purposes.

Intermediary service that handles authentication before forwarding requests to the Kubernetes API server.

Pluggable components in container orchestration platforms for verifying user identities using various methods.

Rules defining access permissions for users and services in container orchestration platforms.

Serverless container hosting service in Azure, offering rapid deployment of containers without cluster management.

Managed Docker registry service for storing and managing container images in Azure cloud environments.

Implementation of Border Gateway Protocol within containerized network environments for advanced routing.

In container networks, BGP (Border Gateway Protocol) manages routing information between containers and external networks for efficient traffic routing.

Microservices design pattern where a dedicated service acts as an API gateway for specific frontend needs.

Processes for preserving and recovering container data and configurations in orchestration platforms.

Foundation Docker image upon which other images are built, containing core OS and runtime components.

Process of choosing appropriate foundation images for container builds, balancing size, security, and functionality.

Kubernetes quality of service class for pods with no resource guarantees, scheduled when resources are available.

Deployment strategy using two identical environments to minimize downtime and risk during updates.

Temporary tokens used for secure cluster initialization and node joining in Kubernetes, simplifying cluster setup.

Minimalist Linux-based operating system optimized for running containers in cloud environments.

Advanced container image building toolkit offering improved performance and caching capabilities.

Use of BuildKit for efficient, concurrent, and cache-optimized container image creation, improving build performance.

Isolation technique in microservices to contain failures and prevent system-wide cascading failures.

The Bulkhead Pattern in microservices isolates failures by dividing services into separate compartments, preventing issues in one from affecting others.

Kubernetes quality of service class for pods that can use more resources than requested when available.

Security configuration guidelines for deploying containers securely in various environments.

Technique of using multiple Container Network Interface plugins together for advanced networking capabilities.

Kubernetes feature for fine-grained CPU resource management and allocation to containers, optimizing performance.

Technique to limit CPU usage of containers to prevent resource monopolization and ensure fair allocation.

Architectural pattern separating read and write operations in distributed systems, often used in microservices.

Architectural pattern separating read and write operations in distributed systems, often used in microservices.

Standard interface between container runtimes and Kubernetes, allowing pluggable runtime implementations.

Functionality within CRI for pulling, inspecting, and removing container images, standardizing image operations.

Standardized logging interface for container runtimes implementing the Container Runtime Interface.

Performance and resource usage data exposed by container runtimes adhering to the CRI specification.

Kubernetes feature allowing selection of different runtime configurations for containers, enabling specialized runtimes.

Unix domain socket used for communication between Kubelet and the CRI-compatible container runtime.

Process of verifying that a container runtime correctly implements the CRI specification, ensuring compatibility.

Lightweight container runtime specifically designed for Kubernetes, implementing the CRI specification.

Core components and architecture of the CRI-O container runtime, including its interaction with Kubernetes.

Use of CRI-O, a lightweight container runtime, as the primary runtime in a Kubernetes cluster.

Component of CSI responsible for volume provisioning and attachment operations in container orchestration systems.

Plugins implementing the Container Storage Interface for various storage systems in Kubernetes.

Short-lived volumes in Kubernetes, created and deleted alongside a pod using CSI drivers, for temporary storage.

Process of transitioning from in-tree volume plugins to CSI drivers in Kubernetes, improving storage extensibility.

Component of CSI responsible for mounting volumes and making them available to containers.

Feature allowing storage provisioning based on topology constraints in Kubernetes, optimizing data locality.

Caching strategy where the application checks the cache before retrieving data from the main data store.

Techniques for implementing and managing caches in containerized applications for improved performance.

Open-source networking and network security solution for containers, providing a rich set of security policies.

High-performance networking mode in Calico using extended Berkeley Packet Filter for packet processing.

Technique of releasing new versions to a subset of users or servers to minimize risk and gather feedback.

Fine-grained privileges that can be assigned to containers, enhancing security by limiting root-level access.

Mechanisms for managing and restricting Linux capabilities assigned to containers for improved security.

Groupings or classifications of container-related resources or components for easier management and discovery.

Ceph's block storage system, often used for persistent volumes in container orchestration platforms.