Parent folderOpen Confluence

RWS Architecture article

DC 3.0 Architecture Structure

DC 3.0 is the project-facing view across the architecture vault. It groups the target architecture into the workstreams used for planning, review, and delivery, while the domain fo

  1. Typeindex
  2. Statusactive
  3. Domain20-architecture
On this page
  1. How to Read This
  2. DC 3.0 Workstreams
  3. Reference Candidates
  4. Architecture Domain Map
  5. Delivery Map
  6. Traceability Rules
  7. Next Steps

DC 3.0 is the project-facing view across the architecture vault. It groups the target architecture into the workstreams used for planning, review, and delivery, while the domain folders keep the deeper design detail.

How to Read This

  1. Use this page to orient on the DC 3.0 project structure.
  2. Follow the domain architecture links for target-state design detail.
  3. Use workpackages for delivery sequencing and acceptance criteria.
  4. Use ABB/SBB notes only as the capability-to-solution traceability layer.

DC 3.0 Workstreams

WorkstreamArchitecture FocusDelivery ScopeKey Building Blocks
Network and Supporting ServicesDatacenter fabric, DDI, DCIM, connectivity, evidencewp-01-dc3-0-network-and-supporting-services, wp-02-dcimdc-network-structure, Backbone Core, dns-dhcp-ipam
Storage and Data ProtectionStorage backend, OpenShift storage integration, backup and recoverywp-04-dc3-0-storage, wp-16-business-continuity-and-disaster-recoveryblock-file-s3-storage, Block Storage, Object Storage, backup-and-disaster-recovery, ceph, cohesity
Trust, Identity, and SecuritySecrets, IAM, hardening, policy and compliance controlswp-03-trust-and-secret-services, wp-06-security-posture-and-hardening, wp-07-identity-and-access-management-iamsecrets-management, smart-access, openbao, keycloak, automation
Platform Services and AutomationGitOps, fleet management, platform automation, service catalog patterns, controlled registrywp-08-platform-services-automation, wp-09-caas-platform, wp-19-developer-hubfleet-management, automation, registry, red-hat-quay, red-hat-advanced-cluster-management, openshift-gitops
Workload ServicesVMaaS, DBaaS, FaaS, WFaaS, migration, service meshwp-11-legacy-workload-migration, wp-12-database-as-a-service-dbaas, wp-13-virtual-machines-as-a-service-vmaas, wp-14-functions-as-a-service-faas, wp-15-workflows-as-a-service-wfaas, wp-18-service-meshServer Virtualization, virtual-machines-as-a-service, openshift-virtualization, service-mesh
AI and Developer AccelerationTransitional OpenShift AI lane, model-assisted delivery, developer accelerationwp-17-devops-acceleration-with-agent-models, wp-21-openshift-ai-dc-a-transitional-production-lanedata-science-and-ai, red-hat-openshift-ai, red-hat-developer-hub
Governance and OrganizationFinOps, governance cadence, operating model, people and organizationwp-10-finops-and-governance, wp-20-people-and-organizationPlatform Architecture, Principles

Reference Candidates

These notes are not yet part of a finalized DC 3.0 workstream, but they preserve candidate capability coverage that needs ownership review.

CandidateReview Focus
IoT GatewayConfirm whether edge gateway capability belongs in DC 3.0 scope or remains separate OT/edge architecture input.
IoT Connectivity LTEConfirm ownership boundary between mobile IoT connectivity and network/DC supporting services.
IoT ManagementConfirm whether IoT management integrates with DCIM, platform operations, or remains a separate management service.

Architecture Domain Map

DomainDC 3.0 RoleStart Here
PlatformShared runtime, OpenShift operating model, automation, and workload servicesPlatform Architecture
NetworkFabric, routing, lane topology, edge/load-balancing, and network validationNetwork Architecture
StorageBackend storage, Kubernetes integration, performance, encryption, and protectionStorage Architecture
SecurityIAM, secrets, hardening, policy, compliance, and audit evidenceSecurity Architecture
AIAI workload lane, OpenShift AI, model hosting, and developer accelerationdata-science-and-ai

Delivery Map

Planning ViewPurpose
Delivery Work PackagesCanonical delivery package list and domain grouping.
workpackage-portfolio-indexPortfolio-level package overview.
workpackage-dependencies-indexDependency and sequencing view.
adr-013-implementation-phasingPhasing decision context for DC 3.0 delivery.

Traceability Rules

  • Architecture notes explain target state and constraints.
  • ADRs record decisions and trade-offs.
  • Workpackages define delivery scope, dependencies, and acceptance criteria.
  • ABB/SBB notes provide capability-to-solution traceability where useful.
  • Legacy publication content is not the DC 3.0 source model; treat legacy wording as reference input only.

Next Steps

  • Keep this page aligned with the lead-architect DC 3.0 structure.
  • Add missing workstream-specific indexes only where a page has enough reusable content.
  • Promote mature workstream decisions into ADRs instead of embedding decisions in this overview.