File path interpreted relative to another location.

Restricting the frequency of operations or requests.

Database copy used primarily for read operations.

Ease with which source code can be understood.

Collection of related data fields.

Function calling itself directly or indirectly.

In-memory data store often used for caching and messaging.

Version of software made available to users.

Version considered ready for release if no critical problems remain.

Planning and controlling software releases.

Mechanism allowing software to invoke operations on another system.

Pattern abstracting data-access operations.

Desired capability or constraint of software.

Something software can access or consume.

Resource acquired but not properly released.

Time taken to return a response to a request.

Attempting a failed operation again.

Rules controlling when and how failed operations are retried.

Proxy receiving client requests and forwarding them to backend services.

Authorization based on assigned user roles.

Reverting software or data to an earlier state.

Gradually replacing instances with a new software version.

Determining where requests or data should be sent.

Remote Procedure Call mechanism.

Timing-dependent interaction between concurrent operations.

Programming style centered on asynchronous data streams and events.

Data representation optimized for reading.

System required to respond within defined time constraints.

Lock applied to a specific database record.

Function that invokes itself.

Duplicate resources used to improve reliability.

Runtime inspection or manipulation of program structures.

Delay between primary data and replicated copies.

Data included in an HTTP request payload.

Metadata sent with an HTTP request.

Assignment of resources to software operations.

Value uniquely identifying a resource.