The documents in this series discuss networking architecture patterns that are
designed based on the required communication models between applications
residing in Google Cloud and in other environments (on-premises, in other
clouds, or both).

These patterns should be incorporated into the overall organization landing
zone architecture, which can include multiple networking patterns to address the
specific communication and security requirements of different applications.

The documents in this series also discuss the different design variations that
can be used with each architecture pattern. The following networking
patterns can help you to meet communication and security requirements for
your applications:

- [Mirrored pattern](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/mirrored-pattern)
- [Meshed pattern](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/meshed-pattern)
- [Gated patterns](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/gated-patterns)
  - [Gated egress](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/gated-egress)
  - [Gated ingress](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/gated-ingress)
  - [Gated egress and gated ingress](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/gated-egress-ingress)
- [Handover pattern](https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/handover-pattern)