Framework de arquitetura bem estruturada: pilar de confiabilidade
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Last reviewed 2024-12-30 UTC
O pilar de confiabilidade no
Google Cloud Well-Architected Framework
fornece princípios e recomendações para ajudar você a projetar, implantar e gerenciar
cargas de trabalho confiáveis em Google Cloud.
Este documento é destinado a arquitetos de nuvem, desenvolvedores, engenheiros de plataforma,
administradores e engenheiros de confiabilidade do site.
A confiabilidade é a capacidade de um sistema realizar consistentemente as funções pretendidas nas condições definidas e manter o serviço ininterrupto. As práticas recomendadas para confiabilidade incluem redundância, design com tolerância a falhas, monitoramento e processos de recuperação automatizados.
Como parte da confiabilidade, a resiliência é a capacidade do sistema de resistir e se recuperar de falhas ou interrupções inesperadas, mantendo o desempenho. Os recursos doGoogle Cloud , como implantações multirregionais, backups automatizados e soluções de recuperação de desastres, podem ajudar a melhorar a resiliência do sistema.
A confiabilidade é importante para sua estratégia de nuvem por vários motivos, incluindo:
Tempo de inatividade mínimo: o tempo de inatividade pode levar à perda de receita, diminuição da produtividade e danos à reputação. As arquiteturas resilientes ajudam a garantir que os sistemas continuem funcionando durante falhas ou se recuperem de maneira eficiente delas.
Experiência do usuário aprimorada: os usuários esperam interações perfeitas com a tecnologia. Sistemas resilientes ajudam a manter a performance e a disponibilidade consistentes, além de oferecer um serviço confiável mesmo durante alta demanda ou problemas inesperados.
Integridade dos dados: falhas podem causar perda ou corrupção de dados.
Sistemas resilientes implementam mecanismos como backups, redundância e replicação para proteger os dados e garantir que eles permaneçam precisos e acessíveis.
Continuidade de negócios: sua empresa depende da tecnologia para operações críticas. Arquiteturas resilientes ajudam a garantir a continuidade após uma falha catastrófica, permitindo que as funções comerciais continuem sem interrupções significativas e oferecendo suporte a uma recuperação rápida.
Compliance: muitos setores têm requisitos regulamentares para disponibilidade do sistema e proteção de dados. As arquiteturas resilientes podem ajudar você a atender a esses padrões, garantindo que os sistemas permaneçam operacionais e seguros.
Redução dos custos de longo prazo: as arquiteturas resilientes exigem investimento inicial, mas a resiliência pode ajudar a reduzir os custos ao longo do tempo, evitando períodos de inatividade caros, correções reativas e permitindo um uso mais eficiente dos recursos.
Mentalidade organizacional
Para tornar seus sistemas confiáveis, você precisa de um plano e uma estratégia estabelecida.
Essa estratégia precisa incluir educação e autoridade para priorizar a confiabilidade junto com outras iniciativas.
Deixe claro que toda a organização é responsável pela confiabilidade, incluindo desenvolvimento, gerenciamento de produtos, operações, engenharia de plataforma e engenharia de confiabilidade do site (SRE).
Até mesmo os grupos focados em negócios, como marketing e vendas, podem influenciar a confiabilidade.
Todas as equipes precisam entender as metas de confiabilidade e os riscos dos aplicativos. As equipes precisam ser responsáveis por esses requisitos. Os conflitos entre confiabilidade e desenvolvimento regular de recursos do produto precisam ser priorizados e escalados de acordo.
As atividades que você realiza para projetar, implantar e gerenciar um sistema confiável podem ser categorizadas nas seguintes áreas de foco. Cada um dos princípios e recomendações de confiabilidade neste pilar é relevante para uma dessas áreas de foco.
Escopo: para entender seu sistema, faça uma análise detalhada da arquitetura dele. É preciso entender os componentes, como eles funcionam e interagem, como os dados e as ações fluem pelo sistema e o que pode dar errado. Identifique possíveis falhas, gargalos e riscos, o que ajuda você a tomar medidas para mitigar esses problemas.
Observação: para evitar falhas no sistema, implemente uma observação e um monitoramento abrangentes e contínuos. Com essa observação, você pode entender tendências e identificar possíveis problemas de forma proativa.
Resposta: para reduzir o impacto das falhas, responda de maneira adequada e recupere com eficiência. As respostas automáticas também podem ajudar a reduzir o impacto das falhas. Mesmo com planejamento e controles, ainda podem ocorrer falhas.
Aprendizado: para evitar que as falhas se repitam, aprenda com cada
experiência e tome as medidas adequadas.
Princípios básicos
As recomendações no pilar de confiabilidade do Well-Architected Framework são mapeadas para os seguintes princípios básicos:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-12-30 UTC."],[[["\u003cp\u003eThe Reliability pillar of the Google Cloud Well-Architected Framework offers guidelines for designing, deploying, and managing reliable workloads, focusing on maintaining consistent performance and uninterrupted service.\u003c/p\u003e\n"],["\u003cp\u003eKey aspects of reliability include resilience, the ability to recover from failures, and best practices such as redundancy, fault-tolerant design, monitoring, and automated recovery processes, all of which are critical for minimizing downtime and maintaining user satisfaction.\u003c/p\u003e\n"],["\u003cp\u003eEstablishing an organizational mindset where every team prioritizes reliability and is accountable for meeting targets is crucial for ensuring system dependability, and planning for reliability should be a holistic effort across the entire organization.\u003c/p\u003e\n"],["\u003cp\u003eThe core principles for reliability involve defining user-experience goals, setting realistic targets, building redundant systems, using horizontal scalability, utilizing observability, designing for graceful degradation, testing for recovery, and conducting thorough postmortems.\u003c/p\u003e\n"],["\u003cp\u003eThe focus areas for reliability are scoping, observation, response, and learning, which entail analyzing system architecture, monitoring for issues, responding to failures, and improving through experience.\u003c/p\u003e\n"]]],[],null,["# Well-Architected Framework: Reliability pillar\n\n| To view the content in the reliability pillar on a single page or to to get a PDF output of the content, see [View on one page](/architecture/framework/reliability/printable).\n\nThe reliability pillar in the\n[Google Cloud Well-Architected Framework](/architecture/framework)\nprovides principles and recommendations to help you design, deploy, and manage\nreliable workloads in Google Cloud.\n\nThis document is intended for cloud architects, developers, platform engineers,\nadministrators, and site reliability engineers.\n\n*Reliability* is a system's ability to consistently perform its intended\nfunctions within the defined conditions and maintain uninterrupted service. Best\npractices for reliability include redundancy, fault-tolerant design, monitoring,\nand automated recovery processes.\n\nAs a part of reliability, *resilience* is the system's ability to withstand and\nrecover from failures or unexpected disruptions, while maintaining performance.\nGoogle Cloud features, like\n[multi-regional deployments](/architecture/deployment-archetypes/multiregional),\nautomated backups, and disaster recovery solutions, can help you improve your\nsystem's resilience.\n\nReliability is important to your cloud strategy for many reasons, including the\nfollowing:\n\n- **Minimal downtime**: Downtime can lead to lost revenue, decreased productivity, and damage to reputation. Resilient architectures can help ensure that systems can continue to function during failures or recover efficiently from failures.\n- **Enhanced user experience**: Users expect seamless interactions with technology. Resilient systems can help maintain consistent performance and availability, and they provide reliable service even during high demand or unexpected issues.\n- **Data integrity**: Failures can cause data loss or data corruption. Resilient systems implement mechanisms such as backups, redundancy, and replication to protect data and ensure that it remains accurate and accessible.\n- **Business continuity**: Your business relies on technology for critical operations. Resilient architectures can help ensure continuity after a catastrophic failure, which enables business functions to continue without significant interruptions and supports a swift recovery.\n- **Compliance**: Many industries have regulatory requirements for system availability and data protection. Resilient architectures can help you to meet these standards by ensuring systems remain operational and secure.\n- **Lower long-term costs**: Resilient architectures require upfront investment, but resiliency can help to reduce costs over time by preventing expensive downtime, avoiding reactive fixes, and enabling more efficient resource use.\n\nOrganizational mindset\n----------------------\n\nTo make your systems reliable, you need a plan and an established strategy.\nThis strategy must include education and the authority to prioritize reliability\nalongside other initiatives.\n\nSet a clear expectation that the entire organization is responsible for\nreliability, including development, product management, operations, platform\nengineering, and\n[site reliability engineering (SRE)](/sre).\nEven the business-focused groups, like marketing and sales, can influence\nreliability.\n\nEvery team must understand the reliability targets and risks of their\napplications. The teams must be accountable to these requirements. Conflicts\nbetween reliability and regular product feature development must be prioritized\nand escalated accordingly.\n\nPlan and manage reliability holistically, across all your functions and teams.\nConsider setting up a Cloud Centre of Excellence (CCoE) that includes a\nreliability pillar. For more information, see\n[Optimize your organization's cloud journey with a Cloud Center of Excellence](https://cloud.google.com/blog/topics/training-certifications/optimize-your-organizations-cloud-journey-with-a-cloud-center-of-excellence).\n\nFocus areas for reliability\n---------------------------\n\nThe activities that you perform to design, deploy, and manage a reliable system\ncan be categorized in the following focus areas. Each of the reliability\nprinciples and recommendations in this pillar is relevant to one of these focus\nareas.\n\n- **Scoping**: To understand your system, conduct a detailed analysis of its architecture. You need to understand the components, how they work and interact, how data and actions flow through the system, and what could go wrong. Identify potential failures, bottlenecks, and risks, which helps you to take actions to mitigate those issues.\n- **Observation**: To help prevent system failures, implement comprehensive and continuous observation and monitoring. Through this observation, you can understand trends and identify potential problems proactively.\n- **Response**: To reduce the impact of failures, respond appropriately and recover efficiently. Automated responses can also help reduce the impact of failures. Even with planning and controls, failures can still occur.\n- **Learning**: To help prevent failures from recurring, learn from each experience, and take appropriate actions.\n\nCore principles\n---------------\n\nThe recommendations in the reliability pillar of the Well-Architected Framework are\nmapped to the following core principles:\n\n- [Define reliability based on user-experience goals](/architecture/framework/reliability/define-reliability-based-on-user-experience-goals)\n- [Set realistic targets for reliability](/architecture/framework/reliability/set-targets)\n- [Build highly available systems through resource redundancy](/architecture/framework/reliability/build-highly-available-systems)\n- [Take advantage of horizontal scalability](/architecture/framework/reliability/horizontal-scalability)\n- [Detect potential failures by using observability](/architecture/framework/reliability/observability)\n- [Design for graceful degradation](/architecture/framework/reliability/graceful-degradation)\n- [Perform testing for recovery from failures](/architecture/framework/reliability/perform-testing-for-recovery-from-failures)\n- [Perform testing for recovery from data loss](/architecture/framework/reliability/perform-testing-for-recovery-from-data-loss)\n- [Conduct thorough postmortems](/architecture/framework/reliability/conduct-postmortems)\n\n| **Note:** To learn about the building blocks of infrastructure reliability in Google Cloud, see [Google Cloud infrastructure reliability guide](/architecture/infra-reliability-guide).\n\nContributors\n------------\n\nAuthors:\n\n- [Laura Hyatt](https://www.linkedin.com/in/laura-hyatt) \\| Customer Engineer, FSI\n- [Jose Andrade](https://www.linkedin.com/in/jmandrade) \\| Customer Engineer, SRE Specialist\n- [Gino Pelliccia](https://www.linkedin.com/in/gino-pelliccia-13637025) \\| Principal Architect\n\n\u003cbr /\u003e\n\nOther contributors:\n\n- [Andrés-Leonardo Martínez-Ortiz](https://www.linkedin.com/in/almo) \\| Technical Program Manager\n- [Brian Kudzia](https://www.linkedin.com/in/brian-kudzia-3061558) \\| Enterprise Infrastructure Customer Engineer\n- [Daniel Lees](https://www.linkedin.com/in/daniellees) \\| Cloud Security Architect\n- [Filipe Gracio, PhD](https://www.linkedin.com/in/filipegracio) \\| Customer Engineer, AI/ML Specialist\n- [Gary Harmson](https://www.linkedin.com/in/garyharmson) \\| Principal Architect\n- [Kumar Dhanagopal](https://www.linkedin.com/in/kumardhanagopal) \\| Cross-Product Solution Developer\n- [Marwan Al Shawi](https://www.linkedin.com/in/marwanalshawi) \\| Partner Customer Engineer\n- [Nicolas Pintaux](https://www.linkedin.com/in/nicolaspintaux) \\| Customer Engineer, Application Modernization Specialist\n- [Radhika Kanakam](https://www.linkedin.com/in/radhika-kanakam-18ab876) \\| Program Lead, Google Cloud Well-Architected Framework\n- [Ryan Cox](https://www.linkedin.com/in/ryanlcox) \\| Principal Architect\n- [Samantha He](https://www.linkedin.com/in/samantha-he-05a98173) \\| Technical Writer\n- [Wade Holmes](https://www.linkedin.com/in/wholmes) \\| Global Solutions Director\n- [Zach Seils](https://www.linkedin.com/in/zachseils) \\| Networking Specialist\n\n\u003cbr /\u003e"]]