Parent folderOpen Confluence

RWS Architecture article

Serverless

Serverless is the product-neutral architecture building block for event-driven and function-style workload execution. It states what DC 3.0 needs from this capability before a conc

  1. Typeabb
  2. Statuscandidate
  3. Domainplatform
On this page
  1. ABB Serverless
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Serverless

Summary

Serverless is the product-neutral architecture building block for event-driven and function-style workload execution. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides event-driven and function-style workload execution.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the datacenters ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Serverless workloads must define runtime limits, event sources, identity, observability, and data handling.
  • SBBs must avoid hidden platform dependencies that prevent portability or operational support.

Service Description

This ABB offers a serverless service that lets teams run event-driven functions or short-lived services without managing the underlying runtime lifecycle. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Serverless.
  • MVP: identify candidate SBBs and connect them to the service, support, and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud landing zone in ODC-Amsterdam, following the RWS ICT Strategy 2025-2030 private-cloud direction.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • HTTP, event, queue, and trigger interfaces.
  • Container, identity, secret, and telemetry integrations.
  • Developer workflow and deployment APIs.

Dependencies

  • Depends on clusters-as-a-service for a supporting capability or integration boundary.
  • Depends on automation for a supporting capability or integration boundary.
  • Depends on registry for a supporting capability or integration boundary.
  • No implementing SBB is mapped yet; candidate SBB selection is a dependency for further elaboration.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • No SBB is available yet. Candidate selection must be completed before this ABB can be promoted beyond capability intent.