Patrones de arquitectura de herramientas de redes seguras de nubes híbridas y múltiples
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Last reviewed 2023-12-14 UTC
Este documento es el tercero de tres documentos de un conjunto. Se analizan los patrones de arquitectura de redes híbridas y de múltiples nubes. En esta parte, se exploran varios patrones comunes de arquitectura de red segura que puedes usar para arquitecturas híbridas y de múltiples nubes. Se describen las situaciones para las que estos patrones de herramientas de redes son más adecuados y se proporcionan prácticas recomendadas para implementarlas con Google Cloud.
El conjunto de documentos para patrones de arquitectura híbridos y de múltiples nubes consta de estas partes:
Patrones de arquitectura de herramientas de redes seguras de nubes híbridas y múltiples: se analizan los patrones de arquitectura de redes híbridas y de múltiples nubes desde la perspectiva de las herramientas de redes (este documento).
Conectar entornos de computación privados a Google Cloud de forma segura y confiable es esencial para cualquier arquitectura híbrida y de múltiples nubes exitosa.
El patrón de conectividad de red híbrida y arquitectura de red en la nube que elijas para una configuración de nube híbrida y múltiples nubes debe cumplir con los requisitos únicos de tus cargas de trabajo empresariales. También debe adaptarse a los patrones de arquitectura que planeas aplicar. Aunque es posible que debas adaptar cada diseño, hay patrones comunes que puedes usar como plano.
Los patrones de arquitectura de herramientas de redes de este documento no deben considerarse alternativas al diseño de la zona de destino en Google Cloud.
En cambio, debes diseñar e implementar los patrones de arquitectura que selecciones como parte del diseño general de la zona de destino de Google Cloud, que abarca las siguientes áreas:
Identidades
Administración de recursos
Seguridad
Redes
Supervisión
Las diferentes aplicaciones pueden usar distintos patrones de arquitectura de herramientas de redes, que se incorporan como parte de una arquitectura de zona de destino. En una configuración de múltiples nubes, debes mantener la coherencia del diseño de la zona de destino en todos los entornos.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 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"]]
