Skip to content

docs: multi-region infrastructure - #1415

Merged
ennru merged 3 commits into
mainfrom
ennru-region-infra
Mar 17, 2026
Merged

ennru merged 3 commits into
mainfrom
ennru-region-infra

Conversation

@ennru

@ennru ennru commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

Introduce page with details about multi-region isolation and DNS management.

image

@github-actions github-actions Bot added the documentation documentation related label Mar 16, 2026

@nbarnes22 nbarnes22 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, minor comments

Akka multi-region is a series of features that allows Akka applications to replicate state between multiple Akka regions.
This page describes the infrastructure in place to enable these features. It does not explain the replication itself,
for a detailed understanding of how Akka replicates data across regions, the best place to go is the Akka libraries
documentation on replicated event sourcing.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for a detailed understanding of how Akka replicates data across regions, the best place to go is the Akka libraries
documentation on replicated event sourcing.

The Akka infrastucture relies on three main features enabling multi-region replication:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

infrastructure*

different environments, for example, there may be a production region group, and a development region group.

=== mTLS Authentication
All cross-region communication is authenticated using mutual Transport Layer Security (mTLS). So, every client, and every

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Omit so

For customers using a `secondary_apps_domain_name` for region or cluster-level failover routing, the same customer-provided
`ClusterIssuer` used for auto-generated hostname certificates is reused to automatically provision certificates for the secondary
hostname.
This configuration enables DNS-level healthchecks and global traffic management patterns. The DNS structure follows a two-tier pattern:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

health checks*

@ennru
ennru merged commit 2655fd8 into main Mar 17, 2026
10 checks passed
@ennru
ennru deleted the ennru-region-infra branch March 17, 2026 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation documentation related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants