Cloud and Tiering

Start with memory when the application can refill its cache. Add a storage tier when data needs to outlive its current holders.

Storage choice	What it gives you	Boundary
Memory-only Swytch	Fast, disposable local state; shared keys may have other holders	Losing every holder loses the data
Atmos	A commercial local-disk tier	Available to commercial customers; setup documentation is supplied separately
Swytch Cloud	A network storage tier and peer discovery	Only uploaded, acknowledged state has reached durable storage

Atmos documentation is supplied separately to commercial customers.

Choose by the failure you need to survive

A process restart, Pod replacement, and loss of a node are different failures. Memory disappears with the process. Local storage depends on the lifetime and availability of its disk. A network tier can recover acknowledged state after all local processes stop.

Adding another Swytch replica does not automatically make a backup of every key. Subscriptions follow use.

Configure Swytch Cloud or follow Kubernetes tiering. For a rollout plan, read survive pod replacement.