---
# System prepended metadata

title: Well Architecture

---

# Well-Architecture 

[AWS The pillars of the framework](https://aws.amazon.com/tw/architecture/well-architected)
* **Operational excellence**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html)
        * Perform operations as code
        * Make frequent, small, reversible changes
        * Refine operations procedures frequently
        * Anticipate failure
        * Learn from all operational failures
        * Use managed services
        * Implement observability for actionable insights
* **Security**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html)
        * Implement a strong identity foundation
        * Maintain traceability
        * Apply security at all layers
        * Automate security best practices
        * Protect data in transit and at rest
        * Keep people away from data
        * Prepare for security events
* **Reliability**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html)
        * Automatically recover from failure
        * Test recovery procedure
        * Scale horizontally to increase aggregate workload availability
        * Stop guessing capacity
        * Manage change in automation
* **Performance efficiency**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/perf-dp.html)
        * Democratize advanced technologies
        * Go global in minutes
        * Use serverless architectures
        * Experiment more often
        * Consider mechanical sympathy
* **Cost optimization**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html)
        * Implement Cloud Financial Management
        * Adopt a consumption model
        * Measure overall efficiency
        * Stop spending money on undifferentiated heavy lifting
        * Analyze and attribute expenditure
* **Sustainability**
    * [Design principles](https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html)
        * Understand your impact
        * Establish sustainability goals
        * Maximize utilization
        * Anticipate and adopt new, more efficient hardware and software offerings
        * Use managed services
        * Reduce the downstream impact of your cloud workloads

==============================================================

[Google Cloud Architecture Framework](https://cloud.google.com/architecture/framework)
* [**System design**](https://cloud.google.com/architecture/framework/system-design)
    * Apply core principles of system design.
    * Select geographic regions to support your business applications.
    * Manage cloud resources.
    * Choose and manage compute.
    * Design your network infrastructure.
    * Select and implement a storage strategy.
    * Optimize your database.
    * Analyze your data.
    * Implement machine learning.
    * Design your cloud workloads for sustainability.
* [**Operational excellence**](https://cloud.google.com/architecture/framework/operational-excellence)
    * Automate your deployments
    * Set up monitoring, alerting, and logging
    * Establish cloud support and escalation processes
    * Manage capacity and quota
    * Plan for peak traffic and launch events
    * Create a culture of automation
* [**Security, privacy, and compliance**](https://cloud.google.com/architecture/framework/security)
    * Review shared responsibility and shared fate on Google Cloud
    * Understand security principles
    * Manage risks with controls
    * Manage your assets
    * Manage identity and access
    * Implement compute and container security
    * Secure your network
    * Implement data security
    * Deploy applications security
    * Manage compliance obligations
    * Implement data residency and sovereignty requirements
    * Implement privacy requirements
    * Implement logging and detective controls
* **Reliability**
    * [Design and operational principles]( https://cloud.google.com/architecture/framework/reliability/principles#design_and_operational_principles)
        * Define your reliability goals
        * Build observability into your infrastructure and applications
        * Design for scale and high availability
        * Create reliable operational processes and tools
        * Build efficient alerts
        * Build a collaborative incident management process

* [**Cost optimization**](https://cloud.google.com/architecture/framework/cost-optimization)
    * Adopt and implement FinOps
    * Monitor and control cost
    * Optimize cost: Compute, containers, and serverless
    * Optimize cost: Storage
    * Optimize cost: Databases and smart analytics
    * Optimize cost: Networking
    * Optimize cost: Cloud operations
* [**Performance optimization**](https://cloud.google.com/architecture/framework/performance-optimization)
    * Implement the performance optimization process.
    * Monitor and analyze performance.
    * Optimize compute performance.
    * Optimize storage performance.
    * Optimize networking performance.
    * Optimize database performance.
    * Optimize analytics performance.