Command
Represents a request to perform an operation as an object or function. Unlike an event it expresses intent, not fact; it provides neither durable queuing nor safe undo by itself.
KNOWLEDGE AT HAND
551 concepts from programming, backend development and GitOps. Definitions, acronym expansions and references — no account required.
Results: 551
Represents a request to perform an operation as an object or function. Unlike an event it expresses intent, not fact; it provides neither durable queuing nor safe undo by itself.
A named auxiliary query in WITH, used by a larger SQL query. It helps structure queries; do not assume automatic materialization or faster execution. Inspect the execution plan.
Source documentation ↗An identifier for a publicly described vulnerability. Assess whether the component and exploitation conditions exist in your deployment; the identifier alone does not describe all risk.
PHP dependency manager: composer.json declares requirements and composer.lock pins resolved installation versions.
Source documentation ↗Provides a shared contract for individual elements and groups. Define group-operation meaning and whole-tree traversal cost.
Building behaviour from smaller collaborating parts. It allows dependency changes without extending inheritance hierarchies, but needs clear collaboration contracts.
Multiple tasks make progress over overlapping periods. They need not execute physically at the same instant; results may depend on interleaving.
Nonsecret Kubernetes configuration. Changing the object does not mean the application has read the new value; behavior depends on injection and refresh mechanisms.
Source documentation ↗Data governing how an application runs in an environment. Validate required settings at startup; configuration should not hold current-customer state or repository-stored secrets.
A bounded set of connections reused by operations. When all are busy, new tasks wait or fail; more threads do not increase database capacity.
A distributed-systems result: during a network partition, linearizable consistency and a response to every request at a functioning node cannot both be guaranteed. This concerns behavior during a partition, not an arbitrary choose-two-of-three rule.
Source documentation ↗Testable client assumptions about a provider. A test should preserve old-client behaviour rather than updating both sides together and hiding incompatibility.
A process or process group running with isolation and resource controls. A container is not automatically a strong security boundary and usually shares the host kernel.
A layered artifact containing a filesystem and startup metadata. Removing a secret in a later layer does not remove it from earlier image layers.
A service storing and distributing container images. Git source access need not grant image access; the pulling identity needs separate authorization.
A distributed network delivering and often caching content near users. Incorrect cache rules can expose private responses.
Source documentation ↗A browser policy restricting script and resource sources. It is an additional defense, not a replacement for HTML sanitization or authorization.
Source documentation ↗A mechanism wrapping work with resource setup and cleanup, including on exceptions, such as Python with open.
CI integrates changes with checks. Continuous delivery keeps software releasable; continuous deployment automatically deploys changes meeting criteria. Explicitly identify the production-promotion decision.
Frequent integration backed by automated build and test checks. A green pipeline proves only the checks performed, not complete production readiness.
Components managing cluster state: API, scheduling and controllers. Workers run workloads. API unavailability is not the same as immediate termination of running containers.
Source documentation ↗An execution unit that can suspend and resume. Scheduling depends on the runtime; suspension does not automatically move blocking I/O onto a suitable thread.
A browser mechanism governing whether script from another origin may read a response. It is not API authorization and does not block every non-browser client.
The knowledge and assumptions one module has about another. Access to adapter internals makes adapter changes affect clients.
The processor executing program instructions. Analyze CPU load with response time and container limits; a low percentage does not rule out waiting on other resources.
A lock limiting parallel bytecode execution in CPython builds that use it. Free-threaded builds also exist; do not assign identical constraints to every Python configuration.
Source documentation ↗Separating the write model from the read model. It can operate in one process and database; separate projections introduce synchronization and rebuilding costs.
Defines a new Kubernetes resource type. A schema alone does not execute behavior; a controller commonly processes instances of that type.
Source documentation ↗Basic data creation, reading, updating and deletion operations. Business models often need richer operations and rules than exposing tables directly through HTTP.
A deterministic digest used for purposes such as integrity checks. A hash alone neither authenticates the author nor encrypts data; anyone knowing the input can compute it.