Pattern for creating objects through a method.

Switching to a backup system after failure.

Ability to continue operating despite failures.

Configuration controlling feature availability.

Model with finite states and transitions.

Reusable software structure for applications.

Returning service to the original system.

Development branch for a particular feature.

Identifier representing an open file or resource.

Mechanism controlling simultaneous file access.

System organizing and storing files.

System controlling network traffic by rules.

Creating a new process or repository copy.

Design that defaults to a safe state after failure.

Reference used to access an open file.

Correctness and consistency of file contents.

Rule controlling file access.

Protocol for transferring files over networks.

Mechanism selecting or modifying data.

Cleanup mechanism invoked during object lifecycle.

Database field referencing another table's key.

Parallel pattern that splits and later combines tasks.

Older software can handle newer formats.

Release introducing new functionality.

Update to embedded device software.

Switch controlling feature availability.

Runtime mechanism for enabling features.

Behavior that defaults to a safe state.

One-dimensional CSS layout system.

Interactive input element.

Checking submitted form data.

Browser API for network requests.

Proxy acting on behalf of clients.

Mechanism controlling data transmission rate.

Ability to continue despite failures.

Group of components sharing failure risk.

Infrastructure region affected by a failure.