Repository navigation
docs: add a decision guide for choosing your environment - #1831
Conversation
…gnty Add "Choosing your environment" to Production Readiness: how Akka sizes a new environment (the four starting shapes and what drives their cost), when zones are enough versus when multi-region is worth the added cost, and how region choice determines data sovereignty. These are account-team-mediated decisions today, not self-service settings, so the page is written as a decision framework rather than a how-to. Cross-linked from the production readiness overview, which also gains "Data sovereignty" as a named readiness dimension.
|
Related to #1828 (per-service instance sizing): the "Sizing your environment" section here mentions per-service tuning but links to |
|
|
||
| == Sizing your environment | ||
|
|
||
| Every environment has a fixed platform layer (orchestration, gateways, security, observability) that runs regardless of what you deploy, plus a variable service layer that scales with what you run. Platform cost does not drop as you remove services; it is the minimum cost of the environment itself. Low utilization during normal operation is expected: an environment is sized for spikes and failures, not for continuous high load. |
There was a problem hiding this comment.
Might be possible to misunderstand what environment we are talking about here. We are describing the platform infrastructure here and not the service sizing or scaling of service pods. Shouldn't service sizing and scaling be described or mentioned in same page?
There was a problem hiding this comment.
Agreed, that is why I added this comment - so this one should not be completed until 1828 is done. I'll go ahead and change this PR to draft then.
There was a problem hiding this comment.
#1828 merged, so I've replaced the placeholder pointer with a real link to services/instance-sizing.adoc and clarified this page covers platform-level sizing only. Marked ready for review again.
…ederation Plane Address review feedback: "your data stays inside the region you choose" read as contradicting the multi-region section, where data is explicitly replicated to a second chosen region. Reword to be plural-aware (regions you select, not a single region), and name that this is about application data specifically, distinct from the globally-run Federation Plane described in the technical overview.
Replace the placeholder pointer to technical-overview.adoc with the real cross-link to services/instance-sizing.adoc, and clarify that platform-level sizing (this page) and per-service sizing (that page) are separate, the latter being self-service. Addresses the review comment that per-service sizing was missing from this page, which was blocked on #1828 merging.
Summary
akka_sizing_availability_multiregion.docx), restyled to match docs voice (second person, no marketing language, literal terminology) and re-verified against internal references for accuracy — the preset names and figures match Akka's internal cluster-tier reference exactly.Test plan
docs/bin/verify-include-paths.shpassesdocs/bin/vale.sh— 0 errors (matches CI gate); reviewed remaining style warnings, left as-is where they match existing repo conventions (e.g. spaced em-dashes) or are false positives (e.g. flagging "AWS" as a term to lowercase)asciidoctorrender of both changed pages checked for syntax (Docker unavailable in the authoring environment for a full Antora build)make local opento confirm nav placement and xref resolution in the full site build