TECHNOLOGY

Serverless

For Serverless, we define applicability from the purpose and constraints, including conditions where it should not be used. Avoid locking the design to one model or platform, separate data, integration, and monitoring, and record the reasons for each choice.

Read this page

Item 1 of 1: Serverless

AWS Cloud

Serverless

For Serverless, we define applicability from the purpose and constraints, including conditions where it should not be used. Avoid locking the design to one model or platform, separate data, integration, and monitoring, and record the reasons for each choice.

Scope

For Serverless, we define applicability from the purpose and constraints, including conditions where it should not be used.

  1. Design decisions
  2. Validation
  3. Operational review
  4. Human governance
  5. Related pages

Design decisions

For Serverless, we avoid locking the design to one model or platform, separate data, integration, and monitoring, and record the reasons for each choice.

Validation

For Serverless, we use repeatable inputs and criteria and inspect failure cases as well as expected behavior.

Operational review

For Serverless, we track changes, quality shifts, and use patterns while keeping a path for rollback.

Human governance

For Serverless, we do not leave consequential decisions to automation alone and define accountable review points.

Related pages