Computer
Computer: Programmable hardware that processes input and stores or emits results. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Encyclopedia & Knowledge Base
Self-hosting & operations
Comprehensive knowledge base on server operations, containers, databases, networking, media pipelines, and self-hosted infrastructure — clearly explained with architecture, practical operations, and troubleshooting.
0%1024 terms
Structure
32 × 32
Languages
Deutsch + English
Scope
32 Module
Focus
Operations & Troubleshooting
0 / 1024 completed
Module 1Computer and server systemsFundamentals, operations, and troubleshooting for Computer and server systems.32 terms
Server
Server: A system that continuously provides services or data to other systems. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Client
Client: A program or device that requests a service from a server. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Host (Computer and server systems)
Host: The operating system or machine on which a process or virtual environment runs. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Hardware
Hardware: The physical components of a computer, such as CPU, RAM, and storage. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Software
Software: Executable programs and data that determine hardware behaviour. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Operating system
Operating system: The layer that manages hardware and provides processes, files, and networking to programs. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Kernel
Kernel: The privileged core of an operating system that controls hardware access and resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Linux distribution
Linux distribution: A Linux kernel bundled with package management, system tools, and maintained packages. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Ubuntu Server
Ubuntu Server: An Ubuntu distribution aimed at server operation without requiring a desktop interface. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →CPU
CPU: The processor that executes machine instructions and coordinates computation. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →CPU core
CPU core: A largely independent execution unit inside a CPU. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Thread
Thread: A schedulable flow of control within a process. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →RAM
RAM: Volatile working memory for currently needed code and data. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Memory utilization
Memory utilization: The occupied portion of memory, including useful caches. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Swap
Swap: Disk space into which the kernel can move infrequently used memory pages. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Mass storage
Mass storage: Non-volatile storage for persistently retained data. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →HDD
HDD: A magnetic storage device with mechanically moving read/write heads. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →SSD
SSD: A non-volatile flash storage device without moving parts. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →File system
File system: The data structures and rules used to organise files on a storage device. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Partition
Partition: A logically delimited region of a block device. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Mount point
Mount point: The directory where a file system is attached to the directory tree. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Network interface
Network interface: The logical or physical endpoint through which a host sends and receives network packets. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →GPU
GPU: A highly parallel processor for graphics and compute workloads. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →VRAM
VRAM: Fast memory used directly by a GPU for models, textures, and intermediate results. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →NVIDIA driver
NVIDIA driver: The kernel and user-space components connecting the operating system to an NVIDIA GPU. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →System time
System time: The current time maintained by the operating system for logs, certificates, and schedules. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Time zone
Time zone: A rule set that converts UTC into local time including daylight-saving changes. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Hostname
Hostname: The local name identifying a computer in the system and often on the network. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Reboot
Reboot: A controlled restart of the operating system and its services. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Shutdown
Shutdown: The controlled stopping of services and powering down of a system. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Availability
Availability: The proportion of time during which a service is usable as intended. Detailed documentation covering architecture, production operations, and troubleshooting within “Computer and server systems”.
Open article →Module 2Files, paths, and directoriesFundamentals, operations, and troubleshooting for Files, paths, and directories.32 terms
File
File: A named sequence of bytes with metadata in a file system. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Directory
Directory: A file-system object that maps names to files and subdirectories. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Absolute path
Absolute path: A path that starts at the root and is unambiguous regardless of the working directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Relative path
Relative path: A path resolved relative to the current or specified starting directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Working directory
Working directory: The directory from which a process resolves relative paths. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Root directory
Root directory: The topmost node of a file-system directory tree. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Home directory
Home directory: The personal default directory of a user account. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Hidden file
Hidden file: A file whose Unix name begins with a dot and is therefore often hidden. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →File extension
File extension: The suffix after the final dot in a name, commonly indicating format or purpose. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →File name
File name: The directory entry name used to address a file. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Case sensitivity
Case sensitivity: The property of treating upper- and lower-case letters in names as distinct. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Symbolic link
Symbolic link: A special file that stores another path as its target. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Hard link
Hard link: An additional directory name for the same inode and file content. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Inode
Inode: The file-system structure holding metadata and block references but not the file name. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Owner
Owner: The user account assigned to a file-system object. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Group
Group: A set of user accounts that can be granted shared permissions. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →File permissions
File permissions: Rules allowing read, write, and execute operations for owner, group, and others. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Read permission
Read permission: Permission to read file content or list directory names. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Write permission
Write permission: Permission to modify file content or create and remove directory entries. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Execute permission
Execute permission: Permission to execute a file or traverse a directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →umask
umask: A bit mask that removes default permissions when files are created. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Recursive operation
Recursive operation: An operation that traverses a directory and its complete subtree. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Glob pattern
Glob pattern: A shell pattern such as `*.log` that expands to matching path names. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →File size
File size: The number of bytes logically stored in a file. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Free disk space
Free disk space: Storage capacity not yet occupied and available for new data. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Temporary file
Temporary file: A file for short-lived intermediate data that may be removed after use. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Lock file
Lock file: A file used by processes to coordinate ownership or exclusive work. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Configuration file
Configuration file: A file storing mutable program settings outside the code. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Log file
Log file: An append-oriented file containing time-ordered operational and error messages. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Binary file
Binary file: A file whose bytes are not directly interpreted as readable text. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Text file
Text file: A file whose characters are read using a character encoding. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Character encoding
Character encoding: The mapping between characters and their stored byte sequences. Detailed documentation covering architecture, production operations, and troubleshooting within “Files, paths, and directories”.
Open article →Module 3Shell fundamentalsFundamentals, operations, and troubleshooting for Shell fundamentals.32 terms
Shell
Shell: A program that reads and expands commands and starts programs. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Bash
Bash: A common Unix shell with a scripting language and interactive command line. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Terminal
Terminal: An interface presenting input and output for a shell or console program. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Prompt (Shell fundamentals)
Prompt: The shell input marker showing readiness and often contextual information. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Command (Shell fundamentals)
Command: The name of a program or shell built-in to execute. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Argument
Argument: A positional value passed to an invoked program. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Option
Option: A usually named switch that changes command behaviour. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Exit code
Exit code: An integer through which a process reports success or failure to its caller. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Standard output
Standard output: The normal output stream of a process, file descriptor 1. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Standard error
Standard error: The separate diagnostic output stream of a process, file descriptor 2. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Standard input
Standard input: The input stream of a process, file descriptor 0. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Pipe
Pipe: A connection feeding one process's standard output into the next process's input. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Redirection
Redirection: A shell instruction connecting input or output streams to files or other destinations. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Environment variable
Environment variable: A named string value inherited by child processes. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Shell variable
Shell variable: A named value in the current shell state that is not automatically inherited. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Quoting
Quoting: Shell syntax controlling spaces or expansions within an argument. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Escaping
Escaping: Neutralising the special meaning of an individual character. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Wildcard
Wildcard: A placeholder character such as `*` or `?` in a matching pattern. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Command history
Command history: The sequence of previously entered commands stored by the shell. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Tab completion
Tab completion: The shell feature that completes names and options after pressing Tab. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →pwd
pwd: The shell command that prints the absolute path of the working directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →cd
cd: The shell command that changes the current shell's working directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →ls
ls: The command for listing directory entries and metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →mkdir
mkdir: The command for creating one or more directories. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →cp
cp: The command for copying files or directory trees. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →mv
mv: The command for moving or renaming files. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →rm
rm: The command for removing directory entries without a recycle bin. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →find
find: A tool that searches directory trees by file properties. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →grep
grep: A tool that filters text lines using regular expressions. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →head
head: A tool that outputs the beginning of a text stream. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →tail
tail: A tool that outputs or follows the end of a text stream. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →less
less: An interactive pager for navigating long text output. Detailed documentation covering architecture, production operations, and troubleshooting within “Shell fundamentals”.
Open article →Module 4Users, permissions, and processesFundamentals, operations, and troubleshooting for Users, permissions, and processes.32 terms
User account
User account: A stored user identity with a login name, identifier, and assigned permissions. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →System user
System user: A usually non-interactive account under which a service runs with limited privileges. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →UID
UID: The numeric user identifier the kernel uses instead of the name for permission checks. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →GID
GID: The numeric identifier of a Unix group used for shared access permissions. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Root user
Root user: The Unix account with unrestricted system privileges. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →sudo
sudo: A tool for controlled execution of individual commands under another identity. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Least privilege
Least privilege: The principle of granting an account or process only the privileges required for its task. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Process
Process: A running program instance with its own address space and resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →PID
PID: The numeric identifier of a running process. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Parent process
Parent process: The process that creates another process and can collect its status. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Child process
Child process: A process started by a parent process and assigned its own PID. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Daemon
Daemon: A long-running service process operating in the background. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Foreground process
Foreground process: A process currently attached to the controlling terminal. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Background process
Background process: A process that continues without owning the current terminal input. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Signal
Signal: An asynchronous kernel notification informing a process about an event or control request. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →SIGTERM
SIGTERM: The catchable signal requesting graceful process termination. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →SIGKILL
SIGKILL: The uncatchable signal that immediately terminates a process. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Process state
Process state: The current scheduler state of a process, such as running, sleeping, or exited. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Zombie process
Zombie process: An exited process whose status has not yet been collected by its parent. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Process priority
Process priority: The weighting used by the scheduler when distributing CPU time among processes. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Nice value
Nice value: A Unix value influencing CPU priority, with larger values receiving less preference. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Resource limit (Users, permissions, and processes)
Resource limit: A kernel-enforced ceiling for resources such as memory, processes, or open files. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Open file
Open file: A file or other I/O endpoint used by a process through a descriptor. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →File descriptor
File descriptor: A small process-local number referring to an open file, pipe, or socket. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →User group
User group: A collection of user accounts to which shared permissions are assigned. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Ownership change
Ownership change: Changing the user or group assignment of a file-system object. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →chmod
chmod: The Unix command for changing file permission bits. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →chown
chown: The Unix command for changing owner and group. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →ps
ps: The tool for taking a snapshot of running processes and their identifiers. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →top
top: An interactive real-time monitor for processes, CPU, and memory usage. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →htop
htop: An interactive visual process viewer with search and process controls. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →kill
kill: The command for sending a signal to a process or process group. Detailed documentation covering architecture, production operations, and troubleshooting within “Users, permissions, and processes”.
Open article →Module 5Networking fundamentalsFundamentals, operations, and troubleshooting for Networking fundamentals.32 terms
Network
Network: Connected systems exchanging data through agreed protocols. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →LAN
LAN: A geographically limited local network. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →WAN
WAN: A network connecting remote local networks across larger distances. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Internet
Internet: The global interconnected network based on the Internet protocol suite. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →IP address
IP address: A logical address by which an interface is reachable in an IP network. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →IPv4
IPv4: The IP version using 32-bit addresses. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →IPv6
IPv6: The IP version using 128-bit addresses and a vastly larger address space. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Subnet
Subnet: A contiguous IP address range sharing a network prefix. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Subnet mask
Subnet mask: An IPv4 mask separating the network prefix from the host portion of an address. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Default gateway
Default gateway: The router to which packets for destinations outside the local network are sent. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Router
Router: A device or process that forwards packets between IP networks. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Switch
Switch: A Layer 2 device forwarding Ethernet frames based on MAC addresses. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →MAC address
MAC address: An identifier of a network interface on the local Ethernet layer. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Port
Port: A 16-bit number mapping TCP or UDP traffic to a service. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →TCP
TCP: A connection-oriented transport protocol providing ordered, acknowledged delivery. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →UDP
UDP: A connectionless transport protocol without delivery or ordering guarantees. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Socket
Socket: An operating-system endpoint for network communication. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Connection
Connection: The stateful communication channel between two network endpoints. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Packet
Packet: A bounded unit of data with headers and payload transmitted through a network. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Bandwidth
Bandwidth: The theoretical or practical amount of data transferable per unit time. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Latency
Latency: The delay between sending and observing a response. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Packet loss
Packet loss: The failure of individual transmitted packets to reach their destination. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Loopback
Loopback: A virtual network interface whose traffic remains within the local host. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →localhost
localhost: The name conventionally resolving to the local loopback address. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Private IP address
Private IP address: An address from reserved ranges that is not globally routed on the Internet. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Public IP address
Public IP address: An IP address that is globally routable on the Internet. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →NAT
NAT: Rewriting IP addresses or ports at a network boundary. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Firewall
Firewall: A rule-enforcement point that permits or drops network traffic by its properties. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Inbound traffic
Inbound traffic: Network traffic arriving at a host or service from outside. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Outbound traffic
Outbound traffic: Network traffic sent outward by a host or service. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →ping
ping: A diagnostic tool sending ICMP echo requests and measuring response times. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →traceroute
traceroute: A diagnostic tool revealing router hops toward a destination. Detailed documentation covering architecture, production operations, and troubleshooting within “Networking fundamentals”.
Open article →Module 6Web fundamentalsFundamentals, operations, and troubleshooting for Web fundamentals.32 terms
Web browser
Web browser: A client that retrieves web resources over HTTP, renders HTML, and executes scripts. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Website
Website: A related collection of web resources under a common origin. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Web server
Web server: Software that accepts HTTP requests and returns static or dynamic responses. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →URL
URL: A URI describing the location of and access method for a resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →URI
URI: A string that uniquely identifies a resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Scheme
Scheme: The leading URL component such as `https` that specifies access protocol and semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Host (Web fundamentals)
Host: The operating system or machine on which a process or virtual environment runs. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Domain
Domain: A hierarchical DNS name that makes services and resources addressable. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Subdomain
Subdomain: A subordinate namespace to the left of a parent domain. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Path
Path: The URL component identifying a resource within an origin. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Query parameter
Query parameter: A named key-value pair after `?` that parameterises a request. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Fragment
Fragment: The URL component after `#` used locally by the client for navigation. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTP
HTTP: A stateless request-response protocol for web resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTPS
HTTPS: HTTP carried inside an authenticated and encrypted TLS connection. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTP request
HTTP request: A client message containing a method, target, headers, and optional body. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTP response
HTTP response: The server reply containing a status code, headers, and optional payload. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTP method
HTTP method: The verb of an HTTP request that identifies the desired operation. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →GET
GET: The safe HTTP method for retrieving a resource representation. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →POST
POST: The HTTP method for submitting data for server-side processing. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →PUT
PUT: The idempotent HTTP method for fully replacing a target resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →PATCH
PATCH: The HTTP method for partially modifying a resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →DELETE (Web fundamentals)
DELETE: The idempotent HTTP method for removing a resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →HTTP status code
HTTP status code: A three-digit number classifying success, redirection, or failure of an HTTP response. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Header
Header: A named metadata field in an HTTP message. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Body
Body: The optional payload of an HTTP request or response. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Content-Type
Content-Type: The HTTP header specifying the media format and optional character encoding of a body. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →User-Agent
User-Agent: A client identifier in an HTTP header that may describe software and platform. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Cookie
Cookie: A small value stored and sent by the browser for an origin. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Cache (Web fundamentals)
Cache: A fast temporary store avoiding repeated computation or transfer. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Redirect
Redirect: An HTTP response directing the client to another target. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Origin
Origin: The combination of URL scheme, host, and port forming a web security boundary. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Same-origin policy
Same-origin policy: The browser rule limiting script access across different origins. Detailed documentation covering architecture, production operations, and troubleshooting within “Web fundamentals”.
Open article →Module 7Data and configuration formatsFundamentals, operations, and troubleshooting for Data and configuration formats.32 terms
Plain text
Plain text: Unformatted character content without binary structure or markup semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →JSON
JSON: A text format for objects, arrays, and primitive values. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →YAML
YAML: An indentation-sensitive, human-readable data format commonly used for configuration. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →TOML
TOML: A configuration format using typed key-values and tables. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →XML
XML: A textual tree format with nested elements and attributes. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →CSV
CSV: A row-oriented tabular format with delimited field values. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Markdown
Markdown: A lightweight markup language for structured text. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →HTML
HTML: The markup language describing a web page's structure and semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →MIME type
MIME type: A standardised label for content format, such as `image/png`. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →UTF-8
UTF-8: A variable-length Unicode character encoding using one to four bytes. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Unicode
Unicode: The standard assigning abstract code points to writing-system characters. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Line ending
Line ending: The character sequence marking the end of a text line, such as LF or CRLF. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Escape sequence
Escape sequence: A character sequence encoding a special character or control behaviour. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Key-value pair
Key-value pair: A named association from a key to one value. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Object
Object: A structured collection of named properties. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Array
Array: An ordered list of zero or more values. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Boolean
Boolean: A data type with the two truth values true and false. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Null value
Null value: An explicit value representing the absence of a value. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Number
Number: A numeric data value that may be integral or decimal depending on the format. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →String
String: An ordered sequence of characters. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Schema
Schema: A machine-checkable description of allowed data structure and types. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Serialization
Serialization: Converting a runtime value into a storable or transferable format. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Deserialization
Deserialization: Reconstructing a runtime value from serialised data. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Parser
Parser: Software that turns input text into structure according to a grammar. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Syntax error
Syntax error: Input that violates the grammar of the format being used. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Indentation
Indentation: Leading whitespace that controls readability or, in YAML, nesting. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Comment
Comment: Human-readable text ignored by a parser according to the format rules. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Duplicate key
Duplicate key: Multiple occurrences of the same key in an object or mapping. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →.env file
.env file: A text file of environment variables loaded into processes by a tool. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Secret
Secret: A confidential value such as a password, key, or token. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Placeholder
Placeholder: A recognisable substitute marker to be replaced with a real value before use. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Default value
Default value: The value used automatically when no explicit value is supplied. Detailed documentation covering architecture, production operations, and troubleshooting within “Data and configuration formats”.
Open article →Module 8Systematic debuggingFundamentals, operations, and troubleshooting for Systematic debugging.32 terms
Failure symptom
Failure symptom: The observable effect of a failure without yet claiming its cause. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Error message
Error message: Diagnostic output describing the type, location, or identifier of an error. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Reproduction
Reproduction: A sequence of steps that triggers the same failure again. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Minimal reproduction
Minimal reproduction: The smallest reliable set of inputs and steps that triggers a failure. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Hypothesis
Hypothesis: A testable proposition about a cause or behaviour. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Root cause
Root cause: The underlying cause whose correction permanently removes the failure. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Symptom
Symptom: A measurable or visible sign of a problem. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Correlation
Correlation: Co-occurrence of two observations without a proven cause-and-effect relationship. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Causation
Causation: A demonstrated cause-and-effect relationship between a change and an outcome. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Log analysis
Log analysis: Examining log messages by time and content to diagnose failures. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Timestamp (Systematic debugging)
Timestamp: A time value locating an event in logs or measurements. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Stack trace
Stack trace: The chain of function or method calls at the time of a failure. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Warning
Warning: A message about an unusual condition that does not necessarily stop execution. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Error
Error: A condition in which a requested operation did not complete correctly. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Debug level
Debug level: A highly verbose log level exposing internal state for diagnosis. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Info level
Info level: A log level for normal, relevant operational events. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Health check (Systematic debugging)
Health check: A repeatable test of the minimum required service state. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Smoke test
Smoke test: A brief test of core functions after startup or a change. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Integration test
Integration test: A test exercising real interfaces between multiple components. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Regression test
Regression test: A test detecting recurrence of a previous defect. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Expected state
Expected state: The documented state a system or test is supposed to reach. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Actual state
Actual state: The state actually observed in a system or test. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Differential test
Differential test: A comparison of the same input across two versions or implementations. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Configuration check
Configuration check: Checking that settings exist, are syntactically valid, and take effect. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Syntax check
Syntax check: A check for grammar errors without fully executing the program. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Network check
Network check: A layered check of name resolution, route, port, and application response. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Permission check (Systematic debugging)
Permission check: Checking effective identity and access permissions for a resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Storage check
Storage check: Checking a storage target for mounting, free space, inodes, and writability. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Resource check
Resource check: Checking whether CPU, RAM, storage, or GPU meets a service requirement. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Rollback (Systematic debugging)
Rollback: Returning to a previously known working state. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Change history
Change history: A chronological record of relevant configuration and software changes. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Root cause analysis
Root cause analysis: A structured investigation of symptom, cause, correction, and prevention. Detailed documentation covering architecture, production operations, and troubleshooting within “Systematic debugging”.
Open article →Module 9Linux services and packagesFundamentals, operations, and troubleshooting for Linux services and packages.32 terms
Package manager
Package manager: A tool for installing, upgrading, and removing packages with dependencies. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →APT
APT: The package-management interface for Debian-based systems. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Package source
Package source: A configured location from which packages and metadata are obtained. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Repository (Linux services and packages)
Repository: A source of versioned packages and their metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Package index
Package index: A local catalogue of available package names, versions, and dependencies. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Package version
Package version: An identifier for a particular published revision of a package. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Dependency
Dependency: A component required by another piece of software to function. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Transitive dependency
Transitive dependency: An indirect dependency required by a direct dependency. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Installation
Installation: Copying and registering software for use on a system. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Uninstallation
Uninstallation: Controlled removal of installed software and its registration. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Upgrade
Upgrade: Moving to a newer software version while retaining intended data. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Security update (Linux services and packages)
Security update: An update that fixes known security vulnerabilities. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Version pinning
Version pinning: Fixing a concrete version so upgrades do not change it unexpectedly. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →systemd
systemd: The common Linux service manager and init process. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Unit
Unit: A resource definition managed by systemd. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service unit
Service unit: A systemd file describing service startup, process supervision, and dependencies. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Timer unit
Timer unit: A systemd file activating another unit at times or intervals. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Target unit
Target unit: A systemd grouping unit used to synchronise multiple units toward a target state. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service status
Service status: The load, active, and failure state reported by systemd for a service. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service start
Service start: Instructing the service manager to start an inactive service. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service stop
Service stop: Controlled termination of a running service by the service manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service restart
Service restart: Stopping and then starting a service again. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Service autostart
Service autostart: Enabling a service to start automatically at a boot target. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →System journal
System journal: The structured, centrally queried log store maintained by systemd-journald. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →journalctl
journalctl: The tool for querying the structured systemd journal. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →systemctl
systemctl: The tool for controlling and inspecting systemd units. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Boot process
Boot process: The sequence from loading the kernel to reaching requested system targets. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →EnvironmentFile
EnvironmentFile: A file of environment variables read by a systemd unit. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →ExecStart
ExecStart: The systemd directive containing the main command started for a service. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Restart policy (Linux services and packages)
Restart policy: The rule determining when a service manager restarts an exited process. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Unit dependency
Unit dependency: A declared ordering or requirement relationship between systemd units. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Load state
Load state: The systemd state indicating whether a unit file was found and loaded successfully. Detailed documentation covering architecture, production operations, and troubleshooting within “Linux services and packages”.
Open article →Module 10Storage and backupsFundamentals, operations, and troubleshooting for Storage and backups.32 terms
Block device
Block device: A storage device exposing data in addressable blocks. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Volume
Volume: A logically usable storage region with its own lifecycle. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Bind mount (Storage and backups)
Bind mount: Making an existing directory tree available at a second mount point. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Network share
Network share: Shared file storage exposed through a network protocol. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →SMB
SMB: A network protocol for file and printer sharing, especially in Windows environments. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →NFS
NFS: A Unix-oriented protocol for remote file systems. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Storage capacity
Storage capacity: The total amount of data a storage target can logically hold. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Disk usage
Disk usage: The occupied portion of a file system, including metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Reserved space
Reserved space: Space retained by a file system for administration or privileged processes. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →File system check
File system check: A consistency check of a file system’s metadata and references. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Snapshot
Snapshot: A point-in-time view of data, often implemented with copy-on-write. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Backup
Backup: A separate copy from which lost or damaged data can be restored. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Full backup
Full backup: A backup of all selected data independent of earlier backups. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Incremental backup
Incremental backup: A backup of changes since the most recent backup of any type. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Differential backup
Differential backup: A backup of all changes since the most recent full backup. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Restore
Restore: Recovering backed-up data into a usable state. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Restore test
Restore test: A controlled recovery attempt proving that a backup is usable. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Backup rotation
Backup rotation: Rule-based retention and deletion of backups across time. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Retention period
Retention period: The defined duration for which data or backups are retained. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Offsite backup
Offsite backup: A backup stored in a geographically or administratively separate location. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →3-2-1 backup rule
3-2-1 backup rule: The recommendation for three copies on two media types with one offsite copy. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Checksum
Checksum: A computed verification value for detecting unintended data changes. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →SHA-256
SHA-256: A cryptographic hash function producing a 256-bit digest. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Data integrity
Data integrity: The property that data remains complete and unintentionally unaltered. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Atomic write
Atomic write: A write operation whose result becomes visible either completely or not at all. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →File synchronization
File synchronization: Reconciling two file sets based on their differences. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →rsync
rsync: A tool for efficiently synchronising file trees based on differences. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Archive
Archive: A file bundling multiple files and metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Compression
Compression: Encoding data using less storage space. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →tar
tar: An archive format and tool bundling file trees with metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Deletion deadline
Deletion deadline: The defined time after which data should be removed automatically. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Data lifecycle
Data lifecycle: The sequence of data creation, use, retention, and deletion. Detailed documentation covering architecture, production operations, and troubleshooting within “Storage and backups”.
Open article →Module 11DNS, TLS, CDN, and tunnelsFundamentals, operations, and troubleshooting for DNS, TLS, CDN, and tunnels.32 terms
DNS
DNS: The distributed system resolving domain names into resource data. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →DNS zone
DNS zone: An administratively managed portion of the DNS namespace. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Resource record
Resource record: A typed DNS data record containing a name, value, and lifetime. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →A record
A record: A DNS record mapping a name to an IPv4 address. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →AAAA record
AAAA record: A DNS record mapping a name to an IPv6 address. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →CNAME record
CNAME record: A DNS alias pointing one name to another canonical name. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →TXT record
TXT record: A DNS record for text values, often used for verification or policy declarations. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →MX record
MX record: A DNS record naming responsible mail servers and their priorities. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Name server
Name server: An authoritative or recursive service that answers DNS queries. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Resolver
Resolver: A service answering DNS queries recursively or from cache. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →DNS cache
DNS cache: A cache of resolved DNS answers retained until their TTL expires. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →DNS TTL
DNS TTL: The permitted caching lifetime of a DNS record in seconds. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →DNS propagation
DNS propagation: The delayed visibility of changed DNS answers caused by distributed caches. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Certificate
Certificate: A signed document binding a public key to names. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Certificate authority
Certificate authority: A trust authority that validates identities and digitally signs certificates. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Let's Encrypt
Let's Encrypt: A public automated certificate authority providing free TLS certificates. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →TLS
TLS: A protocol providing authenticated, confidential, integrity-protected connections. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →TLS handshake
TLS handshake: The setup of a TLS connection including negotiation, certificate validation, and key establishment. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Public key
Public key: The shareable key component used for encryption or signature verification. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Private key
Private key: The secret key component used for decryption or signature creation. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Certificate chain
Certificate chain: The sequence from a server certificate through intermediates to a trusted root. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →SNI
SNI: The TLS extension through which a client states the requested hostname during the handshake. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →HSTS
HSTS: An HTTP header instructing browsers to use HTTPS exclusively for a period. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →CDN
CDN: A distributed network of edge servers delivering content closer to users. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Reverse tunnel
Reverse tunnel: An internally initiated connection carrying controlled external access back inward. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Cloudflare Tunnel
Cloudflare Tunnel: An outbound connection from `cloudflared` to Cloudflare’s edge for published origins. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →cloudflared
cloudflared: The agent establishing Cloudflare tunnels and forwarding to origin services. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Tunnel token
Tunnel token: A confidential credential allowing a tunnel agent to join a tunnel configuration. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Public hostname
Public hostname: The publicly resolvable DNS name through which a service is addressed. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Origin service
Origin service: The internal origin service to which a proxy or tunnel forwards requests. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Zero Trust
Zero Trust: An access model that trusts no network location by default and evaluates every request. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Access policy
Access policy: A rule defining identities and conditions for permitted access. Detailed documentation covering architecture, production operations, and troubleshooting within “DNS, TLS, CDN, and tunnels”.
Open article →Module 12Docker fundamentalsFundamentals, operations, and troubleshooting for Docker fundamentals.32 terms
Container
Container isolates a process with its own filesystem and network namespace. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container image
Container image provides the immutable filesystem and startup metadata for a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Image layer
Image layer stores one immutable filesystem change inside an image. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Dockerfile
Dockerfile reproducibly describes how Docker builds an image from instructions. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Build context
Build context is the file set available to the Docker builder for COPY and ADD. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Base image
Base image provides the immutable filesystem and startup metadata for a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Image tag
Image tag is a human-readable and mutable reference to an image version. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Image digest
Image digest identifies image content immutably through a cryptographic hash. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container registry
Container registry stores and distributes versioned container images. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker Hub
Docker Hub stores and distributes versioned container images. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container runtime
Container runtime belongs to Docker's control path between a user command and a running container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker Engine
Docker Engine belongs to Docker's control path between a user command and a running container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker daemon
Docker daemon belongs to Docker's control path between a user command and a running container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker CLI
Docker CLI belongs to Docker's control path between a user command and a running container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container start
Container start controls a defined transition in the container lifecycle. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container stop
Container stop controls a defined transition in the container lifecycle. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container restart
Container restart controls a defined transition in the container lifecycle. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container log
Container log contains standard output and standard error from the container's main process. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Port mapping
Port mapping maps a reachable host port to a listening container port. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container port
Container port maps a reachable host port to a listening container port. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Host port
Host port maps a reachable host port to a listening container port. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker network
Docker network provides isolated name resolution and packet transport between containers. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Bridge network
Bridge network provides isolated name resolution and packet transport between containers. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Overlay network (Docker fundamentals)
Overlay network provides isolated name resolution and packet transport between containers. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Docker volume
Docker volume attaches persistent or host-provided data to a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Bind mount (Docker fundamentals)
Bind mount attaches persistent or host-provided data to a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Read-only mount
Read-only mount attaches persistent or host-provided data to a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Entrypoint (Docker fundamentals)
Entrypoint defines the program and arguments run as PID 1 in a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Command (Docker fundamentals)
Command defines the program and arguments run as PID 1 in a container. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Container environment
Container environment passes runtime configuration to the process as key-value pairs. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Health check (Docker fundamentals)
Health check periodically verifies that a service is functional rather than merely started. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Restart policy (Docker fundamentals)
Restart policy controls a defined transition in the container lifecycle. Detailed documentation covering architecture, production operations, and troubleshooting within “Docker fundamentals”.
Open article →Module 13Compose, Swarm, and PortainerFundamentals, operations, and troubleshooting for Compose, Swarm, and Portainer.32 terms
Docker Compose
Docker Compose declaratively describes multiple container services as one application. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Compose file
Compose file declaratively describes multiple container services as one application. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Compose service
Compose service groups reproducibly configured containers inside a Compose namespace. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Compose project
Compose project groups reproducibly configured containers inside a Compose namespace. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Docker Swarm
Docker Swarm is part of the cluster that assigns service desired state to available nodes. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm manager
Swarm manager is part of the cluster that assigns service desired state to available nodes. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm worker
Swarm worker is part of the cluster that assigns service desired state to available nodes. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm node
Swarm node is part of the cluster that assigns service desired state to available nodes. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Stack
Stack groups related Swarm services from a declarative stack file. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm service
Swarm service represents desired configuration, concrete execution, or replica state of a Swarm service. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm task
Swarm task represents desired configuration, concrete execution, or replica state of a Swarm service. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Replica
Replica represents desired configuration, concrete execution, or replica state of a Swarm service. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Desired state
Desired state represents desired configuration, concrete execution, or replica state of a Swarm service. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Current state
Current state represents desired configuration, concrete execution, or replica state of a Swarm service. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Rolling update
Rolling update controls the order, pace, and rollback behavior of a service update. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Update parallelism
Update parallelism controls the order, pace, and rollback behavior of a service update. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Update delay
Update delay controls the order, pace, and rollback behavior of a service update. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Rollback configuration
Rollback configuration controls the order, pace, and rollback behavior of a service update. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Placement constraint
Placement constraint restricts tasks to nodes with matching roles or labels. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Resource limit (Compose, Swarm, and Portainer)
Resource limit limits consumption or reserves schedulable CPU and memory resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Resource reservation
Resource reservation limits consumption or reserves schedulable CPU and memory resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm secret
Swarm secret delivers sensitive or regular configuration data to selected services in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Swarm config
Swarm config delivers sensitive or regular configuration data to selected services in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Overlay network (Compose, Swarm, and Portainer)
Overlay network connects services across the cluster and resolves their logical names. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Ingress network
Ingress network connects services across the cluster and resolves their logical names. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Routing mesh
Routing mesh connects services across the cluster and resolves their logical names. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Service discovery
Service discovery connects services across the cluster and resolves their logical names. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Portainer
Portainer provides a web interface for inspecting and managing Docker. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Stack editor
Stack editor groups related Swarm services from a declarative stack file. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Stack deployment
Stack deployment groups related Swarm services from a declarative stack file. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Service scaling
Service scaling changes the desired number of identical service replicas. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Service inspect (Compose, Swarm, and Portainer)
Service inspect shows the complete active service specification held by the Swarm manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Compose, Swarm, and Portainer”.
Open article →Module 14Reverse proxies and routingFundamentals, operations, and troubleshooting for Reverse proxies and routing.32 terms
Reverse proxy
Reverse proxy mediates connections between client and destination but in opposite trust directions. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Forward proxy
Forward proxy mediates connections between client and destination but in opposite trust directions. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Router rule
Router rule decides from host or path which router handles a request. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Host rule
Host rule decides from host or path which router handles a request. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →PathPrefix rule
PathPrefix rule decides from host or path which router handles a request. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →EntryPoint (Reverse proxies and routing)
EntryPoint defines the listening address and port of a Traefik ingress. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Middleware (Reverse proxies and routing)
Middleware modifies or checks a request between router and backend. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Backend service
Backend service describes reachable target instances and their distribution behind the proxy. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Load balancer
Load balancer describes reachable target instances and their distribution behind the proxy. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Upstream
Upstream describes reachable target instances and their distribution behind the proxy. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Traefik
Traefik is a reverse-proxy web server for routing, TLS, and forwarding. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Traefik provider
Traefik provider supplies Traefik with dynamic routing objects from an infrastructure source. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Docker provider
Docker provider supplies Traefik with dynamic routing objects from an infrastructure source. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Swarm provider
Swarm provider supplies Traefik with dynamic routing objects from an infrastructure source. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Traefik label
Traefik label encodes dynamic Traefik configuration directly on a container or service. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →nginx
nginx is a reverse-proxy web server for routing, TLS, and forwarding. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →nginx server block
nginx server block selects the virtual host, path scope, and forwarding target in nginx. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →nginx location block
nginx location block selects the virtual host, path scope, and forwarding target in nginx. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →proxy_pass
proxy_pass selects the virtual host, path scope, and forwarding target in nginx. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Forwarded header
Forwarded header carries original protocol, host, or client address across proxy boundaries. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →X-Forwarded-For
X-Forwarded-For carries the original client IP as an ordered proxy chain. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →X-Forwarded-Proto
X-Forwarded-Proto tells the backend the original client scheme such as HTTPS. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →X-Real-IP
X-Real-IP carries original protocol, host, or client address across proxy boundaries. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →WebSocket upgrade
WebSocket upgrade upgrades an HTTP connection to a persistent bidirectional connection. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Request timeout
Request timeout limits waiting time for connection setup or an upstream response. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Response timeout
Response timeout limits waiting time for connection setup or an upstream response. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Upload limit
Upload limit limits request size or frequency before the backend. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Request body limit
Request body limit limits request size or frequency before the backend. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Sticky session
Sticky session binds repeated client requests to the same backend instance. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Rate limit
Rate limit limits request size or frequency before the backend. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Compression middleware
Compression middleware compresses eligible HTTP responses according to Accept-Encoding. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Access log
Access log records each proxy request with status, target, and duration. Detailed documentation covering architecture, production operations, and troubleshooting within “Reverse proxies and routing”.
Open article →Module 15Frontend fundamentalsFundamentals, operations, and troubleshooting for Frontend fundamentals.32 terms
HTML document
HTML document structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →DOM
DOM is the runtime-mutable object structure of the loaded HTML document. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →HTML element
HTML element structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →HTML attribute
HTML attribute structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Semantic HTML
Semantic HTML structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Form
Form structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Input field
Input field structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Button
Button structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Label
Label structures content and interaction as accessible browser document elements. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS
CSS controls selection, values, and size calculation of visual presentation. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS selector
CSS selector controls selection, values, and size calculation of visual presentation. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS class
CSS class controls selection, values, and size calculation of visual presentation. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS custom property
CSS custom property controls selection, values, and size calculation of visual presentation. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS box model
CSS box model controls selection, values, and size calculation of visual presentation. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Flexbox
Flexbox arranges elements along one or two layout axes. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →CSS Grid
CSS Grid arranges elements along one or two layout axes. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Responsive design
Responsive design adapts layout and interaction to available space and device characteristics. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Media query
Media query adapts layout and interaction to available space and device characteristics. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →JavaScript
JavaScript provides the language and standard used to program browser state and interaction. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →ECMAScript
ECMAScript provides the language and standard used to program browser state and interaction. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Event (Frontend fundamentals)
Event reports a user or browser action and attaches reacting code. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Event listener
Event listener reports a user or browser action and attaches reacting code. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Fetch API
Fetch API performs asynchronous network work and represents its eventual result. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Promise
Promise performs asynchronous network work and represents its eventual result. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →async and await
async and await performs asynchronous network work and represents its eventual result. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Browser storage
Browser storage stores small key-value data in the browser with different lifetimes. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Local Storage
Local Storage stores small key-value data in the browser with different lifetimes. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Session Storage
Session Storage stores small key-value data in the browser with different lifetimes. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →File upload
File upload passes user-selected files to browser logic and an upload endpoint. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Drag and drop
Drag and drop passes user-selected files to browser logic and an upload endpoint. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Progress indicator
Progress indicator visualizes measurable upload or processing progress instead of mere waiting. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Web accessibility
Web accessibility makes content usable by keyboard, screen readers, and sufficient contrast. Detailed documentation covering architecture, production operations, and troubleshooting within “Frontend fundamentals”.
Open article →Module 16Backends and web APIsFundamentals, operations, and troubleshooting for Backends and web APIs.32 terms
Backend
Backend processes server-side rules, data access, and responses behind a web interface. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Application server
Application server processes server-side rules, data access, and responses behind a web interface. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Node.js
Node.js forms the JavaScript runtime, package tool, and project manifest of a Node project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →npm
npm forms the JavaScript runtime, package tool, and project manifest of a Node project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →package.json
package.json forms the JavaScript runtime, package tool, and project manifest of a Node project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Python
Python forms the language, isolated package environment, and installer of a Python project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Virtual environment
Virtual environment forms the language, isolated package environment, and installer of a Python project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →pip
pip forms the language, isolated package environment, and installer of a Python project. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →FastAPI
FastAPI serves a Python web application through an ASGI server and optional process manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →ASGI
ASGI serves a Python web application through an ASGI server and optional process manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Uvicorn
Uvicorn serves a Python web application through an ASGI server and optional process manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Endpoint
Endpoint maps an HTTP method and URL path to a backend function. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Route
Route maps an HTTP method and URL path to a backend function. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Request model
Request model defines and validates the shape, types, and output of API data. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Response model
Response model defines and validates the shape, types, and output of API data. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Validation
Validation defines and validates the shape, types, and output of API data. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Middleware (Backends and web APIs)
Middleware runs reusable cross-cutting logic or supplied dependencies per request. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Dependency injection
Dependency injection runs reusable cross-cutting logic or supplied dependencies per request. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Background task
Background task moves work out of the direct response path or executes waiting work concurrently. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Multipart upload
Multipart upload transfers large files in chunks rather than as one JSON object. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Streaming response
Streaming response transfers large files in chunks rather than as one JSON object. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Server-sent events
Server-sent events keeps a connection open for server updates or bidirectional messages. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →WebSocket
WebSocket keeps a connection open for server updates or bidirectional messages. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →OpenAPI
OpenAPI describes API contracts in machine-readable form and presents them interactively. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Swagger UI
Swagger UI describes API contracts in machine-readable form and presents them interactively. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Error handling
Error handling translates internal failures into controlled, logged HTTP responses. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Exception handler
Exception handler translates internal failures into controlled, logged HTTP responses. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →CORS
CORS defines which browser origins may read an API or send credentials. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Pydantic
Pydantic defines and validates the shape, types, and output of API data. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Async function
Async function moves work out of the direct response path or executes waiting work concurrently. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Worker process
Worker process moves work out of the direct response path or executes waiting work concurrently. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Gunicorn
Gunicorn serves a Python web application through an ASGI server and optional process manager. Detailed documentation covering architecture, production operations, and troubleshooting within “Backends and web APIs”.
Open article →Module 17PostgreSQLFundamentals, operations, and troubleshooting for PostgreSQL.32 terms
Relational database
Relational database stores structured data transactionally and serves it to multiple clients through SQL. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →PostgreSQL
PostgreSQL stores structured data transactionally and serves it to multiple clients through SQL. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database server
Database server stores structured data transactionally and serves it to multiple clients through SQL. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database
Database stores structured data transactionally and serves it to multiple clients through SQL. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database schema
Database schema organizes records into named structures with defined types. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Table
Table organizes records into named structures with defined types. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Column
Column organizes records into named structures with defined types. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Row
Row organizes records into named structures with defined types. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Data type
Data type organizes records into named structures with defined types. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Primary key
Primary key enforces identity, relationships, or valid values directly in the database. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Foreign key
Foreign key enforces identity, relationships, or valid values directly in the database. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Unique constraint
Unique constraint enforces identity, relationships, or valid values directly in the database. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Not-null constraint
Not-null constraint enforces identity, relationships, or valid values directly in the database. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database index
Database index accelerates matching search and sort operations at the cost of storage and writes. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →B-tree index
B-tree index accelerates matching search and sort operations at the cost of storage and writes. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →SQL
SQL is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →SELECT
SELECT is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →INSERT
INSERT is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →UPDATE
UPDATE is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →DELETE (PostgreSQL)
DELETE is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →JOIN
JOIN is a statement for reading, writing, or joining relational data. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Transaction
Transaction groups changes so they fully apply or are safely discarded. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →COMMIT (PostgreSQL)
COMMIT groups changes so they fully apply or are safely discarded. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →ROLLBACK (PostgreSQL)
ROLLBACK groups changes so they fully apply or are safely discarded. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →ACID
ACID groups changes so they fully apply or are safely discarded. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Connection pool
Connection pool keeps a limited set of reusable database connections. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database migration
Database migration moves schema and data reproducibly from one version to the next. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database role
Database role defines database identity and allowed operations according to least privilege. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database user
Database user defines database identity and allowed operations according to least privilege. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Database permission
Database permission defines database identity and allowed operations according to least privilege. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →pg_dump
pg_dump exports logical PostgreSQL structures and data into a backup format. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →pg_restore
pg_restore restores an archive created by pg_dump in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “PostgreSQL”.
Open article →Module 18SQLite, Redis, and queuesFundamentals, operations, and troubleshooting for SQLite, Redis, and queues.32 terms
SQLite
SQLite stores a relational database directly in one local file. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Database file
Database file stores a relational database directly in one local file. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Write-ahead logging
Write-ahead logging writes changes to a WAL log first and improves concurrent reads. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →SQLite transaction
SQLite transaction stores a relational database directly in one local file. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis
Redis keeps data primarily in memory for very fast key access. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →In-memory database
In-memory database keeps data primarily in memory for very fast key access. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis key
Redis key is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis value
Redis value is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Expiration
Expiration automatically deletes a Redis key after a defined remaining lifetime. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis TTL
Redis TTL automatically deletes a Redis key after a defined remaining lifetime. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis hash
Redis hash is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis list
Redis list is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis set
Redis set is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis sorted set
Redis sorted set is a Redis data structure with its own access and ordering semantics. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis Pub/Sub
Redis Pub/Sub distributes transient messages to currently connected subscribers without persistence. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Redis persistence
Redis persistence persists Redis data periodically or as an append-only change log. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →RDB snapshot
RDB snapshot persists Redis data periodically or as an append-only change log. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →AOF
AOF persists Redis data periodically or as an append-only change log. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Cache (SQLite, Redis, and queues)
Cache avoids expensive recomputation through reusable results and measurable hits. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Cache miss
Cache miss avoids expensive recomputation through reusable results and measurable hits. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Cache hit
Cache hit avoids expensive recomputation through reusable results and measurable hits. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Job queue
Job queue moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Job
Job moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Producer
Producer moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Consumer
Consumer moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Queue worker
Queue worker moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →FIFO
FIFO moves discrete work items from a producer to a processing worker. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Retry
Retry reprocesses failed jobs or isolates them after limited attempts. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Dead-letter queue
Dead-letter queue reprocesses failed jobs or isolates them after limited attempts. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Visibility timeout
Visibility timeout temporarily reserves a fetched job until it is acknowledged or becomes visible again. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Idempotency key
Idempotency key makes repeated equivalent requests have the same effect through a stable key. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Distributed lock
Distributed lock coordinates exclusive access by multiple processes through a shared lock key. Detailed documentation covering architecture, production operations, and troubleshooting within “SQLite, Redis, and queues”.
Open article →Module 19Accounts, authentication, and sessionsFundamentals, operations, and troubleshooting for Accounts, authentication, and sessions.32 terms
Identity
Identity represents a person or service identity with associated account state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Account
Account represents a person or service identity with associated account state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Registration
Registration represents a person or service identity with associated account state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Login
Login verifies credentials and starts or ends an authenticated context. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Logout
Logout verifies credentials and starts or ends an authenticated context. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Authentication
Authentication verifies credentials and starts or ends an authenticated context. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Authorization
Authorization decides after identity verification whether a specific action is allowed. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Password hash
Password hash stores passwords as deliberately expensive one-way derivations with an individual random value. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Salt
Salt stores passwords as deliberately expensive one-way derivations with an individual random value. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Argon2
Argon2 stores passwords as deliberately expensive one-way derivations with an individual random value. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →bcrypt
bcrypt stores passwords as deliberately expensive one-way derivations with an individual random value. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Session
Session links a random browser identifier to server-side login state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Session ID
Session ID links a random browser identifier to server-side login state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Session cookie
Session cookie links a random browser identifier to server-side login state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Access token
Access token carries time-limited access claims or renews them without a password. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Refresh token
Refresh token carries time-limited access claims or renews them without a password. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →JWT
JWT carries time-limited access claims or renews them without a password. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →OAuth 2.0
OAuth 2.0 standardizes delegated authorization and adds verifiable user identity. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →OpenID Connect
OpenID Connect standardizes delegated authorization and adds verifiable user identity. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Google login
Google login connects an external identity provider through an exactly registered callback address. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Discord login
Discord login connects an external identity provider through an exactly registered callback address. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Callback URL
Callback URL connects an external identity provider through an exactly registered callback address. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →CSRF
CSRF prevents or limits cross-site state-changing requests carrying existing cookies. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →SameSite cookie
SameSite cookie prevents or limits cross-site state-changing requests carrying existing cookies. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Secure cookie
Secure cookie restricts session cookies to HTTPS and removes JavaScript access. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →HttpOnly cookie
HttpOnly cookie restricts session cookies to HTTPS and removes JavaScript access. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Role model
Role model decides after identity verification whether a specific action is allowed. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Permission check (Accounts, authentication, and sessions)
Permission check decides after identity verification whether a specific action is allowed. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Account recovery
Account recovery represents a person or service identity with associated account state. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Email verification
Email verification confirms control of a communication channel through short-lived one-time tokens. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Brute-force protection
Brute-force protection limits repeated login attempts per identity and source. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Login rate limit
Login rate limit verifies credentials and starts or ends an authenticated context. Detailed documentation covering architecture, production operations, and troubleshooting within “Accounts, authentication, and sessions”.
Open article →Module 20Monitoring and observabilityFundamentals, operations, and troubleshooting for Monitoring and observability.32 terms
Monitoring
Monitoring makes system state visible through selected signals and explorable relationships. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Observability
Observability makes system state visible through selected signals and explorable relationships. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Metric
Metric is a numeric time-series value with a name, labels, and timestamp. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Log
Log records discrete events and bounds their local storage use. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Trace
Trace links work steps or logs from the same request across service boundaries. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Event (Monitoring and observability)
Event describes one state-changing occurrence with time and context. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Dashboard
Dashboard combines selected measurements for a specific operational purpose. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Alert
Alert triggers a notification for an actionable measured condition. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Threshold
Threshold triggers a notification for an actionable measured condition. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Uptime
Uptime measures reachability over time or through repeated external functional checks. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Availability check
Availability check measures reachability over time or through repeated external functional checks. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Liveness probe
Liveness probe separates process liveness from readiness to receive real traffic. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Readiness probe
Readiness probe separates process liveness from readiness to receive real traffic. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →CPU metric
CPU metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Memory metric
Memory metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Disk metric
Disk metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Network metric
Network metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →GPU metric
GPU metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Queue metric
Queue metric measures utilization or saturation of a specific technical resource. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Request rate
Request rate quantifies request volume, error fraction, or request duration. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Error rate
Error rate quantifies request volume, error fraction, or request duration. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Response time
Response time quantifies request volume, error fraction, or request duration. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Percentile
Percentile describes a distribution boundary instead of an outlier-sensitive average. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →P50
P50 describes a distribution boundary instead of an outlier-sensitive average. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →P95
P95 describes a distribution boundary instead of an outlier-sensitive average. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →P99
P99 describes a distribution boundary instead of an outlier-sensitive average. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Prometheus
Prometheus collects numeric metrics from instrumented targets using a pull model. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Exporter
Exporter collects numeric metrics from instrumented targets using a pull model. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Grafana
Grafana visualizes and alerts on data from connected observability sources. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Structured log
Structured log records discrete events and bounds their local storage use. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Correlation ID
Correlation ID links work steps or logs from the same request across service boundaries. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Log rotation
Log rotation records discrete events and bounds their local storage use. Detailed documentation covering architecture, production operations, and troubleshooting within “Monitoring and observability”.
Open article →Module 21FFmpeg, containers, and codecsFundamentals, operations, and troubleshooting for FFmpeg, containers, and codecs.32 terms
FFmpeg
FFmpeg is a command-line framework for reading, filtering, and writing media streams. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →ffprobe
ffprobe reads container, stream, codec, and timing information without transcoding. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Media container
Media container packages encoded streams or changes only their wrapper without re-encoding. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Codec
Codec defines compression and conversion between raw and encoded media. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Encoder
Encoder defines compression and conversion between raw and encoded media. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Decoder
Decoder defines compression and conversion between raw and encoded media. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Transcoding
Transcoding defines compression and conversion between raw and encoded media. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Remuxing
Remuxing packages encoded streams or changes only their wrapper without re-encoding. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Bitrate
Bitrate controls data volume and quality distribution across a medium's duration. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Constant bitrate
Constant bitrate controls data volume and quality distribution across a medium's duration. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Variable bitrate
Variable bitrate controls data volume and quality distribution across a medium's duration. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →CRF
CRF controls data volume and quality distribution across a medium's duration. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Two-pass encoding
Two-pass encoding controls data volume and quality distribution across a medium's duration. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Resolution
Resolution determines the spatial or temporal structure of a video stream. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Aspect ratio
Aspect ratio determines the spatial or temporal structure of a video stream. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Frame rate
Frame rate determines the spatial or temporal structure of a video stream. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Keyframe
Keyframe determines the spatial or temporal structure of a video stream. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →GOP
GOP determines the spatial or temporal structure of a video stream. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Pixel format
Pixel format describes digital color channels, range, and color resolution of an image. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Color space
Color space describes digital color channels, range, and color resolution of an image. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Chroma subsampling
Chroma subsampling describes digital color channels, range, and color resolution of an image. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →H.264
H.264 is a video codec with its own balance of quality, compute cost, and compatibility. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →H.265
H.265 is a video codec with its own balance of quality, compute cost, and compatibility. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →VP9
VP9 is a video codec with its own balance of quality, compute cost, and compatibility. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →AV1
AV1 is a video codec with its own balance of quality, compute cost, and compatibility. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →AAC
AAC is a lossy audio codec with different container and device profiles. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Opus
Opus is a lossy audio codec with different container and device profiles. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →MP3
MP3 is a lossy audio codec with different container and device profiles. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Stream mapping
Stream mapping explicitly selects which video, audio, or subtitle streams are written. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Filtergraph
Filtergraph connects media filters with named inputs and outputs into a processing pipeline. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Hardware encoding
Hardware encoding performs video encoding on specialized hardware or general CPU cores. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Software encoding
Software encoding performs video encoding on specialized hardware or general CPU cores. Detailed documentation covering architecture, production operations, and troubleshooting within “FFmpeg, containers, and codecs”.
Open article →Module 22Media, image, and document formatsFundamentals, operations, and troubleshooting for Media, image, and document formats.32 terms
MP4
MP4 is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →WebM
WebM is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Matroska
Matroska is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →MOV
MOV is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →AVI
AVI is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →WAV
WAV stores audio uncompressed or losslessly and suits editing and archiving. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →FLAC
FLAC stores audio uncompressed or losslessly and suits editing and archiving. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →OGG
OGG is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →M4A
M4A is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →PNG
PNG is a raster image format with its own support for quality, animation, or transparency. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →JPEG
JPEG is a raster image format with its own support for quality, animation, or transparency. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →WebP
WebP is a raster image format with its own support for quality, animation, or transparency. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →AVIF
AVIF is a media container that bundles supported video, audio, and metadata streams. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →GIF
GIF is a raster image format with its own support for quality, animation, or transparency. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →SVG
SVG describes shapes mathematically and remains sharp when enlarged. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →PDF preserves page layout or recovers text from scanned document pages. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →PDF page
PDF page preserves page layout or recovers text from scanned document pages. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Raster image
Raster image stores an image as a finite pixel grid with fixed resolution. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Vector graphic
Vector graphic describes shapes mathematically and remains sharp when enlarged. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Alpha channel
Alpha channel stores per-pixel opacity in addition to color values. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Transparency
Transparency stores per-pixel opacity in addition to color values. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Image compression
Image compression reduces image data without information loss or by discarding detail in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Lossless compression
Lossless compression reduces image data without information loss or by discarding detail in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Lossy compression
Lossy compression reduces image data without information loss or by discarding detail in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Metadata
Metadata stores extra information such as capture time, orientation, or device model outside the pixels. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →EXIF
EXIF stores extra information such as capture time, orientation, or device model outside the pixels. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →ICC color profile
ICC color profile maps numeric color values to a defined color space for consistent display. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →DPI
DPI is print-density metadata and does not by itself change pixel dimensions. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Audio channel
Audio channel is one discrete audio stream within mono, stereo, or multichannel sound. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Sample rate
Sample rate states how many audio samples are stored per second. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Bit depth
Bit depth determines the numeric range of each uncompressed audio sample. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Document OCR
Document OCR preserves page layout or recovers text from scanned document pages. Detailed documentation covering architecture, production operations, and troubleshooting within “Media, image, and document formats”.
Open article →Module 23Machine learning fundamentalsFundamentals, operations, and troubleshooting for Machine learning fundamentals.32 terms
Artificial intelligence
Artificial intelligence is the umbrella term for systems that automate tasks such as perception, reasoning, or planning. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Machine learning
Machine learning derives decision rules from example data instead of programming every rule by hand. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Deep learning
Deep learning uses many stacked neural layers to learn features directly from large datasets. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Neural network
A neural network connects weighted computational units in layers and adjusts their weights from an error signal. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Model
A model is the learned mathematical mapping that turns inputs into predictions or generated outputs after training. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Model weight
A model weight is a learned numeric value that controls how strongly a signal affects another model component. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Parameter
A parameter is a model value optimized during training; parameter count affects memory use and capacity. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Training
Training repeatedly computes predictions, errors, and weight updates over example data. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Training data
Training data are the examples from which a model learns patterns; selection and labeling shape its behavior. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Inference
Inference runs an already trained model on new inputs without further weight updates. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Input
An input is data encoded for a model, such as token IDs, normalized pixels, or audio samples. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Output
An output is the raw or post-processed model result, such as logits, text tokens, an image tensor, or a transcript. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Tensor
A tensor is a multidimensional numeric array with a data type and shape used by ML frameworks. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Batch
A batch groups multiple examples into one computation and trades memory consumption for throughput. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Epoch
An epoch is one complete pass through the dataset selected for training. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Learning rate
The learning rate scales each optimization step; values that are too high destabilize learning, while low values slow it down. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Loss function
A loss function expresses the difference between a model prediction and its training target as a number. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Optimizer
An optimizer uses gradients and their history to calculate concrete model-weight updates. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Checkpoint
A checkpoint stores model state and often optimizer state at a particular training or release point. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Model architecture
A model architecture defines layer types, connections, and data flow and must match the checkpoint. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Base model
A base model is a broadly trained starting point used directly or adapted to a task. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Fine-tuning
Fine-tuning continues training an existing base model on a smaller task-specific dataset. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Quantization
Quantization stores weights or activations with fewer bits, trading accuracy for memory and compute savings. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Distillation
Distillation trains a smaller student model to imitate outputs or intermediate representations of a larger teacher. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Embedding
An embedding maps discrete content to a dense numeric vector where similar content can be close together. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Token
A token is the smallest unit produced by a tokenizer and is not necessarily a complete word. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Tokenizer
A tokenizer splits text using a fixed vocabulary and deterministically maps pieces to token IDs. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Transformer
A transformer processes sequences with attention and parallel feed-forward blocks rather than a purely recurrent loop. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Attention
Attention weights relationships between sequence positions so relevant parts influence the current computation more strongly. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Language model
A language model estimates probabilities over token sequences and generates text by repeatedly selecting the next token. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Large language model
A large language model is a scaled-up language model with many parameters and broad pretraining. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Multimodal model
A multimodal model processes or generates multiple modalities such as text, images, and audio in one pipeline. Detailed documentation covering architecture, production operations, and troubleshooting within “Machine learning fundamentals”.
Open article →Module 24Diffusion and ComfyUIFundamentals, operations, and troubleshooting for Diffusion and ComfyUI.32 terms
Diffusion model
A diffusion model learns to remove noise step by step from a random state to generate data. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Forward diffusion
Forward diffusion progressively adds noise to training data according to a defined schedule. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Reverse diffusion
Reverse diffusion reconstructs a sample from noise step by step under control of the learned model. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Noise
Noise is the random starting tensor whose values are determined by seed, shape, and data type. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Noise schedule
The noise schedule defines how much noise each timestep adds or removes. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Latent space
Latent space is a compressed feature representation in which many image models operate instead of using pixels. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →VAE
A variational autoencoder compresses images into latents and decodes latents back into pixels. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Text encoder
A text encoder turns prompt tokens into contextual vectors that condition image generation. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →CLIP
CLIP learns a shared image-text space and commonly provides text conditioning in diffusion pipelines. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Prompt (Diffusion and ComfyUI)
A prompt describes desired subjects, properties, and relationships as positive conditioning for the generator. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Negative prompt
A negative prompt provides unwanted properties as counter-conditioning when the selected model supports it. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Sampler
A sampler is the numerical method that calculates the next latent state from model predictions. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Scheduler
A scheduler distributes noise levels or sigmas across sampling steps, changing the trajectory and result. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Sampling steps
Sampling steps are the number of iterative denoising computations; more steps are not automatically better. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Guidance scale
Guidance scale controls how strongly conditional and unconditional predictions are separated. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →CFG
Classifier-free guidance combines conditional and unconditional model predictions to control prompt adherence. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Seed
The seed initializes the random-number generator and makes identical inputs reproducible under identical conditions. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Denoising strength
Denoising strength determines how far the starting latent is noised and therefore changed in image-to-image workflows. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Text-to-image
Text-to-image creates an image latent from text conditioning and random noise without an input image. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Image-to-image
Image-to-image encodes a source image as a latent and modifies it under additional prompt conditioning. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Inpainting
Inpainting regenerates only a masked image region while using the unmasked context. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Outpainting
Outpainting expands the canvas and generates new areas that match the existing edge context. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Upscaling
Upscaling enlarges an image and reconstructs detail through interpolation or a learned model. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →ControlNet
ControlNet adds spatial guidance such as edges, pose, depth, or segmentation to a diffusion model. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →LoRA
LoRA stores a small low-rank weight update that adapts a base model without a full new checkpoint. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →ComfyUI
ComfyUI is a node-based interface and API that executes generative-model components as a directed workflow. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →ComfyUI node
A ComfyUI node has typed inputs and outputs and performs one bounded processing step. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →ComfyUI workflow
A ComfyUI workflow is a directed graph of compatible nodes including parameters and connections. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Workflow JSON
Workflow JSON serializes node types, IDs, parameters, and edges for reproducible ComfyUI execution. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Model loader
A model loader reads weights and matching architecture components from the model directory into memory. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →KSampler
KSampler is the ComfyUI node that combines latent, conditioning, sampler, scheduler, seed, and step count. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →VAE Decode
VAE Decode converts a completed latent tensor into visible pixels using the matching VAE. Detailed documentation covering architecture, production operations, and troubleshooting within “Diffusion and ComfyUI”.
Open article →Module 25Image models and model operationsFundamentals, operations, and troubleshooting for Image models and model operations.32 terms
FLUX
FLUX is a family of transformer-based image-generation models from Black Forest Labs with distinct workflow and licensing requirements. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →FLUX Schnell
FLUX Schnell is the FLUX variant optimized for few-step, fast inference and is governed by its own model license. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →FLUX Dev
FLUX Dev is a higher-quality, more compute-intensive FLUX variant whose non-commercial license must be reviewed before use. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Quantized image model
A quantized image model lowers weight bit width to fit in less VRAM but may lose detail. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →GGUF model
A GGUF model bundles quantized tensors and metadata in a file format readable by compatible loaders. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Safetensors
Safetensors is a weight format without executable pickle code and with explicit tensor offsets. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Diffusers
Diffusers is a Python library providing model components, schedulers, and pipelines for diffusion inference. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Hugging Face Hub
The Hugging Face Hub distributes versioned model artifacts, model cards, and licenses through repositories. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Model card
A model card documents a model's purpose, training context, limitations, license, and known risks. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Model license
A model license defines whether weights may be copied, modified, used commercially, or offered as a service. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Commercial use
Commercial use means employing a model or its outputs in an activity intended to generate revenue. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Checkpoint directory
The checkpoint directory is the loader's expected location for weight files and associated configuration. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Model download
A model download transfers large versioned artifacts and must account for licensing, free space, and checksums. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →File integrity
File integrity uses a cryptographic checksum to confirm that a model artifact arrived complete and unchanged. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Model cache
A model cache retains loaded or downloaded artifacts, saving time at the cost of RAM or disk space. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →VRAM requirement
VRAM requirement includes weights, activations, latents, and temporary buffers and depends on precision and resolution. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Native resolution
Native resolution is the size range used during training where an image model usually keeps compositions stable. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Aspect-ratio bucket
An aspect-ratio bucket groups training or inference sizes with similar ratios under bounded pixel budgets. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Tiled upscaling
Tiled upscaling processes overlapping image tiles separately to reach high resolutions with limited VRAM. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Real-ESRGAN
Real-ESRGAN is a learned super-resolution model that enlarges images and compensates for common real-world degradation. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Background removal
Background removal segments the main subject and turns the result into a transparent alpha channel. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Image segmentation
Image segmentation assigns a class or instance to each pixel, producing spatial regions. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Segmentation mask
A segmentation mask encodes per pixel which region should be selected, protected, or modified. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Object detection
Object detection returns classes and bounding boxes for detected objects but not a pixel-accurate mask. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Object removal
Object removal masks a subject and reconstructs the hidden background through inpainting. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Inpainting mask
An inpainting mask marks pixels to regenerate while preserving the rest of the image. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Mask feathering
Mask feathering softens a hard mask edge over a chosen radius to hide transitions. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Bounding box
A bounding box is a rectangular coordinate region describing a detected object's position and extent. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Prompt weighting
Prompt weighting changes the relative influence of individual text fragments on image conditioning. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Clip skip
CLIP skip uses an earlier text-encoder layer, changing prompt representation for models trained for it. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →LoRA weight
LoRA weight scales how strongly a loaded LoRA update affects the base model. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Model switching
Model switching replaces weights and sometimes encoders or VAE; incompatible leftover components must be unloaded. Detailed documentation covering architecture, production operations, and troubleshooting within “Image models and model operations”.
Open article →Module 26Audio, transcription, and music generationFundamentals, operations, and troubleshooting for Audio, transcription, and music generation.32 terms
Speech recognition
Speech recognition converts acoustic speech signals into text or token sequences. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Transcription
Transcription produces readable text from an audio recording and may add timestamps or speaker information. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Whisper
Whisper is an open model family for multilingual speech recognition, translation, and speech activity detection. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →faster-whisper
faster-whisper runs Whisper models through CTranslate2 with optimized data types and reduced memory use. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Whisper model size
Whisper model size determines parameter count, language accuracy, VRAM demand, and processing speed. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Language detection
Language detection estimates the likely spoken language from an audio segment for subsequent decoding. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Timestamp (Audio, transcription, and music generation)
A timestamp maps text or an event to a position on the audio timeline. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Segment
A transcription segment groups a continuous audio interval with text, start, end, and confidence. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Word timestamp
A word timestamp estimates the start and end of one recognized word rather than an entire segment. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Voice activity detection
Voice activity detection separates speech regions from silence or noise and reduces unnecessary inference. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Diarization
Diarization assigns speech segments to different speaker identities without needing their names. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Speaker segmentation
Speaker segmentation determines time boundaries where a different speaker begins or ends. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Subtitle
A subtitle connects text to time intervals and optionally formatting or positioning information. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →SRT
SRT is a simple subtitle format containing an index, time interval, and text block. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →WebVTT
WebVTT is a web subtitle format with timestamps, cues, and optional presentation settings. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Text normalization
Text normalization standardizes numbers, punctuation, capitalization, or filler words after recognition. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Audio resampling
Audio resampling changes a signal's sample rate and must prevent aliasing with suitable filters. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Mono downmix
A mono downmix combines multiple audio channels into one while avoiding clipping. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Noise reduction
Noise reduction estimates unwanted signal components and attenuates them, potentially damaging speech or music. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Music generation
Music generation creates audio from conditioning such as style, lyrics, structure, tempo, or reference material. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Text-to-music
Text-to-music converts a textual style and content description into a temporal music representation and audio. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Lyrics
Lyrics are sung text and often need section and line structure for a music model. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Instrumental mode
Instrumental mode disables vocal conditioning and generates music without an intended voice. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Style description
A style description conditions genre, instrumentation, mood, production, and vocal characteristics. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Song structure
Song structure describes temporal sections such as intro, verse, chorus, bridge, and outro. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Tempo
Tempo is the perceived speed of a piece of music and is commonly expressed in beats per minute. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →BPM
BPM specifies the intended number of musical beats per minute and provides a concrete tempo reference. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Musical key
Musical key describes the tonal center and scale material that organize pitches within a piece. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Duration
Duration is the planned or actual length of an audio result on the timeline. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →ACE-Step
ACE-Step is an open music-generation model that turns text, lyrics, and structure into longer audio pieces. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Language-model backend
A language-model backend creates or interprets text conditioning for downstream audio or music models. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Music checkpoint
A music checkpoint contains learned weights for audio generation and must match the model configuration. Detailed documentation covering architecture, production operations, and troubleshooting within “Audio, transcription, and music generation”.
Open article →Module 27GPU, CUDA, and inference optimizationFundamentals, operations, and troubleshooting for GPU, CUDA, and inference optimization.32 terms
GPU compute
GPU compute uses many parallel execution units for large tensor operations instead of serial CPU execution. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →CUDA
CUDA is NVIDIA's programming and runtime platform for general computation on compatible GPUs. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →CUDA Toolkit
The CUDA Toolkit provides compilers, libraries, headers, and diagnostic tools for CUDA applications. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →CUDA driver
The CUDA-capable NVIDIA driver connects user libraries to the GPU and kernel and limits supported runtime versions. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Compute capability
Compute capability identifies the hardware features and instructions supported by an NVIDIA GPU. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →NVIDIA Container Toolkit
The NVIDIA Container Toolkit injects driver libraries and GPU devices into Linux containers in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →NVIDIA runtime
The NVIDIA container runtime augments OCI startup with GPU devices and matching driver mounts. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Default runtime
The default runtime is the container runtime used for new containers when none is explicitly selected. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →GPU device
A GPU device is the operating-system-exposed compute unit with its own ID, VRAM, and utilization. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →GPU passthrough
GPU passthrough assigns a physical GPU device or selected functions to a VM or container. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →NVIDIA_VISIBLE_DEVICES
NVIDIA_VISIBLE_DEVICES filters which GPU IDs an NVIDIA container runtime exposes inside a container. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →CUDA out of memory
CUDA out of memory means a GPU memory allocation could not be satisfied from available VRAM. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →VRAM fragmentation
VRAM fragmentation splits free memory into blocks too small for a large contiguous allocation. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Model offloading
Model offloading moves model components not needed concurrently from VRAM to RAM or storage. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →CPU offloading
CPU offloading keeps selected weights or operations in system memory, reducing VRAM use at a speed cost. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →VAE offloading
VAE offloading moves the VAE encoder or decoder to CPU when not needed alongside the main model. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Attention slicing
Attention slicing computes attention in smaller chunks to reduce peak VRAM consumption. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Memory-efficient attention
Memory-efficient attention avoids fully materializing large attention matrices. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →FlashAttention
FlashAttention is an IO-aware attention kernel that reduces memory traffic and accelerates exact attention. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →xFormers
xFormers is a library of optimized transformer components including memory-efficient attention kernels. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Mixed precision
Mixed precision combines data types of different widths to use tensor cores and memory more efficiently. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →FP32
FP32 is 32-bit floating point with high range and precision but high memory and bandwidth demand. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →FP16
FP16 is 16-bit floating point with low memory use but a narrower numeric range than FP32. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →BF16
BF16 keeps FP32's exponent range but uses fewer mantissa bits and therefore less precision. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →INT8
INT8 represents quantized values with eight integer bits and requires calibration or suitable scales. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →INT4
INT4 represents quantized values with four bits, greatly saving memory at the cost of higher quantization error. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Quantization error
Quantization error is the difference between an original value and its discrete low-bit representation. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Tensor Core
A tensor core is a specialized GPU unit for fast matrix multiplication in supported data types. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Batch size
Batch size is the number of examples processed together and affects VRAM, latency, and throughput. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Inference latency
Inference latency is the time from a complete input to an available model output. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Throughput
Throughput measures how many examples, tokens, or frames a system processes per unit time. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →GPU utilization
GPU utilization reports the share of time compute units are active, not the amount of allocated VRAM. Detailed documentation covering architecture, production operations, and troubleshooting within “GPU, CUDA, and inference optimization”.
Open article →Module 28Application securityFundamentals, operations, and troubleshooting for Application security.32 terms
Threat model
A threat model documents assets, attackers, trust boundaries, and realistic attack paths for a system. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Attack surface
Attack surface comprises every publicly or internally reachable input, service, account, and dependency. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Security boundary
A security boundary marks a transition where data, identities, or privileges must be validated again. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Defense in depth
Defense in depth combines independent safeguards so one failed control does not immediately compromise the whole system. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Secret management
Secret management creates, stores, distributes, and revokes credentials outside source code and images. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Secret rotation
Secret rotation replaces credentials in a controlled sequence, updates consumers, and then revokes the old value. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Credential leak
A credential leak exposes a password, token, or key through logs, code, image layers, or output. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Input validation
Input validation accepts only data with the expected structure, length, type, and value range. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Output encoding
Output encoding escapes data for its specific output context such as HTML, URL, or JavaScript. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →SQL injection
SQL injection inserts untrusted input into database commands; parameterized queries separate data from SQL code. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Command injection
Command injection executes user input as part of a shell command; fixed argument arrays avoid interpretation. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Path traversal
Path traversal uses path components such as dot-dot to escape an allowed base directory. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Cross-site scripting
Cross-site scripting injects untrusted content into a page as active browser code. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Server-side request forgery
SSRF makes a server fetch attacker-selected internal or external destinations. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Unsafe file upload
Unsafe file upload accepts content, size, names, or formats without sufficient validation and isolation. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →MIME sniffing
MIME sniffing lets clients guess content type and may interpret uploaded data as active content. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Zip bomb
A zip bomb is a highly compressed archive that consumes extreme storage or compute when expanded. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Malware scan
A malware scan checks files or behavior against signatures and heuristics but cannot guarantee safety. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Rate limiting
Rate limiting caps actions per identity, IP, or token within a time window. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Abuse prevention
Abuse prevention combines quotas, reputation, anomaly detection, and moderation against misuse. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Denial of service
Denial of service deliberately exhausts a service's bandwidth, connections, CPU, GPU, RAM, or storage. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Content Security Policy
Content Security Policy uses an HTTP header to restrict the sources from which a browser may load scripts and other resources. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →CORS policy
A CORS policy decides which foreign browser origins may read an API's responses. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →TLS termination
TLS termination decrypts HTTPS at a designated proxy and forwards the request under controlled conditions. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Reverse-proxy trust
Reverse-proxy trust defines which proxies may supply forwarded client-IP and protocol headers. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Security header
A security header controls browser protections such as framing, MIME handling, transport, or referrer disclosure. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Audit log
An audit log records security-relevant actions with time, actor, target, and outcome for accountability. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Data protection
Data protection safeguards personal data through legal basis, purpose limitation, access control, and secure processing. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Data minimization
Data minimization collects and retains only data genuinely required for the stated purpose. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Deletion policy
A deletion policy defines triggers, deadlines, scope, and verifiable execution of data deletion. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Security update (Application security)
A security update fixes a known vulnerability in software, an image, a library, or firmware. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Vulnerability management
Vulnerability management inventories components, assesses findings, prioritizes risk, and tracks remediation. Detailed documentation covering architecture, production operations, and troubleshooting within “Application security”.
Open article →Module 29Reliability and capacity planningFundamentals, operations, and troubleshooting for Reliability and capacity planning.32 terms
Service-level indicator
A service-level indicator is a measured value such as success rate or latency that represents user experience. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Service-level objective
A service-level objective sets the target range for an SLI over a period. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Service-level agreement
A service-level agreement is a contractual promise with defined measurement rules and possible consequences for failure. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Error budget
An error budget is the tolerable amount of failure or unavailable time derived from an SLO. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Capacity planning
Capacity planning forecasts load and sizes compute, storage, networking, and headroom. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Resource profile
A resource profile measures a workload's typical and peak CPU, RAM, GPU, disk, and network use. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →CPU limit
A CPU limit caps processor time available to a container and may throttle it when reached. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Memory limit
A memory limit caps RAM for a process or container; exceeding it may trigger an OOM termination. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →GPU limit
A GPU limit restricts device access or planned GPU capacity but is not supported uniformly by every orchestrator. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Disk limit
A disk limit caps occupied storage or reserves free space for safe operation. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Upload quota
An upload quota caps the number or total size of files uploaded per user or period. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Daily quota
A daily quota caps usage during one calendar day and resets its counter at a defined time and timezone. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Concurrency
Concurrency means multiple tasks are in progress at once even if they do not compute in parallel. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Parallelism
Parallelism executes multiple operations simultaneously on different compute units. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Job serialization
Job serialization runs resource-intensive jobs one after another to avoid load spikes. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Queue position
Queue position is the number of jobs scheduled ahead of one job and may change due to priorities. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Wait time
Wait time measures the interval between job acceptance and processing start. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Processing speed
Processing speed relates completed data volume or work units to elapsed time for a defined workload. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Autoscaling
Autoscaling changes instance count or resources automatically from measured load and defined bounds. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Vertical scaling
Vertical scaling assigns more or less CPU, RAM, or GPU to an existing instance. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Horizontal scaling
Horizontal scaling changes the number of equivalent instances and requires shareable state. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Load shedding
Load shedding deliberately rejects lower-priority work before overload harms every request. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Circuit breaker
A circuit breaker temporarily stops calls to a failing dependency and later probes for recovery. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Retry budget
A retry budget caps extra attempts so failures are not amplified by a retry storm. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Exponential backoff
Exponential backoff increases delay between retries and is usually combined with random jitter. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Timeout budget
A timeout budget divides maximum end-to-end time among internal calls and processing. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Graceful shutdown
Graceful shutdown stops accepting new work, finishes in-flight tasks, and releases resources cleanly. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Health dependency
A health dependency is an external component whose state affects a service's readiness. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Single point of failure
A single point of failure is one component whose failure stops the entire service. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →High availability
High availability uses redundancy and automatic failover to survive individual failures. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Disaster recovery
Disaster recovery restores data and services from tested backups after a major failure. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Recovery time objective
Recovery time objective is the maximum acceptable time to restore a service. Detailed documentation covering architecture, production operations, and troubleshooting within “Reliability and capacity planning”.
Open article →Module 30Builds, tests, and releasesFundamentals, operations, and troubleshooting for Builds, tests, and releases.32 terms
Source code
Source code is the human-readable instruction from which a build creates executable or distributable artifacts. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Version control
Version control records traceable file changes and enables comparison, collaboration, and restoration. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Git
Git is a distributed version-control system that stores content as immutable objects and commits. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Repository (Builds, tests, and releases)
A repository contains the version history, references, and working data of a bounded project. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Commit (Builds, tests, and releases)
A commit is an immutable snapshot with a parent reference, author information, and message. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Branch
A branch is a movable name for a line of commits and enables parallel development. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Tag
A Git tag is a stable reference to a particular commit, commonly used for releases. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Merge
A merge combines changes from two commit lines and requires conflict resolution for overlapping edits. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Release
A release is a named, verified bundle of version, artifacts, changes, and notes. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Semantic versioning
Semantic versioning labels incompatible, compatible, and corrective changes as major, minor, and patch. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Changelog
A changelog summarizes user-relevant changes between released versions in a structured form. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Build
A build reproducibly transforms defined sources and dependencies into a distributable artifact. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Reproducible build
A reproducible build creates a bit-identical or verifiably equivalent result from identical sources and tool versions. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Multi-stage build
A multi-stage build separates compilation tools from a lean runtime image and copies only required artifacts. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Build cache
A build cache reuses unchanged intermediate results and invalidates them based on inputs. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →.dockerignore
A .dockerignore file excludes local files from the Docker build context. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Dependency lockfile
A dependency lockfile pins exact resolved versions and integrity values for repeatable installations. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Unit test
A unit test checks a small function or class in isolation with controlled inputs and outputs. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →API test
An API test sends defined requests and checks status, headers, schema, and business response. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →End-to-end test
An end-to-end test exercises a complete user flow across real integrated components. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Browser test
A browser test drives a browser engine and checks DOM, interaction, navigation, and visible states. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Fixture
A fixture is controlled starting data or system state used reproducibly by a test. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Mock
A mock replaces a dependency and specifies expected calls or controlled responses. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Test coverage
Test coverage measures which code paths a test run executes but does not prove correctness. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Linter
A linter statically detects rule violations, suspicious patterns, and common source-code errors. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Formatter
A formatter deterministically rewrites source code into an agreed style. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Static analysis
Static analysis examines code without execution for type errors, data flows, vulnerabilities, or rule violations. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Continuous integration
Continuous integration automatically builds and tests every change in a clean environment. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Continuous delivery
Continuous delivery automatically prepares verified artifacts while keeping production release controllable. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Deployment artifact
A deployment artifact is the immutable, versioned package rolled out to a target environment. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Checksum manifest
A checksum manifest lists files and cryptographic hashes to verify transfer and content. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Staging
Staging is a production-like environment for integration and release tests without real production data. Detailed documentation covering architecture, production operations, and troubleshooting within “Builds, tests, and releases”.
Open article →Module 31Incident analysis and recoveryFundamentals, operations, and troubleshooting for Incident analysis and recovery.32 terms
Incident
An incident is an unplanned disruption affecting a service's security, availability, or quality. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Incident severity
Incident severity classifies impact and urgency using predefined criteria. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Initial response
Initial response acknowledges the incident, preserves evidence, limits harm, and assigns ownership. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Triage
Triage prioritizes symptoms, affected users, and likely failure domains for the first checks. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Affected service
An affected service is the component whose observable behavior differs from its expected state. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Blast radius
Blast radius describes how many users, data sets, and dependent systems an incident reaches. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Incident timeline
An incident timeline orders changes, alerts, symptoms, and actions chronologically with their time source. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Known change
A known change is a documented modification shortly before the symptom and therefore a testable hypothesis. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Service inspect (Incident analysis and recovery)
Service inspect shows a service's desired orchestrator specification including image, mounts, and environment. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Task history
Task history shows current and previous instances of an orchestrated service with states and errors. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Container inspect
Container inspect returns a container's actual runtime state as structured metadata. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Container exit code
Container exit code is the main process's numeric return value and helps distinguish startup, signal, and application failures. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →OOMKilled
OOMKilled means the kernel or runtime terminated a process because of memory pressure. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Health-check failure
A health-check failure occurs when the configured probe command does not respond successfully in time. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Restart loop
A restart loop occurs when a service repeatedly starts, fails, and is restarted by policy. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Image pull failure
An image-pull failure blocks startup because registry, reference, authorization, network, or platform is incompatible. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Bind-mount failure
A bind-mount failure occurs when host path, type, permissions, or node placement does not match the specification. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Permission denied
Permission denied means file mode, owner, security profile, or process identity forbids an operation. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Connection refused
Connection refused means the target is reachable but no listener accepts the connection on the addressed port. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →DNS failure
A DNS failure prevents resolving a name to the address needed for a connection. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →TLS failure
A TLS failure occurs in certificate validation, hostname, protocol version, cipher, or trust chain. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →HTTP 502
HTTP 502 means a gateway did not receive a valid response from its upstream. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →HTTP 503
HTTP 503 means a service is temporarily unready or unavailable due to overload. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →HTTP 504
HTTP 504 means a gateway did not receive an upstream response within its timeout. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Queue stall
A queue stall occurs when waiting jobs grow but no worker successfully claims or completes them. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Worker crash
A worker crash unexpectedly terminates the processing process during or before a job. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Database connection failure
A database connection failure results from wrong addressing, authentication, TLS, pool exhaustion, or an unready server. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Disk full
Disk full means the filesystem or inode pool cannot accept more writes. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →GPU out of memory
GPU out of memory means weights, activations, and buffers exceed available VRAM. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Rollback (Incident analysis and recovery)
A rollback restores the last known working artifact, configuration, and schema version. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Service recovery
Service recovery returns a disrupted service to a verified stable state in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Postmortem
A postmortem documents impact, timeline, causes, and concrete improvements without blame. Detailed documentation covering architecture, production operations, and troubleshooting within “Incident analysis and recovery”.
Open article →Module 32Maintenance, updates, and governanceFundamentals, operations, and troubleshooting for Maintenance, updates, and governance.32 terms
Maintenance window
A maintenance window is an announced period for changes with a defined start, end, and abort point. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Inventory
An inventory lists operated hardware, software, versions, owners, and lifecycle status. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Service catalog
A service catalog documents each service's purpose, owner, dependencies, interfaces, and operational requirements. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Dependency map
A dependency map shows directed relationships among services, databases, networks, and external components. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Configuration baseline
A configuration baseline is the verified reference state against which later changes are compared. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Desired configuration
Desired configuration declaratively describes the state that automation or operations should establish. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Configuration drift
Configuration drift is an unintended difference between actual state and versioned desired configuration. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Version check
A version check determines installed and available versions together with channel and support status. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Release notes
Release notes describe a version's changes, fixes, known issues, and upgrade guidance. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Breaking change
A breaking change makes previously valid interfaces, configurations, or data incompatible without adaptation. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Deprecation
Deprecation announces future removal of an available feature and identifies a replacement path. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Compatibility matrix
A compatibility matrix records tested combinations of software, driver, model, and platform versions. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Migration plan
A migration plan defines sequence, owners, checks, data paths, downtime, and rollback. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Data migration
A data migration copies or transforms data between locations, formats, or systems with integrity checks. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Schema migration
A schema migration changes database tables, fields, indexes, or constraints in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Model upgrade
A model upgrade replaces weights or architecture and requires quality, resource, and workflow tests. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Driver upgrade
A driver upgrade replaces the hardware-facing software layer and must keep kernel, runtime, and applications compatible. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Image upgrade
An image upgrade deploys a new immutable container image instead of modifying a running container. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Canary deployment
A canary deployment sends a small fraction of traffic to a new version first and compares signals. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Blue-green deployment
Blue-green deployment runs old and new environments in parallel and switches traffic in a controlled way. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Pre-upgrade backup
A pre-upgrade backup preserves all non-reproducible data and recovery metadata before a change. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Post-upgrade validation
Post-upgrade validation repeats defined functional, data, and performance checks after a change. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Rollback point
A rollback point is the uniquely named state to which artifacts, configuration, and data can return. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →License review
License review checks rights, obligations, and incompatibilities in software, model, and content licenses. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Open-source license
An open-source license grants use, inspection, modification, and redistribution under defined conditions. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Data retention
Data retention defines which data is stored, for what reason, and for how long. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Deletion request
A deletion request is a traceable demand to locate and remove affected personal data. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Responsibility
Responsibility assigns an accountable role for operations, release, security, and incident response. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Operations documentation
Operations documentation covers architecture, dependencies, routines, thresholds, and recovery procedures. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Runbook
A runbook is a step-by-step, verifiable procedure for a recurring operational or incident scenario. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Standard operating procedure
A standard operating procedure defines mandatory steps, roles, evidence, and approvals for a routine process. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →Technical debt
Technical debt is intentionally or unintentionally deferred quality work that makes later changes more expensive. Detailed documentation covering architecture, production operations, and troubleshooting within “Maintenance, updates, and governance”.
Open article →No matching terms found.