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 comparison of two Git commands used to undo changes, with revert creating new commits and reset modifying history.

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 comparison of two Git features used to include external repositories in a project, each with different use cases.

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.

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.

Design pattern using DaemonSets to run system daemons or agents on every node in a cluster.

Processes and tools for preserving and restoring data in containerized environments, ensuring data durability.

Techniques ensuring data integrity across distributed container-based applications, maintaining reliability.

Distributed data management architecture providing consistent data access across containerized applications.

Unified data architecture combining data lake and data warehouse features in containerized environments.

Process of moving data between containers or from traditional systems to containerized applications.

Techniques for maintaining data across container lifecycles, including volume mounts and persistent volumes.

Network layer responsible for forwarding container traffic based on control plane decisions.

Techniques for creating and maintaining copies of data across multiple containerized instances.

Partitioning data across multiple database containers for improved scalability and performance.

Process of running database systems within containers for improved portability and resource utilization.

Microservices design pattern where each service has its own dedicated database, ensuring data isolation.

Platform for observability and monitoring of containerized environments and microservices.

Design pattern for handling failed message processing in containerized message-driven systems.

Approach to deploying containers by specifying desired state rather than imperative commands.

Techniques for rolling out container updates, including rolling updates, blue-green, and canary deployments.

Kubernetes component that evicts pods from nodes based on specific policies to optimize cluster resource usage.

Standardized format defining the structure and metadata of Docker container images, ensuring portability.

Kubernetes feature allowing nodes to advertise system hardware resources to the cluster, enabling specialized hardware use.

Network optimization technique in container load balancing for improved performance by bypassing the load balancer for responses.

Implementation of tracing in containerized microservices for end-to-end request visibility.

Implementation of distributed tracing using Jaeger to monitor and optimize performance in microservices architectures.

Implementation of OpenTelemetry for standardized observability in containerized environments.

Minimal container images containing only the application and its runtime dependencies, reducing attack surface.

Command to attach local standard input, output, and error streams to a running container for interaction and debugging.

Set of files located in the specified PATH or URL, used during the docker build process to create images.

Docker CLI plugin for extended build capabilities, including multi-platform builds and enhanced build options.

Component enabling Docker to be used as a container runtime in Kubernetes via the Container Runtime Interface.

Command-line tool for interacting with Docker daemon and managing containers, images, and other Docker objects.

Command creating a new image from a container's changes, useful for saving modifications made to a running container.

Tool for defining and running multi-container Docker applications, simplifying the process of managing complex application stacks.

Process of viewing detailed information about a container's configuration and state, aiding in troubleshooting.

Feature providing digital signing and verification of Docker images, ensuring image authenticity and integrity.

Process of validating the authenticity and integrity of signed Docker images before use.

Feature allowing management of multiple Docker endpoints from a single Docker client, simplifying multi-environment management.

Background service managing Docker objects like images, containers, networks, and volumes.

Command allowing users to run a new process inside a running container, useful for debugging and maintenance tasks.

Commands for exporting a container's filesystem as a tarball and importing it as an image.

Cloud-based repository service for finding and sharing container images, central to the Docker ecosystem.

Command showing the history of an image's layers, providing insight into how the image was built and modified.

Process of examining Docker image metadata, including layers, environment variables, and exposed ports.

Standardized format defining the structure and metadata of Docker container images, ensuring portability.

Virtualized network providing connectivity between Docker containers, isolating container traffic from the host network.

Different networking modes in Docker, including bridge, host, overlay, and macvlan, offering varied connectivity options.

Command for removing unused Docker objects like containers, networks, images, and volumes.

Commands for exporting Docker images to tar archives and importing them back, useful for image transfer and backup.

Command-line tool for scanning Docker images for vulnerabilities, providing detailed reports on potential security issues.

Deprecated component that provided CRI compatibility for Docker in Kubernetes, bridging Docker and CRI.

Unix socket or named pipe used for communication between Docker client and daemon, enabling Docker API access.

Command displaying a live stream of container resource usage statistics, including CPU, memory, and network I/O.

Native clustering and orchestration solution for Docker, allowing you to create and manage a swarm of Docker nodes as a single virtual system.

Real-time stream of Docker daemon events, providing insights into container, image, volume, and network activities.

Command displaying the running processes of a container, similar to the Unix top command but container-specific.

Persistent data storage mechanism for containers, independent of container lifecycle, enabling data persistence.

Different storage backends for Docker volumes, including local, NFS, and cloud-specific drivers.

Text document containing all the commands a user could call on the command line to assemble a Docker image.

Instruction defining build-time variables that users can pass at build-time to the builder.

Guidelines for creating efficient, secure, and maintainable Dockerfiles, optimizing image builds and runtime performance.

Instruction telling Docker how to test a container to check its health status, improving reliability.

Set of commands used in Dockerfiles to build images, including ADD, COPY, RUN, CMD, and ENTRYPOINT.

Set of commands used in Dockerfiles to build images, including ADD, COPY, RUN, CMD, and ENTRYPOINT.

Instruction setting the system call signal that will be sent to the container to exit, customizing shutdown behavior.

File specifying which files and directories should be excluded when building a Docker image.

Approach to software design focusing on the core domain in containerized microservices architectures.

P2P-based image and file distribution system to improve efficiency of image downloads in container environments.

Process of cordoning a node and evicting its pods in preparation for maintenance or decommissioning.

Networking configuration supporting both IPv4 and IPv6 in container environments, enabling broader connectivity options.

Kubernetes feature allowing custom logic to be applied to object creation or modification requests.

Kubernetes feature enabling runtime configuration of audit policies without API server restart.

Automatic creation of storage when persistent volume claims are made in Kubernetes, simplifying storage management.

Monitoring solution for containerized environments, providing deep visibility into application performance.

Combination of Elasticsearch, Logstash, and Kibana for logging and monitoring containerized environments.

Network communication between containers or services within the same cluster or data center.

Deployment of artificial intelligence and machine learning models on edge devices using containers.

Processing and analyzing data at the network edge using containerized analytics applications.

Tools and practices for managing containerized workloads on edge devices, ensuring consistent deployment and updates.

Management and coordination of containerized applications across distributed edge locations.

Security measures and practices specific to containerized edge computing environments, protecting distributed workloads.

Techniques for efficiently distributing containerized workloads across edge devices, optimizing resource usage.

Synchronization of data and state between edge containers and cloud-based systems, ensuring consistency.

Component controlling outbound traffic from a container cluster to external services, enhancing security and traffic management.

Service mesh components managing outbound traffic from the mesh to external services, providing fine-grained control.

Management and policies for outbound network traffic from containers, ensuring security and compliance.

Application Performance Monitoring tool for containerized applications in the Elastic Stack.

Sensitive data stored in an encrypted form in container orchestration platforms, enhancing security.

Comprehensive testing of containerized applications from start to finish, validating entire system functionality.

Kubernetes API resource providing a more scalable alternative to Endpoints for service discovery.

Key-value pairs passed to containers at runtime, used for configuration and runtime behavior control.

High-performance proxy often used in service mesh implementations for containerized environments.

Temporary containers used for troubleshooting or debugging in Kubernetes pods, without affecting the main containers.

Short-lived storage volumes in Kubernetes that share the lifecycle of a pod, useful for temporary data storage.

Routing strategy for load balancing network traffic across multiple paths in container networks.

Distributed key-value store that provides a reliable way to store data across a cluster of machines.

Destinations for cluster-level events in container orchestration platforms, used for monitoring and alerting.

Components or services generating events in containerized environments, often used in event-driven architectures.

Pattern of storing changes to application state as a sequence of events, often used in microservices architectures.

Design pattern capturing all changes to application state as a sequence of events, useful in distributed systems.

Implementation of event sourcing pattern in containerized microservices architectures, ensuring data consistency.

Design approach where containerized services produce, detect, and react to events, enabling loose coupling and scalability.

Rules determining which pods to terminate when a node is under resource pressure in Kubernetes clusters.