App Hub lets you create global, multi-regional, or regional
applications so you can group components based on their geography and how they
communicate. Your [location](https://docs.cloud.google.com/app-hub/docs/locations.md.txt) choice determines which
services and workloads you can register and affects data residency, network
latency, organization policy compliance, and cost.

## Global, multi-regional, and regional applications

Global, multi-regional, and regional applications are defined as follows:

- **Global applications:** Functionally group services and workloads that are
  globally distributed or spread across multiple Google Cloud regions. For
  example, you can include a global Application Load Balancer service and its
  backend workloads distributed worldwide.

- **Multi-regional applications:** Functionally group services and workloads
  that reside within a supported multi-region (`us` in the United States or
  `eu` in the European Union) and its constituent Google Cloud regions. For
  example, an application in `us` can include multi-regional resources in `us`
  and regional resources across regions in the United States, such as
  `us-central1` and `us-east1`.

- **Regional applications:** Functionally group services and workloads that
  reside entirely within a single Google Cloud region. For example, you can
  include a regional Application Load Balancer service and its backend
  workloads, all located in `us-central1`.

To make the best decision for your needs, it's crucial to understand
Google Cloud regions and zones, which are designed to provide fault tolerance
and high availability. Regions are independent geographic areas, and zones are
deployment areas within a region, acting as single failure domains. To learn
more about global, multi-regional, and regional resources, see
[Geography and regions](https://docs.cloud.google.com/docs/geography-and-regions.md.txt) and
[Cloud locations](https://cloud.google.com/about/locations).

The following table highlights the key differences and considerations to help
you choose between global, multi-regional, and regional applications:

|   | **Global application** | **Multi-regional application** | **Regional application** |
|---|---|---|---|
| **Recommended use case** | Best for applications with components that are inherently global or distributed across multiple regions worldwide. | Recommended when application components span multiple regions within a supported multi-region (`us` or `eu`) or use multi-regional resources. | Recommended when all application components reside within the same Google Cloud region, even if they span multiple projects. |
| **Resource extent** | Can contain global, multi-regional, and regional Google Cloud resources from any location. | Can contain Google Cloud resources located in the same multi-region (`us` or `eu`) and in the constituent regions of that multi-region. You can't register global components in a multi-regional application. | Can only contain Google Cloud resources from the *same single region* as the application. You can't register global or multi-regional components in a regional application. |
| **Application metadata** | Stored across multiple regions and accessible from any Google Cloud region. [Data residency](https://docs.cloud.google.com/assured-workloads/docs/data-residency.md.txt) isn't supported. | Stored within the specified multi-region and accessible from any Google Cloud region. [Data residency](https://docs.cloud.google.com/assured-workloads/docs/data-residency.md.txt) isn't supported. | Stored within the specific region, and accessible from any other Google Cloud region when using the global endpoint. Data residency is supported when you use [regional endpoints](https://docs.cloud.google.com/app-hub/docs/regional-endpoints.md.txt), which restrict request processing to the specified region. |
| **Examples** | Managing a global load-balanced application with backend components in various regions to provide a centralized view of the distributed system. | Managing an application in `us` with services and workloads distributed across `us-central1` and `us-east1`. | Managing an application with all services and workloads in `us-central1`. |

## Select the best location for your application

Consider the architecture and operational requirements of the business function
the application represents when choosing between global, multi-regional, and
regional locations. The following comparison is based on geography
considerations:

- In general, [regional applications offer significant benefits](https://docs.cloud.google.com/app-hub/docs/global-regional-applications.md.txt#regional-benefits) over global applications. If you want to take advantage of lower component latency, alignment with data locality requirements, potential network cost savings, and inherent consistency with region-specific Google Cloud features, opt for *regional* applications.
- If your application components span multiple regions within the United States (`us`) or the European Union (`eu`) and don't rely on global Google Cloud resources, opt for *multi-regional* applications.
- If your application components are necessarily distributed across multiple continents or rely on global Google Cloud resources, opt for *global* applications.

You might have Google Cloud resources located in multiple regions that don't
form a single, cohesive global function. In that case, it is often best practice
to define separate regional applications for components within each region.
This approach maximizes [the benefits of regionalization](https://docs.cloud.google.com/app-hub/docs/global-regional-applications.md.txt#regional-benefits)
for each deployment.

Your Google Cloud resource hierarchy, which defines how you organize folders and
projects, is also fundamental. A well-planned hierarchy that aligns with your
application management boundaries, whether regional, multi-regional, or global, simplifies
the grouping and management of services and workloads in applications. For more
information, see [Choose your application setup model](https://docs.cloud.google.com/app-hub/docs/set-up-app-hub.md.txt).

### Benefits of regional applications

Global applications offer flexibility for distributed systems. However, choosing
a regional location for your App Hub applications can provide
significant advantages:

- **Support data residency and compliance:** App Hub metadata
  supports [data residency](https://docs.cloud.google.com/assured-workloads/docs/data-residency.md.txt) when you
  access your regional applications using
  [regional endpoints](https://docs.cloud.google.com/app-hub/docs/regional-endpoints.md.txt). This helps you make
  sure that both your application metadata and the data that the underlying
  Google Cloud resources process and store remain within the geographic limits
  you select. This benefit is crucial for complying with legal, regulatory,
  and organizational requirements for data locality and data sovereignty.

- **Reduce latency:** Colocating application components within the same region
  generally minimizes
  [network latency between components](https://docs.cloud.google.com/network-intelligence-center/docs/performance-dashboard/how-to/view-google-cloud-latency.md.txt),
  potentially improving application performance and user experience.

<!-- -->

- **Meet product feature requirements:** Certain Google Cloud products or features mandate that all interacting components be located in the same region. For example, a Compute Engine instance can only [attach a persistent disk](https://docs.cloud.google.com/compute/docs/disks/regional-persistent-disk.md.txt#repd_add_disk) that is in the same region. A regional App Hub application aligns inherently with such architectural constraints.

<!-- -->

- **Optimize cost:** Data transfer *between* different Google Cloud regions [often incurs networking costs](https://cloud.google.com/vpc/network-pricing), whereas network traffic *within* the same region is typically priced lower. By creating your application regionally, you can better manage and reduce cross-region network charges.

<!-- -->

- **Align with failure domains:** Google Cloud regions are [designed to be independent failure domains](https://cloud.google.com/about/locations). Deploying your application within a single region and using multiple zones within that region for high availability aligns your application's fault tolerance with Google Cloud's infrastructure resilience model.

## What's next

- [Review the list of available App Hub locations](https://docs.cloud.google.com/app-hub/docs/locations.md.txt)

<!-- -->

- [Identify App Hub supported resources](https://docs.cloud.google.com/app-hub/docs/supported-resources.md.txt)

<!-- -->

- [Learn more about geography and regions](https://docs.cloud.google.com/docs/geography-and-regions.md.txt)
- [Review Cloud locations](https://cloud.google.com/about/locations)

<!-- -->

- [Choose your application setup model](https://docs.cloud.google.com/app-hub/docs/set-up-app-hub.md.txt)