Systems programming language focused on safety.

Component restricting request frequency.

Programming based on asynchronous data streams.

Pattern abstracting data-access operations.

Tool identifying potential data races.

Function safely callable again before previous execution ends.

Copy of data or service state.

Maintaining copies of data across systems.

Component processing incoming requests.

Something consumed or managed by software.

Resource acquired but not properly released.

Conforming to REST architectural principles.

Regulation of data or request rates.

Restoring operation after failure.

Maximum acceptable amount of lost data.

Maximum acceptable restoration time.

Duplication used to improve reliability.

Memory management using object reference counts.

API allowing runtime inspection of program structures.

Delay between primary and replica updates.

Maximum time allowed for a request.

Collection of reusable system resources.

Time taken to produce a response.

Specific URL exposing REST functionality.

Excessive retries overwhelming a service.

Process of releasing a software change.

Environment providing services required during execution.

Build prepared for distribution.

Package required during execution.

Announcement that functionality will disappear.

Package combining multiple updates.

Build considered ready for final release.

Releasing software to successive user groups.

Updating instances progressively.

Replacing all old instances with new ones.

Settings applied while software executes.

Credential used to obtain new access tokens.