이 문서는 총 3부로 구성된 문서 중 세 번째 문서입니다. 하이브리드 및 멀티 클라우드 네트워킹 아키텍처 패턴에 대해 다룹니다. 하이브리드 및 멀티 클라우드 아키텍처에 사용할 수 있는 몇 가지 일반적인 보안 네트워크 아키텍처 패턴을 설명합니다. 이 문서에서는 이러한 네트워킹 패턴이 가장 적합한 시나리오를 설명하고 Google Cloud를 사용하여 이를 구현하기 위한 권장사항을 제공합니다.
하이브리드 및 멀티 클라우드 보안 네트워킹 아키텍처 패턴:
네트워킹 관점에서 하이브리드 및 멀티 클라우드 네트워킹 아키텍처 패턴을 논의합니다.
성공적인 하이브리드 및 멀티 클라우드 아키텍처를 위해서는 비공개 컴퓨팅 환경을 Google Cloud 안전하게 안정적으로 연결하는 것이 필수적입니다.
하이브리드 및 멀티 클라우드 설정을 위해 선택하는 하이브리드 네트워킹 연결 및 클라우드 네트워킹 아키텍처 패턴은 엔터프라이즈 워크로드의 고유한 요구사항을 충족해야 합니다. 또한 적용하려는 아키텍처 패턴에 적합해야 합니다. 각 디자인을 맞춤설정해야 할 수도 있지만 청사진으로 사용할 수 있는 일반적인 패턴이 있습니다.
이 문서의 네트워킹 아키텍처 패턴을 Google Cloud의 시작 영역 설계의 대안으로 간주해서는 안 됩니다.
대신 다음 영역을 포함한 전체 Google Cloud 시작 영역 설계의 일부로 선택한 아키텍처 패턴을 설계하고 배포해야 합니다.
ID
리소스 관리
보안
네트워킹
모니터링
애플리케이션마다 시작 영역 아키텍처의 일부로 통합된 다른 네트워킹 아키텍처 패턴을 사용할 수 있습니다. 멀티 클라우드 설정의 경우 모든 환경에서 시작 영역 설계의 일관성을 유지해야 합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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"]]
