Modelli di architettura di rete sicura ibrida e multi-cloud
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Last reviewed 2024-10-29 UTC
Questo documento è il terzo di un insieme di tre documenti. Vengono illustrati i modelli di architettura di rete ibrida e multi-cloud. Questa parte esplora diversi
modelli di architettura di rete sicura comuni che puoi utilizzare per le architetture ibride e
multi-cloud. Descrive gli scenari per cui questi pattern di networking
sono più adatti e fornisce le best practice per implementarli
con Google Cloud.
Il set di documenti per i modelli di architettura ibrida e multi-cloud è composto da queste parti:
Crea architetture ibride e multi-cloud: descrive la pianificazione di una strategia per la progettazione di una configurazione ibrida e multi-cloud con Google Cloud.
Modelli di architettura di rete sicura ibrida e multi-cloud: vengono illustrati i modelli di architettura di rete ibrida e multi-cloud da una prospettiva di rete (questo documento).
Il collegamento di ambienti di computing privati a Google Cloud in modo sicuro e
affidabile è essenziale per qualsiasi architettura ibrida e multi-cloud di successo.
La connettività di rete ibrida e il modello di architettura di rete cloud che scegli per una configurazione ibrida e multi-cloud devono soddisfare i requisiti unici dei tuoi carichi di lavoro aziendali. Deve anche essere adatto ai pattern di architettura che intendi applicare. Anche se potrebbe essere necessario personalizzare ogni progetto, esistono pattern comuni che puoi utilizzare come modello.
Diverse applicazioni possono utilizzare pattern di architettura di rete diversi,
che vengono incorporati come parte di un'architettura di zona di destinazione. In una configurazione
multicloud, devi mantenere la coerenza della progettazione della landing zone in tutti
gli ambienti.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2024-10-29 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"]]