Source
book_cube post
A practical review of architecture frameworks from AWS, Azure, and Google Cloud.
AWS, Microsoft, and Google all maintain mature architecture frameworks to assess solutions before and after production rollout. This chapter provides a practical map: what these materials cover, where they align, and how to turn them into a recurring architecture improvement process.
Framework tabs
Each framework is placed in its own tab. Switching tabs reveals a full-width description, polygon visualization, and pillar-by-pillar details for that specific provider.
AWS Well-Architected Framework
6 pillars
AWS provides an end-to-end architecture review model that spans operations, security, reliability, performance, cost, and sustainability. It works well as a recurring production checklist.
Core framework pillars
- 1. Operational excellence: Operations, monitoring, incident response, and continuous improvement.
- 2. Security: Data/system protection, IAM, threat detection, and response.
- 3. Reliability: Failure tolerance and predictable recovery behavior.
- 4. Performance efficiency: Efficient resource selection for real workload patterns.
- 5. Cost optimization: Reducing waste while preserving target service quality.
- 6. Sustainability: Lowering energy footprint and environmental impact.
Axis comparison across frameworks
A dedicated comparison component highlights which axes are common across providers and which ones are explicitly separated only in selected frameworks.
| Axis | What this axis covers | AWS | Azure | Google Cloud |
|---|---|---|---|---|
| Operational excellence | Operations, monitoring, runbooks, and continuous improvement. | Operational excellence | Operational excellence | Operational excellence |
| Security | Protection of data, access boundaries, and infrastructure. | Security | Security | Security (inside a combined pillar) |
| Privacy & compliance | Privacy controls and regulatory alignment. | Not split into a dedicated pillar | Not split into a dedicated pillar | Security, privacy, and compliance |
| Reliability | Resilience and recovery under failures. | Reliability | Reliability | Reliability |
| Performance | Performance efficiency, scaling, and capacity behavior. | Performance efficiency | Performance efficiency | Performance optimization |
| Cost optimization | Spend control and business-value efficiency. | Cost optimization | Cost optimization | Cost optimization |
| Sustainability | Energy footprint and environmental impact. | Sustainability | Not split into a dedicated pillar | Not split into a dedicated pillar |
Shared focus and key differences
- All three frameworks converge on the same core axes: reliability, security, cost, performance, and operations.
- Terminology and depth differ, but the underlying engineering questions are nearly identical.
- Many cloud-oriented practices can be directly applied in on-prem environments.
- These frameworks work well as architecture review checklists and as a shared language across teams.
How to apply this in a team
Build an architectural baseline: system context, critical workloads, SLO/SLA targets, and constraints.
Run pillar-based reviews: capture risks, owners, expected impact, and priority.
Create an improvement backlog: quick wins (up to 2 weeks), mid-term initiatives, and platform epics.
Repeat the cycle regularly (quarterly or before major releases).
Example: from research to framework practice
A clear example of provider guidance rooted in research is Deployment archetypes in the Google Cloud Architecture Framework, which maps to the paper Deployment Archetypes for Cloud Applications.
There is also a practical breakdown of this paper in tellmeabout.tech, which is a good bridge from concept to implementation patterns.
What matters most for leaders and architects
DevEx and engineering tooling directly affect delivery speed and predictability.
Operational discipline and architecture reviews should be continuous, not one-off efforts.
Open-core/open-source strategy can strengthen a commercial product when value balance is maintained.
User trust matters more than a theoretically perfect business model and requires transparent course correction.
Even strong products must adapt quickly to new waves, including AI in the SDLC.
Related chapters
- Why know Cloud Native and 12 factors - Section context: why provider architecture frameworks are foundational for cloud-native system design.
- Infrastructure as Code - Well-architected operational discipline becomes executable through IaC and repeatable delivery workflows.
- Cost Optimization & FinOps - Connects framework cost pillars to FinOps practices and architecture-level cost control decisions.
- Multi-region / Global Systems - Reliability pillar in practice: resilience engineering, regional trade-offs, and global availability patterns.
- Service Mesh Architecture - Operational traffic and policy management patterns for service-to-service communication in distributed systems.
- Data Governance & Compliance - Security and compliance perspectives from provider frameworks for data, access control, and regulation.