Padrões de arquitetura de rede seguros híbridos e de várias nuvens
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Last reviewed 2023-12-14 UTC
Este é o terceiro de três documentos de um conjunto. Ele aborda temas híbridos
e multicloud. Esta parte explora várias
padrões comuns de arquitetura de rede segura que podem ser usados para ambientes
multicloud. Ele descreve cenários em que essas redes
são mais adequados e fornece práticas recomendadas para implementá-los
com o Google Cloud.
O conjunto de documentos para padrões de arquitetura híbridos e de várias nuvens consiste em:
essas partes:
Crie arquiteturas híbridas e de várias nuvens:
discute o planejamento de uma estratégia para arquitetar uma infraestrutura híbrida e de várias nuvens
configuração com o Google Cloud.
Padrões de arquitetura de rede híbridos e seguros para várias nuvens:
aborda padrões de arquitetura de rede híbrida e de várias nuvens
perspectiva de rede (este documento).
Conectar ambientes de computação particulares ao Google Cloud com segurança e
é essencial para qualquer arquitetura híbrida e de multicloud.
O padrão de conectividade de rede híbrida e de arquitetura de rede em nuvem que você
para uma configuração híbrida e de várias nuvens precisam atender aos requisitos exclusivos de
das cargas de trabalho da sua empresa. Ele também precisa se adequar aos padrões de arquitetura que você
que pretendemos aplicar. Embora possa ser necessário adaptar cada design, há padrões comuns que você pode usar como uma planta.
Os padrões de arquitetura de rede neste documento não devem ser
consideradas alternativas
design de zona de destino no Google Cloud.
Em vez disso, você deve projetar e implantar os padrões de arquitetura
selecionar como parte do design geral da zona de destino do Google Cloud,
abrange as seguintes áreas:
Identidades
Gerenciamento de recursos
Segurança
Rede
Monitoramento
Diferentes aplicativos podem usar diferentes padrões de arquitetura de rede,
que são incorporadas como parte da arquitetura de uma zona de destino. Em uma multicloud
configuração, mantenha a consistência do design da zona de destino em todas
do Google Cloud.
[[["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 2023-12-14 UTC."],[[["\u003cp\u003eThis document focuses on secure networking architecture patterns for hybrid and multicloud environments, specifically as they relate to Google Cloud.\u003c/p\u003e\n"],["\u003cp\u003eIt details common patterns, their ideal use cases, and best practices for implementation within Google Cloud's ecosystem.\u003c/p\u003e\n"],["\u003cp\u003eThe patterns discussed are designed to securely and reliably connect private computing environments to Google Cloud.\u003c/p\u003e\n"],["\u003cp\u003eThese networking patterns should be integrated into an overarching Google Cloud landing zone design, which includes aspects like identities, security, resource management, networking, and monitoring.\u003c/p\u003e\n"],["\u003cp\u003eThe document is the third in a series that explores hybrid and multicloud architectures, focusing on the networking perspective, and it provides links to other related content within the series.\u003c/p\u003e\n"]]],[],null,["# Hybrid and multicloud secure networking architecture patterns\n\nThis document is the third of three documents in a set. It discusses hybrid\nand multicloud networking architecture patterns. This part explores several\ncommon secure network architecture patterns that you can use for hybrid and\nmulticloud architectures. It describes the scenarios that these networking\npatterns are best suited for, and provides best practices for implementing them\nwith Google Cloud.\n\nThe document set for hybrid and multicloud architecture patterns consists of\nthese parts:\n\n- [Build hybrid and multicloud architectures](/architecture/hybrid-multicloud-patterns): discusses planning a strategy for architecting a hybrid and multicloud setup with Google Cloud.\n- [Hybrid and multicloud architecture patterns](/architecture/hybrid-multicloud-patterns-and-practices): discusses common architecture patterns to adopt as part of a hybrid and multicloud strategy.\n- Hybrid and multicloud secure networking architecture patterns: discusses hybrid and multicloud networking architecture patterns from a networking perspective (this document).\n\nConnecting private computing environments to Google Cloud securely and\nreliably is essential for any successful hybrid and multicloud architecture.\nThe hybrid networking connectivity and cloud networking architecture pattern you\nchoose for a hybrid and multicloud setup must meet the unique requirements of\nyour enterprise workloads. It must also suit the architecture patterns you\nintend to apply. Although you might need to tailor each design, there are common patterns you can use as a blueprint.\n\nThe networking architecture patterns in this document shouldn't be\nconsidered alternatives to the\n[landing zone design in Google Cloud](/architecture/landing-zones).\nInstead, you should design and deploy the architecture patterns you\nselect as part of the overall Google Cloud landing zone design, which\nspans the following areas:\n\n- Identities\n- Resource management\n- Security\n- Networking\n- Monitoring\n\nDifferent applications can use different networking architecture patterns,\nwhich are incorporated as part of a landing zone architecture. In a multicloud\nsetup, you should maintain the consistency of the landing zone design across all\nenvironments.\n\nThis series contains the following pages:\n\n- [Design considerations](/architecture/hybrid-multicloud-secure-networking-patterns/design-considerations)\n- [Architecture patterns](/architecture/hybrid-multicloud-secure-networking-patterns/architecture-patterns)\n - [Mirrored pattern](/architecture/hybrid-multicloud-secure-networking-patterns/mirrored-pattern)\n - [Meshed pattern](/architecture/hybrid-multicloud-secure-networking-patterns/meshed-pattern)\n - [Gated patterns](/architecture/hybrid-multicloud-secure-networking-patterns/gated-patterns)\n - [Gated egress](/architecture/hybrid-multicloud-secure-networking-patterns/gated-egress)\n - [Gated ingress](/architecture/hybrid-multicloud-secure-networking-patterns/gated-ingress)\n - [Gated egress and ingress](/architecture/hybrid-multicloud-secure-networking-patterns/gated-egress-ingress)\n - [Handover](/architecture/hybrid-multicloud-secure-networking-patterns/handover-pattern)\n- [General best practices](/architecture/hybrid-multicloud-secure-networking-patterns/general-best-practices)\n\nContributors\n------------\n\nAuthor: [Marwan Al Shawi](https://www.linkedin.com/in/marwanalshawi) \\| Partner Customer Engineer\n\nOther contributors:\n\n- [Saud Albazei](https://www.linkedin.com/in/albazei) \\| Customer Engineer, Application Modernization\n- [Anna Berenberg](https://www.linkedin.com/in/annaberenberg) \\| Engineering Fellow\n- [Marco Ferrari](https://www.linkedin.com/in/ferrarimark) \\| Cloud Solutions Architect\n- [Victor Moreno](https://www.linkedin.com/in/vimoreno) \\| Product Manager, Cloud Networking\n- [Johannes Passing](https://www.linkedin.com/in/johannespassing) \\| Cloud Solutions Architect\n- [Mark Schlagenhauf](https://www.linkedin.com/in/mark-schlagenhauf-63b98) \\| Technical Writer, Networking\n- [Daniel Strebel](https://www.linkedin.com/in/danistrebel) \\| EMEA Solution Lead, Application Modernization\n- [Ammett Williams](https://www.linkedin.com/in/ammett) \\| Developer Relations Engineer\n\n\u003cbr /\u003e"]]
