FAQ

Common questions about SOASAP evaluation, cache, SSE, and SDKs.

How fast is flag evaluation?

O(1) in-memory reads. No network I/O on the hot path. Latency is dominated by your application logic, not SOASAP.

Does evaluation require network calls?

No. SDKs evaluate against a local snapshot. The control plane is used for sync and management only.

What happens during outages?

Evaluation continues using the last known snapshot and your code-defined defaults. See Offline Operation.

What happens during startup?

Cold start restores from persistent cache when available, then reconnects SSE. Use preload patterns to avoid blocking the host. See Non-Blocking Startup.

How does cache work?

The SDK debounces disk writes and reloads the snapshot on restart. See Persistent Cache.

How does SSE work?

A long-lived connection receives flag deltas. Reconnect with backoff on failure. See Real-Time Synchronization.

Can I use SOASAP in mobile apps?

Yes. React Native and Kotlin SDKs support offline operation and persistent cache.

Can I use SOASAP in offline environments?

Yes, after an initial sync. Evaluation uses the last snapshot until connectivity returns.

How many flags are supported?

Designed for large flag sets with O(1) reads. Monitor memory for very large JSON payloads. See Large Flag Sets.

Is SOASAP self-hosted?

SOASAP is offered as a managed cloud service. SDKs do not require self-hosting for evaluation.

What SDKs are available?

.NET, Node.js, Python, React, Angular, React Native, and Kotlin. Swift is planned. See SDK Installation.