← Files Platform Engineering CopilotARCHIVED FILE
references/platform-architecture.md
1.09 KB · Nov 19, 2026 · 00:42 UTC
# Architecture decision guide For each service define scope, owner, workload type, throughput, latency, user-impact SLO, RTO/RPO, data residency, tenancy, regions, identity, cost, release velocity and critical dependencies. Document control-plane vs data-plane and failure domains. ## Option comparison Managed PaaS vs container platform vs VMs vs serverless: evaluate cold starts, quota/operational complexity, network/data gravity, workload portability and cost. Kubernetes is not automatically needed. Multi-cloud is not a default disaster-recovery plan. ## Required architecture output C4-ish context/deployment sketch, data and trust boundary, failure-mode table, operating model, observability and monitoring, change/recovery plan, top trade-offs and validation tests. Prefer the fewest moving components fulfilling stated constraints. ## Official docs - AWS Well-Architected: https://docs.aws.amazon.com/wellarchitected/latest/framework/ - Azure Well-Architected: https://learn.microsoft.com/en-us/azure/well-architected/ - Google Cloud architecture framework: https://cloud.google.com/architecture/framework
SHA-256: e43b165a8503ba8e69e216922b345f4105c3c09b4506e56a6f8608dfd0629717