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.

Container-based applications run on serverless platforms, combining containerization with auto-scaling.

Strategies to minimize expenses in serverless architectures while maintaining performance.

Processing and analyzing data using serverless compute resources in the cloud, providing scalable and cost-effective insights.

Handling and transforming data using auto-scaling, event-driven cloud services, eliminating infrastructure management overhead.

Fully managed database services that scale automatically based on demand, eliminating the need for manual provisioning and management.

Practices combining serverless architectures with DevOps principles for efficient cloud development.

Extract, Transform, Load processes using serverless compute for data integration in the cloud.

Connecting applications and data sources using serverless compute in cloud environments.

Building application components as independent, auto-scaling functions in the cloud.

Network management and routing tailored for serverless architectures in cloud environments.

Techniques for efficient use of compute, storage, and network resources in serverless systems.

Protecting serverless applications from vulnerabilities and attacks in cloud environments.

Tools and practices for implementing security in serverless cloud architectures.

Comprehensive solutions for protecting serverless applications and data in the cloud.

Websites built and hosted using serverless cloud services for automatic scaling.

Orchestrating sequences of serverless functions to create complex, scalable processes.

Rules for managing permissions in AWS Organizations across multiple accounts, enforcing security and compliance standards.

Automated detection of services and their network locations in cloud environments.

Targets for service performance and availability in cloud environments, defining quality standards for cloud services.

Central component managing configuration and policies in a service mesh architecture.

Component handling inter-service communication in a service mesh architecture, managing traffic flow and security.

Standardized APIs for interacting with service mesh technologies in cloud environments.

Monitoring and analyzing traffic and behavior within a service mesh architecture.

Protecting inter-service communication within a service mesh in cloud environments.

Distributing data across multiple database instances to improve performance and scalability in cloud environments.

Systems for tracking and allocating cloud resource costs within an organization.

Deploying components of an application as separate containers alongside the main container in cloud environments.

Helper containers deployed alongside main application containers to provide additional functionality in cloud environments.

Using light-based chips for high-speed data transmission in cloud data centers, improving network performance and efficiency.

Tools for implementing SRE practices in cloud environments, focusing on automation and reliability.

Cloud-based systems for creating, deploying, and managing self-executing digital contracts.

Approach to cloud network management using software-based controllers instead of hardware.

Managing and optimizing power allocation in cloud data centers through software control.

Abstracting storage services from underlying hardware in cloud environments for flexible management.

Technology for efficiently routing traffic between cloud and on-premises resources.

Integrating digital information with the physical world in cloud-based augmented and virtual reality systems.

Cloud databases optimized for storing and querying location-based data, essential for geospatial applications and analytics.

Cloud-based service for converting spoken language into text, enabling voice-controlled interfaces and transcription.

Strategies for efficiently using and monitoring discounted, interruptible cloud compute resources.

Tools for optimizing the use of discounted, interruptible cloud compute resources.

Techniques for maximizing cost savings and availability when using discounted, interruptible cloud resources.

Discounted, interruptible cloud compute resources available for bidding, offering cost savings for flexible workloads.

Techniques for maintaining application data consistency in distributed cloud environments.

Serverless architectures that maintain state between function invocations in the cloud.

Cloud-based functions that don't retain state between invocations, enhancing scalability.

AWS service for coordinating multiple Lambda functions into serverless workflows.

High-performance, low-latency memory technology bridging DRAM and SSDs in cloud infrastructure.

Mechanisms to ensure consistent performance levels for storage resources in cloud environments.

Automatically moving data between storage tiers based on access patterns to balance cost and performance.

Real-time analysis of continuously flowing data in cloud environments, enabling instant insights and rapid decision-making.

Handling and analyzing large volumes of real-time data streams in cloud environments.

Cloud-based systems for querying continuous data streams using SQL-like syntax, enabling real-time data analysis.

Segmented portion of a cloud network with its own IP address range, allowing for improved security and traffic management.

Tools for tracking and reporting environmental metrics of cloud resource usage, promoting eco-friendly cloud computing.

Documenting environmental impact and energy efficiency of cloud operations, promoting transparency and accountability.

Allocating cloud resources with consideration for environmental impact, optimizing for energy efficiency.

Improving cloud resource efficiency to minimize environmental impact while maintaining performance and reliability.

Practices and technologies minimizing the environmental impact of cloud operations.

Moving to the cloud with strategies to minimize environmental impact, optimizing resource usage and energy efficiency.

Creating cloud facilities with minimal environmental impact and maximum energy efficiency.

Using collective behavior algorithms to optimize cloud resource allocation, improving efficiency and performance.

Coordinating multiple robots using cloud-based swarm intelligence algorithms, enabling scalable and adaptive robotic systems.

Creating artificial datasets for testing and development in cloud environments, preserving privacy and expanding data availability.

Cloud services for creating AI-generated images, videos, and audio, enabling content creation at scale.

Ultra-low latency network interfaces for real-time tactile feedback in cloud applications.

Methods for labeling cloud resources to improve organization, management, and cost allocation.

Cloud infrastructure specifically designed for telecommunications service providers.

Cloud-based platforms for remotely operating robots with real-time feedback, enabling distant manipulation and interaction.

Cloud service converting written text into spoken words, often used in accessibility and voice interface applications.

Cloud-based predictive analytics for time-dependent data, used for trend analysis and future projections.

Cloud databases optimized for storing and querying time-stamped data, essential for IoT and monitoring applications.

Deploying machine learning models on resource-constrained IoT devices connected to the cloud.

Cloud-based tools for replacing sensitive data with non-sensitive tokens to enhance security.

Comprehensive assessment of direct and indirect costs associated with cloud adoption and usage.

Technique of using pre-trained AI models for new tasks, reducing training time and data requirements in the cloud.

Cloud networking service that connects VPCs, on-premises networks, and other cloud services.

Set of best practices for building scalable, maintainable cloud-native applications.

Lightweight, single-purpose machine images for running cloud applications with minimal overhead.

Analysis of costs and revenues associated with individual cloud service units or transactions.

Efforts to create standardized interfaces for interacting with various cloud services.

Secure, encrypted link between a local network and cloud resources, enabling private access to cloud services over public networks.

Cloud-based delivery of virtual reality content to end-user devices, enabling immersive experiences without local processing.

Cloud databases optimized for storing and querying high-dimensional vector data, often used in AI applications.

Managing and tracking changes to code and configurations in cloud-based repositories.

Increasing the capacity of a single cloud resource by adding more power (CPU, RAM, etc.).

Software-defined network providing connectivity for cloud resources, enabling secure and flexible communication.

Cloud-based platforms offering customizable, isolated development and testing environments.

Emulations of computer systems providing scalable, isolated environments in the cloud.

Software-based network devices deployed in cloud environments for various networking functions.

Software implementations of network functions running on cloud infrastructure, replacing traditional hardware appliances.

Cloud-based services for creating, rendering, and delivering virtual reality experiences.

Cloud-hosted VR environments for collaborative work and data visualization, enabling immersive remote collaboration.

Speech-based interfaces for interacting with cloud applications and services, enhancing accessibility and user experience.

Cloud-based processing for generating 3D holographic or volumetric images, enabling immersive visualization applications.

Cloud services for delivering 3D video content for immersive viewing experiences.

Metric measuring water consumption efficiency in cloud data centers, promoting sustainable resource management.

Tracking water consumption and efficiency in cloud data center operations, promoting sustainable resource management.

Cloud-based security service that filters and monitors HTTP traffic between web applications and the Internet.

Low-level language for running high-performance applications in cloud-based web browsers.

Binary instruction format enabling high-performance execution of code in cloud-based web environments.

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.