RWS Architecture article

Functions as a Service (FaaS)

Provide an event-driven functions-as-a-service platform on OpenShift Serverless (Knative).

  1. Typeworkpackage
  2. Statusplanned
  3. Domainopenshift
On this page
  1. WP-14 Functions as a Service (FaaS)
  2. Summary
  3. Scope
  4. Architecture Context
  5. Decision Context
  6. Dependencies
  7. Acceptance Criteria

WP-14 Functions as a Service (FaaS)

Summary

Provide an event-driven functions-as-a-service platform on OpenShift Serverless (Knative).

Scope

  • Deliver serverless function runtime templates and deployment guardrails on OpenShift Serverless.
  • Define supported event source patterns, retry behavior, and dead-letter handling.
  • Set operational boundaries for scaling, latency classes, and tenancy isolation.

Architecture Context

Decision Context

Dependencies

Acceptance Criteria

  • P99 latency targets are defined per function class.
  • Event delivery is reliable with DLQ and retry policies.