API — application programming interface
- API
- Application Programming Interface
A contract through which one program uses another: operations, data and errors. APIs need not use HTTP; a library interface is also an API.
KNOWLEDGE AT HAND
551 concepts from programming, backend development and GitOps. Definitions, acronym expansions and references — no account required.
Results: 551
A contract through which one program uses another: operations, data and errors. APIs need not use HTTP; a library interface is also an API.
Application Performance Monitoring: analysis of transactions, latency, errors and dependencies. Products may collect data through an agent but still need configuration, access control and interpretation.
Source documentation ↗An AWS service distributing application traffic such as HTTP among targets. Listeners, health checks and routing rules determine whether requests reach the right application.
Generates Applications from parameters and generators. Helps manage multiple environments, but a generator mistake can have a wide impact; control deletion and permissions.
Source documentation ↗A short record of a problem, constraints, alternatives, decision and consequences. It explains why a solution was chosen and when to revisit it.
A GitOps controller comparing Git declarations with cluster resources. Self-healing can revert manual changes, so pause procedures must account for reconciliation.
Binds a declaration source, target cluster/namespace and synchronization policy. Sync and health are different assessments; neither alone proves a business flow.
Source documentation ↗Constrains Argo CD application repositories, destinations and resource kinds. It does not replace Kubernetes RBAC or database permissions.
Source documentation ↗A product name or identifier; no acronym expansion is invented.
A 64-bit ARM processor architecture. An amd64 image is not automatically an arm64 image; verify the platform and native dependencies.
Source documentation ↗Information about the inputs, process and tools that produced an artifact. Its reliability depends on trust in the producer and verification mechanism.
A broad family of techniques for tasks such as pattern recognition or content generation. LLMs are one approach, not a synonym for all AI.
Laravel command interface. Commands may diagnose, generate code or change data; inspect help and choose the right environment.
Source documentation ↗Syntax for organizing code around asynchronous operations. It does not promise parallel execution; design cancellation, timeouts and limits for the runtime.
A Python application/server interface supporting HTTP and WebSocket events. Using ASGI does not fix blocking I/O inside async def.
Source documentation ↗A delivery model allowing repeats to reduce message loss under the system’s assumptions. Recipients must handle duplicates safely.
Checking who a client or service is. Establishing identity does not yet determine which operations and data that identity may access.
Deciding whether an identity may perform a particular operation on a particular resource. Enforce it server-side even when the resource identifier is known.
A distinct infrastructure location within a cloud region used in resilience design. Spreading replicas across zones alone does not ensure data consistency or correct failover.
A datetime carrying information that determines its UTC offset. It need not include a named timezone with full rules. For Python elapsed duration across DST, convert both endpoints to UTC; subtraction with the same timezone can measure wall-clock time.
Source documentation ↗A cloud-services platform for compute, networking and databases, among other uses. Establish account, region, permissions, costs and cleanup before creating resources.
An AWS certificate-management service used by supported integrations. Issuance requires domain validation; it does not automatically configure the whole secure traffic path.
Creates and updates AWS resources from a stack template. Change sets preview updates; drift detection finds some divergences. A resource should have one management owner.
Source documentation ↗Records AWS activity and API calls for auditing. Helps identify who changed configuration; it does not replace application business logs or automatically cover every data event.
Source documentation ↗Managed container compute for supported ECS/EKS scenarios. Not managing nodes does not remove responsibility for images, permissions or data.
Source documentation ↗Manages cryptographic keys and operations using them. Permission to read an encrypted object and permission to decrypt using a key are separate access concerns.
Source documentation ↗Function execution without managing the execution server. Invocations may be retried depending on the event source; control idempotency, time and concurrency. Distinct from a language lambda expression.
Source documentation ↗Stores secrets and supports rotation. Applications need least privilege and a refresh strategy; changing a secret does not immediately update existing connections.
Source documentation ↗Orchestrates workflow steps as state machines. Retries and error handling do not automatically undo external effects; design idempotency and compensation.
Source documentation ↗Resource management and operations tools. Parameter Store holds configuration parameters; operational access through Session Manager should not mean permanent keys and unrestricted SSH.
Source documentation ↗Application-traffic filtering rules before supported entry points. They do not replace code validation/authorization or protect every network path.
Source documentation ↗