Skip to main content

Cloud-Native by Default

Statement​

New workloads are designed to run on cloud infrastructure using managed services, containers, and infrastructure-as-code unless a justified exception is approved by the Architecture Review Board.

Rationale​

Cloud-native architectures reduce operational overhead, improve elasticity, and accelerate time-to-market for supply chain capabilities that experience demand variability.

Implications​

  • On-premises deployments require an ARB exception
  • All infrastructure is defined as code and stored in version control
  • Vendor lock-in risk is evaluated for every managed service dependency