# Example: Regional Distribution

AMPS is well suited for replicating messages to different regions, so clients in those regions are able to quickly receive and publish messages to a local instance. In this case, each region replicates all messages on the topic of interest to the other region(s). A variation on this strategy is to use a region tag in the content, and use content filtering so that each replicates messages intended for use in the other regions or worldwide.

<figure><picture><source srcset="https://82018141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFQiXqIcXoyOqwDbFf6Nl%2Fuploads%2Fgit-blob-98cde5bdfbed7bdc2b148f22aac349a27924e14c%2Fha-regional-distribution-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://82018141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFQiXqIcXoyOqwDbFf6Nl%2Fuploads%2Fgit-blob-f1fa82392f074fbdf52b3ebb8d2cb4b5d1fa4389%2Fha-regional-distribution-light.svg?alt=media" alt="Diagram showing replication between geographic regions" width="300"></picture><figcaption></figcaption></figure>

For this scenario, an AMPS instance in each region replicates to an instance in the other region. To reduce the memory and storage required for publishers, replication between the regions uses `async` acknowledgment, so that once the instance in one region has persisted the message, the message is acknowledged back to the publisher.

In this case, clients in each region connect _only_ to the AMPS instance in that region. Bandwidth within regions is conserved, because each message is replicated once to the region, regardless of how many subscribers in that region will receive the message. Further, publishers are able to publish the message once to a local instance over a relatively fast network connection rather than having to publish messages multiple times to multiple regions.

To configure this scenario, the AMPS instance in each region is configured to forward messages to known instances in the other region.
