Engineering Glossary

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A way to notify a user on Git platforms by using the @ symbol followed by their username.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

High-density memory architecture using vertically stacked chips, enhancing performance and capacity in cloud server hardware.

Cloud infrastructure optimized for 5G networks, supporting high-speed, low-latency services and applications.

Technique to create multiple virtual networks on a shared physical 5G infrastructure, each optimized for specific use cases.

Integration of 5G networks with edge computing to enable low-latency, high-bandwidth applications closer to end-users.

Future convergence of 6G networks with cloud computing, promising ultra-high speeds and advanced capabilities.

Database transaction properties (Atomicity, Consistency, Isolation, Durability) ensuring data integrity in cloud environments.

Software ensuring AI systems adhere to ethical guidelines and regulations in cloud deployments.

Software for identifying and mitigating ethical issues and biases in AI models deployed in cloud environments.

Solutions for managing ethical considerations and regulatory compliance in cloud-based AI systems.

Structured approaches for managing AI development, deployment, and use in cloud environments.

Comprehensive solutions for managing, monitoring, and controlling AI models in cloud-based systems.

Cloud-based tools for explaining and understanding the decision-making processes of AI models.

Software for analyzing and explaining AI model decisions, crucial for transparency in cloud AI services.

Cloud platforms for discovering, sharing, and monetizing pre-trained AI models and algorithms.

Tools for tracking AI model performance and identifying deviations from expected behavior in cloud environments.

Systems for managing different versions of AI models and enforcing governance policies in cloud deployments.

Cloud-based development environments that use AI to assist programmers in writing and optimizing code.

Integration of AI capabilities into data analytics processes in cloud environments for enhanced insights.

Use of AI algorithms to predict and optimize resource allocation in cloud infrastructures.

Application of AI techniques to improve efficiency, performance, and cost-effectiveness of cloud resources.

Automated distribution of cloud resources using AI to optimize performance and cost-efficiency.

AI-based automation of cloud service selection and integration for complex workflows.

Automated creation of source code using AI models, often integrated into cloud development platforms.

Automated categorization and labeling of data using AI algorithms in cloud storage and processing systems.

Use of AI to improve network performance, efficiency, and security in cloud environments.

Intelligent distribution of computing resources in cloud environments using AI algorithms.

Enhanced SIEM systems using AI for improved threat detection and response in cloud environments.

Use of AI algorithms to identify and analyze potential security threats in cloud systems.

Proactive search for hidden threats in cloud environments using AI-powered analytics and automation.

Cloud infrastructure components designed or configured to enhance AI workload performance.

Database systems tailored for AI workloads, often featuring in-memory processing and distributed architectures.

Use of AI algorithms to identify unusual patterns or behaviors in cloud systems and data.

Intelligent automation of data and application integration processes in cloud environments using AI.

Cloud-based offering of AI capabilities, allowing businesses to leverage AI without extensive in-house expertise.

Cloud-based AI capabilities offered as a service, enabling easy integration of AI into applications.

Application of AI for automating and enhancing IT operations management in cloud environments.

Integrated solutions leveraging AI for automated monitoring, analysis, and management of cloud IT operations.

Use of AI-driven analytics to forecast and prevent system failures in cloud infrastructure.

Service that protects APIs in cloud environments by managing access, monitoring traffic, and preventing attacks.

Dedicated services for securing and managing APIs in cloud environments, including access control and threat protection.

Design approach prioritizing API creation before implementation, common in cloud-native application development.

Integration strategy using purpose-built APIs to connect data, devices, and applications in cloud ecosystems.

Persistent 3D digital content overlaid on the physical world, accessible via cloud infrastructure for augmented reality applications.

Cloud-based tools for analyzing user behavior and performance in augmented and virtual reality environments.

Cloud-hosted services enabling multi-user interaction in shared augmented or virtual reality spaces.

Specialized CDN optimized for delivering AR/VR content with low latency and high bandwidth.

Cloud-based tools and services for creating, testing, and deploying augmented and virtual reality applications.

JSON-based files defining infrastructure and configuration for Azure resource deployment.

Dynamic UIs that adjust based on user behavior, device capabilities, and context in cloud applications.

Techniques to identify and mitigate attacks on ML models in cloud-based AI systems.

Systems for informing administrators or users about important events or issues in cloud environments.

Process of examining AI algorithms for bias, errors, or unintended consequences in cloud-based systems.

Seamless, context-aware interaction methods for accessing cloud services in IoT environments.

Tools for identifying unusual patterns or behaviors in cloud systems, often using machine learning techniques.

Network management approach that optimizes performance based on specific application requirements in cloud environments.

Technique for quickly estimating query results in large-scale cloud databases, trading accuracy for speed.

Low-cost cloud storage for infrequently accessed data with longer retrieval times, e.g., Amazon Glacier, Azure Archive Storage.

Cloud-based storage for software build outputs, dependencies, and related metadata.

Hypothetical cloud offering of human-level AI capabilities across various domains.

Cloud-based environments for developing and testing advanced AI systems approaching human-level intelligence.

Systematic recording of actions and events in cloud systems for security and compliance purposes.

Chronological records of system activities for reconstructing and examining the sequence of events in cloud environments.

Integration of machine learning and natural language processing in cloud-based data analytics workflows.

Shared, persistent digital content overlaid on the physical world, accessible via cloud infrastructure.

Cloud-based systems for managing and delivering AR content and experiences, enabling scalable AR applications.

Cloud-powered generation of AR graphics and content, offloading processing from end-user devices.

Collections of EC2 instances that automatically adjust capacity based on defined conditions.

Automatic adjustment of cloud resources to match workload demands, ensuring optimal performance and cost-efficiency.

Automated machine learning processes for model selection, hyperparameter tuning, and feature engineering in cloud environments.

Cloud-based services automating the machine learning pipeline from data preparation to model deployment and monitoring.

AI-driven tools for improving efficiency and performance of machine learning workflows in the cloud.

Systems that automatically implement and maintain cloud resource policies and compliance.

Continuous, AI-driven assessment of cloud systems against regulatory and security standards.

AI-powered tools for identifying, categorizing, and mapping data assets in cloud environments.

AI-driven systems for managing data quality, security, and compliance in cloud environments.

Cloud-based tools using AI to clean, transform, and prepare data for analysis, streamlining data preparation processes.

AI-powered generation and selection of features for machine learning models in cloud environments.

AI-driven coordination of security incident detection and resolution in cloud systems, automating response workflows.

Cloud services that automate the process of creating and optimizing machine learning models, from data prep to deployment.

Cloud-based systems that automate the end-to-end machine learning model development process, including feature engineering and model selection.

AI-driven tools for simulating cyberattacks to identify vulnerabilities in cloud systems and applications.

AI-powered analysis of cloud architectures to identify potential security risks and attack vectors.

Self-managing, self-healing cloud services requiring minimal human intervention, leveraging AI for operations.

Ultra-low latency edge computing extensions of Azure for 5G networks, bringing cloud resources closer to users.

Service for creating, assigning, and managing policies to control Azure resources and ensure compliance.

Cloud-based services facilitating data exchange and process integration between business partners.

Architectural approach creating backend services tailored to specific frontend application needs in cloud environments.

Physical server dedicated to a single tenant, offering direct hardware access in cloud environments.

Dedicated physical servers without virtualization, offered as a cloud service for high-performance workloads.

Execution of series of jobs without user interaction, often for large-scale data processing in the cloud (e.g., AWS Batch, Azure Batch).

Distributed computing environments for processing and analyzing massive datasets in the cloud.

Interface for monitoring and managing cloud service usage and costs, providing detailed breakdowns and forecasts.

Use of cloud resources for computational biology and genomics research, enabling large-scale analysis and modeling.

Evaluation of cloud data center effects on local ecosystems and wildlife to ensure sustainable operations.

Cloud storage that provides fixed-size raw storage volumes, typically used for databases or file systems.

Cloud services providing persistent block-level storage volumes for use with compute instances.

Cloud-based tools for analyzing and visualizing blockchain data and transactions, offering insights into network activity.

Distributed databases using blockchain technology for enhanced security and immutability in cloud environments.

Software for managing and enforcing rules, permissions, and consensus mechanisms in blockchain networks deployed on cloud platforms.

Cloud-based solutions for connecting blockchain networks with existing enterprise systems and applications.

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.

Kubernetes scheduling constraint that prevents pods from being co-located with other pods based on labels.

Kubernetes object that limits the number of pods of a replicated application that can be down simultaneously.

Stages a pod goes through from creation to termination, including pending, running, succeeded, failed, and unknown phases.

Custom resources in Prometheus Operator for declaratively defining how groups of pods should be monitored.

Mechanisms and configurations for enabling network communication between pods in a Kubernetes cluster.

Additional resources consumed by pod infrastructure on top of the container requests and limits.

High-level summary of where a pod is in its lifecycle, used for pod status reporting and monitoring.

Kubernetes feature allowing importance-based scheduling and eviction of pods when resources are constrained.

Kubernetes object defining privilege and access control settings for a pod or container, enhancing security.

Deprecated Kubernetes feature for cluster-level control over pod security sensitive aspects.

Kubernetes-defined levels (privileged, baseline, restricted) of security settings for pods.

Kubernetes object limiting the number of pods that can be down simultaneously for a given application.

Isolation boundary for one or more containers in a pod, providing shared kernel namespaces and cgroups.

Deprecated cluster-level resource controlling security-sensitive aspects of pod specification.

Tool for managing containers and images without a container daemon, compatible with Docker CLI.

Open-source tool for checking Kubernetes resources against configurable best practices, enhancing reliability.

Use of multiple data storage technologies in microservices architectures to best fit varying data storage needs.

Network address translation technique used in container networking for mapping ports, enabling external access.

Process of forwarding a network port from the host to a container, enabling external access to containerized services.

Web-based management UI for Docker environments, simplifying container operations and monitoring.

Cloud-native storage platform providing persistent storage for containerized applications in multi-cloud environments.

Software-defined storage solution by Portworx for containerized stateful applications in Kubernetes.

Kubernetes scheduling policies that filter out nodes that cannot run a pod, based on resource requirements and constraints.

Kubernetes process of evicting lower-priority pods to schedule higher-priority pods when resources are constrained.

CustomResourceDefinition feature for defining custom columns in kubectl output for custom resources.

Kubernetes scheduling policies that rank nodes that have passed the predicate phase, determining the best placement for a pod.

Kubernetes objects defining the relative importance of pods, used in scheduling and preemption decisions.

Kubernetes feature allowing pods to be assigned different priorities, influencing scheduling and eviction decisions.

Containers running with elevated permissions, potentially accessing host resources and devices.

Deployment strategy gradually rolling out changes to a subset of users or servers, monitoring for issues.

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

Kubernetes volume type that maps several existing volume sources into the same directory, combining multiple configs.

Open-source systems monitoring and alerting toolkit, widely used for Kubernetes and container monitoring.

Component of Prometheus handling alerts, including silencing, inhibition, aggregation, and notifications.

Kubernetes operator that makes it easy to deploy and manage Prometheus instances, simplifying monitoring setup.

Component allowing ephemeral and batch jobs to expose their metrics to Prometheus, enhancing monitoring coverage.

Feature allowing Prometheus to send samples to compatible remote storage systems, enabling long-term storage.

Definitions for recording rules and alerting rules in Prometheus, allowing for complex queries and alert conditions.

Process of choosing the appropriate network protocol for container communication based on requirements.

Kubernetes classifications (Guaranteed, Burstable, BestEffort) for pods based on resource requirements and limits.

Platform providing vulnerability management, policy compliance, and runtime defense for containers.

Container registry by Red Hat offering advanced features like vulnerability scanning and fine-grained access controls.

Kubernetes authorization mechanism for fine-grained control over the actions users can perform.

Guidelines for implementing secure and manageable role-based access control in Kubernetes environments.

Use of role-based access control to implement isolation and access management in multi-tenant Kubernetes clusters.

Integration of Remote Direct Memory Access for high-performance, low-latency container networking.

Platform for managing multiple Kubernetes clusters across different cloud providers and on-premises.

Technique to control the rate of requests or traffic in distributed systems, often implemented in API gateways.

Kubernetes volume type providing direct access to a block device for applications requiring this capability.

Architectural approach emphasizing responsiveness, resilience, elasticity, and message-driven communication in distributed systems.

Security practice of mounting a container's root filesystem as read-only to prevent runtime modifications.

Kubernetes volumes mounted with read-only access, enhancing security by preventing modifications.

Service for storing and distributing container images, crucial for managing and deploying containerized applications.

HTTP API provided by container registries for image management, authentication, and metadata retrieval.

Process of verifying the identity of clients making requests to containerized services or APIs.

Technique of locally caching container images to improve pull times and reduce network usage.

Process of replicating container images across multiple registries for improved availability and reduced latency.

Mechanism for registries to send notifications about events such as image pushes, pulls, or deletions.

Scheduled, periodic releases of software components, often used in microservices architectures for coordinated updates.

Kubernetes controller ensuring a specified number of pod replicas are running at any given time.

Process of verifying the identity of clients making requests to containerized services or APIs.

Technique of duplicating incoming requests to a separate service instance for testing or debugging purposes.

Scheduling strategy aiming to consolidate workloads onto a minimal number of nodes for efficient resource utilization.

Constraints set on the amount of compute resources (CPU, memory) a container can consume, preventing resource hogging.

Kubernetes objects for limiting aggregate resource consumption per namespace, ensuring fair resource allocation.

Specifications of the minimum amount of compute resources required by a container, aiding in scheduling decisions.

Process of optimizing resource allocations for containers to balance performance and efficiency.

Kubernetes object providing constraints that limit aggregate resource consumption per namespace.

Limits on the number of retry attempts for failed operations in distributed systems to prevent cascading failures.

Implementation of automatic reattempts for failed operations in microservices to improve system resilience.

Design pattern for handling transient failures in distributed systems by automatically repeating failed operations.

Kubernetes RBAC object defining a set of permissions within a particular namespace, controlling access to resources.

Kubernetes RBAC object that binds a role to a set of users or service accounts within a namespace.

Kubernetes objects associating Roles and ClusterRoles with users, groups, or service accounts.

Kubernetes RBAC objects defining sets of permissions at namespace or cluster level respectively.

Process of reverting a deployment to a previous version in case of issues with the current version.

Deployment strategy where new versions of an application are gradually rolled out by replacing instances incrementally.

Networking solution for Kubernetes providing native Layer 3 networking without overlays for improved performance.

Open-source cloud-native storage orchestrator for Kubernetes, providing the platform, framework, and support for storage solutions.

Kubernetes operator for file, block, and object storage systems, automating deployment and management of storage services.

Containers running without root privileges, enhancing security by reducing the potential impact of container breakouts.

Lightweight, portable container runtime adhering to the OCI specification, used as a low-level runtime by container engines.

Inner workings and components of the RunC container runtime, including its interaction with Linux kernel features.

Security technology that detects and prevents real-time attacks on containerized applications.

Measures and tools for protecting containerized applications during execution, including threat detection and prevention.

Process of identifying and alerting on security threats to running containers and orchestration platforms.

CRI component responsible for managing the entire lifecycle of a container, including creation, execution, and deletion.

Security policies enforcing mandatory access controls on containers and pods in Linux-based systems.

Monitoring approach focusing on Service Level Objectives to ensure application performance and reliability.

Standard specification for service meshes on Kubernetes, providing a common interface for various implementations.

Standards and implementation for securely identifying and authenticating workloads in dynamic environments.

Use of Single Root I/O Virtualization to provide high-performance networking for containers.

Design pattern for managing data consistency across microservices in distributed transactions.

Implementation of the Saga pattern to maintain data consistency in microservices architectures.

Container runtimes providing additional isolation between the container and the host system for enhanced security.

Techniques for isolating running containers from the host system and each other to enhance security.

Kubernetes API for directly managing the number of replicas of a workload without modifying the entire object.

Kubernetes component responsible for assigning pods to nodes based on resource requirements, policies, and constraints.