Engineering Glossary

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Capability of different blockchain networks to exchange and use information across cloud platforms.

Cloud-based blockchain infrastructure and management tools offered as a service, simplifying blockchain adoption.

Cloud platforms offering blockchain infrastructure and tools as a managed service for easy deployment and scaling.

Immutable, distributed ledgers recording all actions and changes to cloud resources for enhanced accountability.

Distributed databases using blockchain for data storage and validation in cloud environments.

Use of blockchain technology for secure, decentralized network management and routing in cloud infrastructures.

Immutable records of security events and access logs in cloud systems using blockchain technology.

Use of blockchain technology to enhance security, integrity, and transparency of cloud services and data.

Cloud-hosted blockchain networks for tracking and verifying supply chain transactions and product provenance.

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

Technique using two identical production environments to reduce downtime and risk when deploying new versions of cloud applications.

Internet routing protocol used in cloud networking to exchange routing information between autonomous systems.

Experimental systems allowing direct neural control of cloud resources and services.

Notifications triggered when cloud spending reaches predefined thresholds to help control costs.

Tools and practices for setting, tracking, and controlling cloud service expenditures.

Cloud-based platforms for data analysis and visualization, e.g., Amazon QuickSight, Power BI.

Architectural pattern separating read and write operations in cloud-based applications.

Open-source networking and security solution for containers and Kubernetes in cloud environments.

Technique of rolling out changes to a small subset of users before full deployment in cloud environments.

Tools and methods for estimating the environmental impact of cloud resource usage.

Metric measuring the carbon emissions associated with data center energy consumption in cloud facilities.

Cloud computing practices that consider and optimize for carbon emissions in resource allocation and usage.

Cloud infrastructure and algorithms designed to minimize carbon footprint by optimizing energy use and sourcing.

Cloud resource management that schedules tasks based on availability of low-carbon energy sources.

Consolidation of log data from various cloud services and applications into a single, searchable repository.

Cloud-based systems for designing, running, and analyzing controlled experiments to test system resilience.

Software used to intentionally introduce failures in cloud systems to test and improve their resilience.

Cloud-based platforms for designing and executing controlled experiments to test system resilience.

Frameworks for allocating and billing cloud service costs to different departments or projects within an organization.

Methods for allocating cloud costs to business units, showing actual charges or usage without billing.

Cloud-based platforms for building, deploying, and managing conversational AI agents.

Open-source, eBPF-based networking, observability, and security solution for container and Kubernetes environments.

Design pattern that prevents cascading failures in distributed cloud systems by temporarily disabling failing components.

Practices promoting reuse, refurbishment, and recycling of cloud infrastructure components.

Software that provides a unified interface to multiple cloud providers, simplifying multi-cloud management.

Service that mediates between cloud users and providers, enforcing security policies and monitoring usage.

Structured approach for planning and implementing cloud migration and optimization strategies.

Tools and services for processing and analyzing large datasets using cloud-based resources.

Systems for discovering, classifying, and managing cloud resources across an organization's infrastructure.

Processes and tools for tracking, optimizing, and governing cloud resources throughout their lifecycle.

Intermediary service that helps organizations select, integrate, and manage multiple cloud services.

Technique of extending on-premises infrastructure into the cloud to handle peak workloads.

Content Delivery Network services that distribute data from cloud origins to global edge locations for faster access.

Tools and practices for measuring and reporting the environmental impact of cloud resource consumption.

Cross-functional team responsible for cloud strategy, governance, and best practices within an organization.

Process of adjusting cloud resource settings to improve performance, security, and cost-efficiency.

Automated identification of unusual or unexpected changes in cloud spending patterns.

Strategies and tools for reducing cloud expenses while maintaining performance and meeting business needs.

Open-source tool for managing and enforcing cloud security, compliance, and cost optimization policies.

Scalable, managed Domain Name System service for translating domain names to IP addresses in cloud environments.

Services ensuring data storage and processing comply with regional data residency and privacy laws.

Framework for defining cloud infrastructure using familiar programming languages instead of configuration files.

Practices and tools for managing, optimizing, and reporting on cloud spending and resource utilization.

Serverless compute platform for running event-driven code without managing infrastructure.

Service that streams video games from cloud servers to user devices, reducing hardware requirements.

Set of policies, processes, and tools for managing and controlling cloud resource usage and compliance.

Tools for managing access rights and permissions across multi-cloud environments.

Service providing direct, private network connections between on-premises networks and Google Cloud.

Strategies and tools for managing software licenses in cloud environments to reduce costs and ensure compliance.

Integrated suite of tools for monitoring, managing, and optimizing multi-cloud and hybrid cloud environments.

Evaluation of on-premises IT assets to determine feasibility, strategy, and costs for moving to the cloud.

Tools and services for tracking performance, availability, and health of cloud resources and applications.

Tools for monitoring and optimizing performance of applications built for cloud environments.

Standardized way to transform application source code into container images for cloud deployment.

Continuous integration and delivery practices optimized for cloud-native application development and deployment.

Database systems designed to leverage cloud infrastructure for scalability, resilience, and performance.

Network architectures and technologies optimized for cloud-native application environments.

Practices and tools for monitoring, logging, and tracing cloud-native applications and infrastructure.

Security practices and tools designed specifically for protecting cloud-native applications and infrastructure.

Storage systems designed to integrate seamlessly with cloud-native applications and container orchestrators.

Tools and practices for automating the deployment, configuration, and management of cloud network resources.

Virtualizing network functions like firewalls and load balancers in cloud environments.

AI-driven tools for optimizing and securing cloud network performance and operations.

Services for measuring and comparing performance metrics across different cloud providers and configurations.

Use of cloud computing resources for processing and generating complex graphics or animations.

Process of moving applications or data from public cloud environments back to on-premises or private cloud infrastructure.

Integration of cloud computing with robotics, enabling robots to leverage cloud resources for processing and data storage.

Cloud-based tools for processing and analyzing large datasets generated by robotic systems.

Measures and tools to protect cloud-connected robotic systems from cyber threats and unauthorized access.

Cloud-based platforms for testing and training robotic systems in virtual environments.

Fully managed platform for deploying and scaling containerized applications in a serverless environment.

Comprehensive measures and tools to protect data, applications, and infrastructure in cloud computing environments.

Tools for continuously monitoring and improving security risks in cloud infrastructure configurations.

Centralized repository of available cloud services and resources within an organization.

Tools and practices for analyzing and optimizing cloud expenditures across an organization.

Automated identification of unusual or unexpected patterns in cloud service usage and costs.

Predictive analytics tools for estimating future cloud costs based on historical usage and trends.

Wide Area Network service that connects and manages global network resources using cloud infrastructure.

Managed service for connecting and managing global network resources using cloud infrastructure.

Security solutions designed to protect cloud-native applications and workloads across multiple environments.

Services for storing, versioning, and collaborating on 3D models and assets in the cloud.

Services providing image and video analysis capabilities for cloud-connected robotic systems.

Platforms offering human-powered or AI-assisted data annotation for machine learning models.

Virtual representations of physical objects or systems, powered by cloud computing and IoT data.

OS designed to manage resources across multiple cloud environments as a single system.

Platforms offering pre-trained or customizable generative AI models as cloud services.

Services using cloud computing to generate and deliver tactile sensations for virtual or augmented reality experiences.

Services utilizing cloud resources to process and analyze motion capture data for animation or biomechanics.

Platforms offering scalable environments and resources for training AI agents using reinforcement learning algorithms.

Services enabling robots to learn and improve their capabilities using cloud-based AI and machine learning resources.

External process allowing custom logic to be added to the Kubernetes scheduling decisions.

Methods used by Kubernetes scheduler to determine the best node placement for pods based on various factors.

Kubernetes component allowing plugins to customize the scheduling process without changing the core scheduler code.

Modular components in Kubernetes scheduler implementing specific scheduling behaviors and policies.

Configurations defining sets of scheduling plugins to be used for different scheduling scenarios in Kubernetes.

Use of Berkeley Packet Filter programs to define fine-grained seccomp profiles for container security.

Security profiles defining allowed system calls for containers, enhancing isolation and reducing attack surface.

Kubernetes object for storing and managing sensitive information such as passwords, tokens, or keys.

Process of securely storing, distributing, and rotating sensitive data in containerized environments.

Linux kernel feature limiting the system calls a process can make, often used to secure containers.

Practices ensuring the integrity and security of container images and their dependencies throughout the development lifecycle.

OpenShift object defining a set of conditions that a pod must run with to be accepted into the system.

OpenShift feature for fine-grained control over the actions containers can perform and the resources they can access.

Integration of vulnerability and compliance scans into the continuous integration process for container images.

Tools and platforms for building and deploying serverless applications on container orchestration systems.

Techniques and tools for monitoring, tracing, and debugging serverless functions and applications.

Architectural patterns for designing and implementing serverless applications in containerized environments.

Practices and tools for securing serverless functions and applications in container-based infrastructures.

Orchestration of multiple serverless functions to create complex, event-driven applications.

Kubernetes abstraction defining a logical set of pods and a policy by which to access them.

Kubernetes feature for securely delivering service account tokens to pods, enhancing security.

Credentials automatically generated for pods to authenticate with the Kubernetes API server.

Technique allowing services to locate and communicate with each other dynamically in containerized environments.

Component of a service mesh responsible for managing and configuring the data plane proxies.

Component of a service mesh consisting of proxies that intercept and control service-to-service communication.

Specification defining a set of common APIs for service meshes on Kubernetes, promoting interoperability.

Architectural pattern providing a dedicated infrastructure layer for handling service-to-service communication.

Standard for measuring and characterizing the performance of service mesh deployments, aiding in optimization.

Custom resources in Prometheus Operator for declaratively defining how services should be monitored.

Mechanisms and configurations for enabling network communication between services in container orchestration platforms.

Kubernetes feature allowing services to route traffic based on node topology for improved performance.

Process of verifying the identity of services communicating with each other in a containerized environment.

Kubernetes object providing an identity for processes running in a pod, used for authentication and authorization.

Technique of dividing data across multiple database instances in containerized environments.

Additional containers in a pod that enhance or extend the functionality of the main container.

Design pattern where a sidecar container is deployed alongside the main application container to provide supporting features.

Proxy container deployed alongside application containers to handle network traffic and implement service mesh functionality.

Use of sidecar proxies to implement service mesh features like traffic management and security in Kubernetes.

Open-source application performance monitoring and observability platform for microservices and Kubernetes environments.

Tool facilitating continuous development for Kubernetes applications, handling building, pushing, and deploying application code.

Use of Skaffold to streamline the development workflow for Kubernetes applications in local environments.

Platform providing vulnerability scanning and security management for container images and Kubernetes deployments.

Approach to network management enabling dynamic, programmatically efficient network configuration in container environments.

Tool and workflow for building reproducible container images from source code, simplifying the build process.

Open-source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.

Integration of Splunk's data platform with containerized environments for logging, monitoring, and analysis.

Security platform providing vulnerability management, compliance, and runtime protection for Kubernetes.

Containerized applications that maintain data or state, requiring special considerations for persistence and scaling.

Kubernetes workload API object used to manage stateful applications, providing unique network identities and stable storage.

Design patterns for deploying and managing stateful applications in Kubernetes using StatefulSets.

Pods managed directly by the kubelet on a specific node, without the API server observing them.

Process of pre-creating storage resources in Kubernetes before they are claimed by persistent volume claims.

File-based method for providing authentication tokens to the Kubernetes API server, useful for bootstrap authentication.

Kubernetes API feature allowing updates to an object's status without modifying its spec, enabling more granular updates.

Kubernetes feature for making scheduling decisions based on the available storage capacity of nodes.

Kubernetes objects defining different classes of storage with varying performance characteristics or policies.

Kubernetes object describing the "classes" of storage offered by the administrator, used for dynamic provisioning.

Software-defined storage for cloud-native applications, providing persistent storage for containers.

Incremental approach to modernizing legacy applications by gradually replacing components with microservices.

Network protocols optimized for real-time data transmission in containerized environments.

Kubernetes volume feature allowing mounting a specific directory of a volume instead of its root.

Open-source project enabling direct networking between pods and services across Kubernetes clusters.

Kubernetes API feature representing sub-components of a resource, allowing more granular access control and operations.

Open-source container management system for edge computing, extending Kubernetes to manage edge nodes efficiently.

Security platform providing real-time threat detection and response for containerized environments.

Specification for securing software update systems, applicable to container image distribution.

Kubernetes node attributes that repel certain pods from scheduling unless they have matching tolerations.

Kubernetes mechanism for controlling which pods can be scheduled on specific nodes, enabling node specialization.

Cloud-native CI/CD framework for Kubernetes, providing custom resources for defining pipelines and tasks.

Kubernetes-native CI/CD solution using custom resources to define pipelines as a series of tasks.

Tool allowing developers to run a single service locally while connecting to a remote Kubernetes cluster.

Platform providing vulnerability management and compliance monitoring for container images and registries.

Techniques for separating and securing resources belonging to different users or groups in multi-tenant Kubernetes clusters.

Open-source tool for static code analysis of Infrastructure as Code, including Kubernetes manifests.

Open-source project extending Prometheus for long-term storage and global query view in large-scale deployments.

Use of Thanos to provide durable storage and global query capability for Prometheus metrics.

Technique for limiting the rate at which a containerized service processes requests to prevent overload.

Development environment as code for teams building Kubernetes microservices, streamlining local development.

Settings controlling the maximum duration for various operations in containerized applications and infrastructure.

Kubernetes pod specifications that allow (but do not require) pods to be scheduled on nodes with matching taints.

Kubernetes feature coordinating resource allocation decisions to provide topology-aligned resource allocations.

Technique of duplicating live traffic to a separate service instance for testing or debugging purposes.

Gradual redirection of traffic from one version of a service to another, often used in canary deployments.

Distribution of incoming requests across multiple versions of a service, enabling advanced deployment strategies.

Open-source security scanner for containers and other artifacts, finding vulnerabilities and misconfigurations.

Set of best practices for building software-as-a-service apps that can be easily deployed to the cloud.

Container security platform providing vulnerability management, compliance, and runtime protection (now part of Prisma Cloud).

Comprehensive cloud-native security platform for containers, serverless, and cloud environments.

Physical network infrastructure upon which overlay networks for container communication are built.

Specialized, single-purpose machine images offering potential advantages in size and security over containers.

Filesystem service for Linux allowing files and directories of separate filesystems to be overlaid, forming a single coherent filesystem.

Kubernetes feature allowing a user to act as another user, useful for debugging and testing access controls.

Linux kernel feature providing per-process isolated instances of user and group ID number spaces.

Network virtualization technology used in container networking for creating overlay networks.

Virtual networks using VXLAN encapsulation to enable container communication across hosts.

Design pattern for providing clients with restricted direct access to a specific resource or service.

Admission controller webhooks in Kubernetes that validate resource requests without modifying them.

Kubernetes admission control mechanism for validating API requests against custom logic before persistence.

Open-source tool for backing up and restoring Kubernetes cluster resources and persistent volumes.

Guidelines defining supported version differences between Kubernetes components to ensure compatibility.