RWS Architecture article

Self-Service Platform

Provide paved-road capabilities so teams can adopt platform services safely without bespoke coordination.

  1. Typeprinciple
  2. Statusactive
  3. Domain60-principles
On this page
  1. Principle – Self-Service Platform
  2. Summary
  3. Intent
  4. Scope and Applicability
  5. Principles
  6. Per-Domain Implementation
  7. OpenShift
  8. Networking
  9. Storage
  10. Security
  11. Platform
  12. AI

Principle – Self-Service Platform

Summary

Provide paved-road capabilities so teams can adopt platform services safely without bespoke coordination.

Intent

Accelerate delivery and reduce cognitive load by offering standardized, supported platform capabilities.

Scope and Applicability

Applies to platform services, developer tooling, and workloads that should scale without manual gatekeeping.

Principles

  • Offer clear, documented service catalogs with defined lifecycle ownership.
  • Default to secure, compliant configurations that teams can consume easily.
  • Prefer reusable platform building blocks over bespoke one-off solutions.

Per-Domain Implementation

OpenShift

  • Publish supported operators, templates, and service tiers for common workloads.

Networking

  • Provide standardized connectivity and ingress/egress patterns as services.

Storage

  • Offer storage classes and protection tiers aligned to workload needs.

Security

  • Provide identity, access, and policy baselines as self-service capabilities.

Platform

  • Maintain consistent onboarding and service-request workflows across domains.

AI

  • Offer self-service golden paths for AI workloads (approved runtimes, model serving, and data access) with clear ownership and guardrails.

Exceptions

Highly specialized workloads may require bespoke integration with explicit architectural approval.