This section of theGoogle Cloud deployment archetypes guide describes the hybrid deployment archetype, provides examples of use cases,and discusses design considerations.

In an architecture that's based on the hybrid deployment archetype, some partsof the application are deployed in Google Cloud, and other parts runon-premises.

Use cases

The following sections provide examples of use cases for which the hybriddeployment archetype is an appropriate choice.

• Low-cost, unlimitedarchive storage in the cloud for an on-premises application.
• AI and ML applications in the cloud for data generated by an on-premises application.
• Cloud-based data warehouse and analytics processes usingBigQuery for data ingested from on-premises data sources.
• Cloud bursting,to handle overflow traffic when the load on the on-premises applicationreaches peak capacity.

The following diagram shows a hybrid topology where data from an on-premisesapplication is uploaded to Google Cloud. Data analysts analyze theuploaded data by using advanced AI, ML, big data, and analytics capabilities inGoogle Cloud.

Tiered hybrid topology

In this topology, which is sometimes called a split-stack deployment, theapplication's frontend is in Google Cloud, and the backend is on-premises.The frontend might include capabilities like load balancing, CDN, DDoSprotection, and access policies. The frontend sends traffic to the on-premisesbackend for processing, as shown in the following diagram:

This architecture might be suitable when an application is used globally but thebackend needs to be within a single, controlled environment. A variation of thisuse case is to run the frontend on-premises and deploy the backend inGoogle Cloud.

More information

For more information about the rationale and use cases for the hybrid deploymentarchetype, seeBuild hybrid and multicloud architectures using Google Cloud.

Design considerations

When you build an architecture that's based on the hybrid deployment archetype,consider the following design factors.

On-premises to cloud network connection

For efficient network communication between your on-premises environment and theresources in Google Cloud, you need a network connection that's reliableand secure. For more information about hybridconnectivity options offered by Google Cloud, seeChoosing a Network Connectivity product.

Setup effort and operational complexity

Setting up and operating a hybrid topology requires more effort than anarchitecture that uses only Google Cloud. To operate this topology, youneed to manage resources consistently across the on-premises andGoogle Cloud environments.

Cost of redundant resources

A hybrid deployment is potentially more expensive than a cloud-only deployment,because data might need to be stored redundantly on-premises and in the cloud.Also, some of the redundant resources might be underutilized. When you build anarchitecture that's based on the hybrid deployment archetype, consider thepotentially higher overall cost of resources.

Example architectures

For examples of architectures that use the hybrid deployment archetype, seeBuild hybrid and multicloud architectures using Google Cloud.