Anti-Patterns
These are the architecture lies that make stateful platforms fragile.
Pretending Sessions Teleport
Moving traffic to a new allocation or region while implying active live sessions moved with it.
Better model
Say sessions drain in place, hydrate on reconnect with durable state, or start fresh.
Warning signals
Using Logs As Truth
Deriving deploy/promotion/wake status from logs rather than operation stage records.
Better model
Operations own mutation truth; logs are diagnostic evidence.
Warning signals
Event Bus As Database
Treating NATS/JetStream as the authoritative source rather than propagation.
Better model
Database/control plane commits truth, events propagate changes to consumers.
Warning signals
Routing By Healthy Backend
Letting service discovery decide production ownership.
Better model
RouteOwner and epoch decide deployment authority; health only chooses among eligible allocations.
Warning signals
Unsafe Wake Replay
Buffering POST/webhook/action bodies during wake without idempotency and replay contract.
Better model
Wake unsafe routes only with explicit idempotency or return controlled retryable response.
Warning signals
MVP Erases Topology
Building launch as if region/cell/resource identity can be added later.
Better model
Keep region/cell/deployment/artifact/allocation identity from day one, even if only one exists.
Warning signals
Warm Deploy Equals Safe Rollback
Assuming Vango state compatibility proves database rollback safety.
Better model
Vango state impact and DB migration impact are separate gates.
Warning signals