Engineering Glossary

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 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.

A Git reference with a specific meaning or function, such as HEAD or FETCH_HEAD.

A deployment environment used for testing changes before releasing to production in Git-based workflows.

A feature on Git hosting platforms allowing users to bookmark repositories of interest.

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.

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

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

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

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

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

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

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

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

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

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

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

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

Platform for observability and monitoring of containerized environments and microservices.

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

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

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

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

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

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

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

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

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

Implementation of OpenTelemetry for standardized observability in containerized environments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Management and coordination of containerized applications across distributed edge locations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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