Engineering Glossary

Alternative terms for the same concept of proposing and reviewing changes in Git-based collaboration.

A Git command used to upload local repository changes to a remote repository, sharing updates with collaborators.

A file in a Git repository that provides information about the project, its purpose, and how to use or contribute to it.

A Git operation that moves or combines a sequence of commits to a new base commit, often used to maintain a linear history.

A Git rebase mode allowing users to modify, reorder, or squash commits before applying them to the target branch.

A Git mechanism that records updates to branch tips and other references in a repository.

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

A strategy where a separate branch is created for release preparation, allowing continued development on the main branch.

A Git repository hosted on a server, allowing collaboration and synchronization between multiple developers.

Centralized location where software packages or modules are stored and managed, facilitating version control and collaboration.

A data structure containing all the files, history, and metadata for a Git-managed project.

Source Control Management, a system for tracking and managing changes to code, of which Git is an example.

The cryptographic hash function used by Git to generate unique identifiers for objects in the repository.

A secure authentication method using a pair of cryptographic keys for accessing remote systems or services.

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

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

The process of preparing changes to be committed in Git, also known as "adding to the index."

A Git feature for temporarily storing uncommitted changes, allowing you to switch branches without committing work in progress.

A Git feature for temporarily saving uncommitted changes, allowing you to switch contexts without committing incomplete work.

A Git command that shows the state of the working directory and staging area, indicating which files are modified or staged.

A Git repository nested within another repository, allowing you to include external projects in your own project.

A named reference to a specific point in Git history, typically used to mark release points or important milestones.

A subscription level for GitHub designed for collaborative groups or small organizations.

The original repository from which a fork is created, or the branch that a local branch is tracking.

Terms describing the flow of changes in Git, with upstream being the source and downstream the destination.

A temporary commit indicating unfinished work, often used to save progress or facilitate code reviews.

A secure alternative to passwords, used for authentication in Git operations, providing limited access to specific resources or actions.

A secondary location where Git stores object files, useful for optimizing storage and performance in large repositories.

A dedicated hardware or virtual machine optimized for running Git services, often used in enterprise environments for improved performance.

The person responsible for addressing an issue or pull request in a Git repository, helping to organize and prioritize tasks.

A temporary code used in two-factor authentication to verify a user's identity when accessing Git repositories or services.

The primary branch in a Git repository from which feature branches are created and into which they are merged after development.

A simple authentication method in Git using a username and password, often discouraged in favor of more secure methods.

The recurring period for which Git hosting services charge users or organizations for their subscriptions and usage.

The email address associated with a Git account or organization for receiving invoices and billing-related communications.

A user role in Git hosting platforms responsible for managing billing information, subscriptions, and payments for an organization.

A subscription package offered by Git hosting services, defining features, storage limits, and pricing for users or organizations.

A brief description of a user's profile on Git platforms, typically including their role, interests, or expertise in software development.

A Git object type representing the contents of a file, stored as a sequence of bytes without any metadata or file attributes.

An action on Git platforms to restrict a user's ability to interact with a repository, often used to manage disruptive behavior.

A set of rules applied to Git branches to control who can push changes, merge, or perform certain actions, enhancing code quality.

A command-line tool often used with Git to transfer data and interact with APIs, supporting various protocols including HTTPS.

A visual representation of an issue or pull request in Git project management tools, used for organizing and prioritizing work.

A series of connected commits in Git, representing a sequence of changes that build upon each other in a repository's history.

A group of changes made to files in a Git repository, typically represented by a commit and including additions, modifications, and deletions.

An automated test or verification process run on Git repositories to ensure code quality, security, or compliance with project standards.

A nested team within a Git organization's hierarchy, inheriting permissions and access rights from its parent team.

A Git command used to remove untracked files and directories from a working directory, helping to maintain a tidy repository.

A technique used in Git hosting services to distribute repository data across multiple servers for improved performance and reliability.

A visual representation of code additions and deletions over time in a Git repository, useful for tracking project activity.

A document outlining expected behavior and guidelines for contributors in a Git repository, promoting a positive community.

A designated person or team responsible for reviewing and approving changes to specific files or directories in a Git repository.

A user with read and write access to a Git repository, able to contribute code and participate in project discussions.

A unique identifier (SHA-1 hash) assigned to each commit in Git, used to reference specific points in a repository's history.

The person who originally created a commit in Git, distinct from the committer who may have applied the changes on behalf of the author.

A visual representation of the commit history in a Git repository, showing the relationships between different branches and merges.

The underlying structure and visual representations of Git's commit history, used for understanding project evolution.

A descriptive text associated with a Git commit, explaining the purpose and details of the changes made in that commit.

A Git object type containing metadata about a commit, including the author, committer, date, and a pointer to the tree object.

A file used by Git to store commit graph information, optimizing performance for operations that traverse the commit history.

A term referring to any Git object that can be resolved to a commit, including commit IDs, branch names, and tags.

A Git feature allowing users to view differences between two branches, often used before merging to review changes.

A visual representation of a user's Git activity over time, showing the frequency and distribution of their contributions to repositories.

A document in a Git repository outlining best practices, coding standards, and procedures for contributors to follow when submitting changes.

The collective changes, commits, issues, and pull requests made by a user to Git repositories, showcasing their involvement in projects.

Any person who has made contributions to a Git repository, whether through code, documentation, or other forms of project support.

A visual representation of all contributors to a Git repository, showing their relative contributions over time and by type.

The fundamental set of Git commands and functionality, excluding third-party extensions or hosting platform-specific features.

A promotional code offering discounts or credits for Git hosting services, often used to attract new users or upgrade existing accounts.

A time-based job scheduler used in Git hosting platforms to automate tasks such as backups, notifications, or periodic code checks.

A Git object not reachable from any reference (branch, tag, etc.), often created during rebasing or other history-altering operations.

A central interface in Git platforms providing an overview of a user's repositories, activities, and notifications.

The primary branch in a Git repository, typically named "main" or "master," serving as the base for new branches and deployments.

A visual representation of a project's dependencies, showing relationships between different components or external libraries.

A visualization of other projects or repositories that depend on a given Git repository, useful for understanding its impact.

An SSH key granting read-only access to a specific Git repository, commonly used for automated deployments or CI/CD processes.

The process of resolving a Git reference (like a branch or tag) to its corresponding commit object or SHA-1 hash.

A state in Git where the HEAD pointer references a specific commit rather than a branch, often used for temporary work.

Tools and features in Git used to identify and troubleshoot issues with repositories, commits, or configuration settings.

A folder within a Git repository containing files and potentially other subdirectories, organized hierarchically.

A term describing a Git working directory that contains uncommitted changes, indicating modifications that haven't been saved to the repository.

Alerts sent via email by Git platforms to inform users about repository activities, mentions, or updates.

A high-tier account type offered by Git hosting services, providing advanced features and support for large organizations.

A problematic merge in Git where conflicts are resolved incorrectly, potentially introducing subtle bugs or inconsistencies.

A type of Git merge where the target branch's pointer is simply moved to the latest commit of the source branch, without creating a new commit.

A temporary branch in Git created to develop a specific feature or fix, typically merged back into the main branch upon completion.

A markdown syntax used in Git documentation and comments to display formatted code snippets with syntax highlighting.

The underlying structure used by Git to store repository data, including objects, refs, and configuration files.

A feature in Git platforms allowing users to receive updates and notifications about other users' activities.

A file containing a Git repository's object database, used in certain Git operations.

A text file specifying intentionally untracked files that Git should ignore, customizable for different project types.

A technique in Git to join two unrelated commit histories, typically used for repository repair or history modification.

A unique identifier (SHA-1) for Git objects, used to ensure data integrity and create content-addressable storage.

The default branch that is checked out when a repository is cloned, typically 'main' or 'master'.

A reference to the tip of a branch, representing the most recent commit in that branch's history.

A characteristic of Git hosting systems designed to ensure continuous operation and minimal downtime.

A script that Git executes before or after events such as commit, push, and receive, used for automating or controlling Git processes.

The unique name assigned to a device on a network, used for identification and communication purposes.

A visual representation of a hash value, often used as a default avatar in Git platforms.

A service that creates, maintains, and manages identity information for users, often integrated with Git platforms.

Machine learning models deployed and executed on edge devices, often with cloud-based training or updates.

Techniques for reducing the size of AI models to run efficiently on resource-constrained edge devices.

Performing text analysis and language understanding tasks on edge devices with cloud support.

Managing and coordinating distributed edge computing resources and their interaction with the cloud.

Using AI on edge devices to forecast equipment failures, with cloud-based model updates and analysis.

Training AI agents on edge devices through interaction with the environment, supported by cloud resources.

Measures to protect data, devices, and applications at the network edge in cloud-connected systems.

Distributed network layer for managing service-to-service communication in edge computing environments.

Data storage systems designed for edge devices with intermittent connectivity to cloud backends.

Applying knowledge from pre-trained cloud models to new tasks on edge devices with limited data.

Creating applications specifically designed to run on edge devices with cloud integration capabilities.

Software development paradigms optimized for creating applications that run on edge devices.

Seamless integration of edge computing resources with centralized cloud infrastructure and services.

Cloud networking component allowing outbound internet communication while blocking inbound traffic.

Fully managed service for deploying and scaling web applications and services on AWS infrastructure.

Static public IP address that can be dynamically assigned to cloud resources, providing consistent access points for applications.

Virtual network interface that can be attached to instances in a VPC, providing flexible networking capabilities.

Virtual network cards that can be attached, detached, and moved between cloud instances.

Integration of analytical capabilities directly into cloud-based applications and workflows.

Cloud-based platforms for analyzing and responding to human emotions in various applications.

Cloud services using AI to detect and respond to user emotions for enhanced interactions.

Protecting data by encoding it both when stored and while moving between cloud systems.

Techniques for securing data both when stored in cloud systems and while being transmitted.

Cloud resource scaling that considers energy consumption alongside performance metrics.

Allocating cloud resources to tasks with consideration for energy consumption and efficiency.

Computing methods designed to minimize energy consumption in cloud environments.

Allocating cloud resources to optimize energy efficiency while meeting performance requirements.

Documenting cloud providers' sustainability and ethical practices for stakeholder transparency.

Open-source edge and service proxy designed for cloud-native applications, providing features like load balancing and observability.

Adherence to principles ensuring fair and responsible use of AI in cloud environments.

Fully managed event routing service for building event-driven applications in Azure.

Storing the state of a system as a sequence of events in cloud-based applications.

Real-time analysis of data streams in cloud environments for immediate insights.

System design where actions are triggered by events in cloud environments, enabling responsive and scalable applications.

Connecting cloud services and applications based on event occurrences, enabling real-time data flow and processing.

APIs that trigger or respond to events in cloud-native applications, enabling real-time data processing and integration.

Developing cloud applications that respond to and generate events, enabling reactive and scalable architectures.

Serverless event bus for building event-driven applications in AWS, facilitating communication between various services.

Data consistency model where all replicas eventually reach a consistent state in distributed cloud systems.

Cloud systems capable of at least one exaFLOPS, or a billion billion calculations per second.

The runtime context in which cloud functions or applications operate, including libraries, dependencies, and configurations.

Monitoring and recording parameters and results of machine learning experiments in cloud environments.

Cloud services for making AI decision-making processes more transparent and interpretable.

Tools for developing AI models with transparent decision-making processes in cloud environments.

Cloud services offering tools to make AI models' decision-making processes more understandable.

Service for creating private connections between Azure datacenters and on-premises infrastructure.

Data integration process where transformation occurs after loading data into the cloud target system.

Process of extracting data from sources, transforming it to fit operational needs, and loading into a target database in the cloud.

Extending cloud capabilities to devices at the extreme edge of the network, like IoT sensors.

Tools for dynamically enabling or disabling features in cloud applications without code deployments.

Centralized repository for storing, managing, and serving machine learning features in cloud environments.

Analyzing data across multiple cloud or edge locations without centralizing the raw data.

System allowing integrated data access across multiple autonomous database management systems in the cloud.

Machine learning technique that trains algorithms across decentralized devices or servers holding local data samples.

Coordinating federated learning processes across multiple edge devices or cloud nodes.

Cloud-based systems for implementing and managing federated learning across distributed datasets.

Applying federated learning techniques to train models on edge devices connected to cloud systems.

Tools for executing queries across multiple distributed databases or data sources in cloud environments.

Cloud service for storing and accessing file data through shared file systems, providing scalable and manageable data storage.

Cloud services providing scalable file storage accessible from multiple compute instances.

Tools and processes for automating financial operations and optimization in cloud environments.

Framework for managing and optimizing cloud costs across an organization, aligning financial and operational goals.

AI-driven tools for continuously optimizing cloud spend and resource allocation.

Security system that monitors and controls incoming and outgoing network traffic in cloud environments.

Open-source, Kubernetes-native serverless framework for building microservices in the cloud, simplifying application deployment.

Extending cloud computing to the edge of the network, bringing processing closer to data sources.

Using historical data and algorithms to predict future trends or values in cloud-based analytics.

Cloud-based encryption allowing computations on encrypted data without decryption.

Tools for building complex serverless applications by combining multiple cloud functions.

Cloud computing model where developers run and manage application functionalities without complex infrastructure.

Adhering to EU data protection regulations in cloud-based data processing and storage.

Cloud compute instances equipped with Graphics Processing Units for parallel processing tasks.

Cloud-based services for creating AI models that can generate new content or data.

Cloud-based systems for analyzing large volumes of location-based data efficiently.

User interfaces that interpret hand or body movements to interact with cloud services.

Methodology using Git repositories as the source of truth for declarative infrastructure and applications in the cloud.

Service that improves availability and performance of applications by optimizing traffic routing across cloud regions.

Database systems that replicate and distribute data across multiple geographic locations in the cloud.

Rules and constraints applied to resources within a Google Cloud organization, enforcing governance and compliance.

Cloud services for analyzing and visualizing complex relationships in large datasets using graph structures.

NoSQL databases designed to store and query data with complex relationships in cloud environments.

Practices and technologies aimed at reducing the environmental impact of cloud data centers and operations.

Practices for developing cloud software that minimizes energy consumption and environmental impact.

Techniques for developing cloud applications that optimize resource usage and reduce environmental impact.

Adhering to US healthcare data protection regulations in cloud-based systems and applications.

Transmitting touch and motion sensations through cloud-connected devices for immersive experiences.

Automated tests to verify the availability and proper functioning of cloud resources and services.

Utilizing excess heat generated by cloud data centers for other purposes, improving energy efficiency.

Packages of pre-configured Kubernetes resources for deploying applications in cloud environments.

Systems managing data across diverse database types and locations in cloud environments.

Using cloud resources for solving complex computational problems requiring significant processing power.

Advanced 3D visualization interfaces for interacting with cloud services and data.

Conceptual cloud data centers using holographic technology for data storage and processing.

Experimental technology using holograms to store data in cloud environments, potentially offering high density.

Experimental data storage technique using holograms in cloud systems for high-density, long-term preservation.

Cloud-based offerings that enable computations on encrypted data without decryption.

Cloud-based service offering encryption that allows computations on encrypted data.

Encryption technique allowing computations on encrypted data without decryption in cloud environments.

Adding more machines to a cloud system to distribute load and increase capacity.

Cloud-based systems facilitating communication between humans and robots or AI agents.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Additional resource consumption introduced by container runtimes and orchestration systems.

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

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

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

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

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

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

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

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

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

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

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

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

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

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