Multiple ChoiceIntermediate 45s
Consistent Rollout via Hashing
How does a feature-flag service keep a percentage rollout consistent across requests and services?
Options
- 1Sample a brand-new random number independently on every single evaluation request the service handles
- 2Deterministically hash a stable identity plus the flag key into a bucket and compare to the rollout threshold
- 3Use the serving host's current wall-clock time as the seed when selecting which rollout bucket applies
- 4Round-robin incoming users into rollout buckets strictly in the order their requests happen to arrive
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.