Local Evaluation
The read path never calls SOASAP Cloud. Evaluation is O(1) against an in-memory snapshot.
This is the primary differentiator. Teams adopt SOASAP for predictable hot-path latency and resilience, not for another HTTP API on every request.
SDK evaluation flow
flags.GetBool("feature-x")
?
In-memory snapshot
?
O(1) lookup
What does not happen on the read path
- No network calls — no HTTP, gRPC, or DNS on evaluation.
- No disk access — reads do not touch the persistent cache.
- No API latency — tail latency is not tied to SOASAP Cloud uptime.
Background work (SSE, cache writes) runs off the hot path. See Real-Time Synchronization.