Edge or server evaluation? Measure before you choose
Evaluating flags at the edge is fast. Evaluating them on your server is simple. Which one you want depends on numbers you can measure in an afternoon.

Driftwire SDKs can evaluate a flag in three places: in your server process, at the CDN edge before the request reaches you, or in the browser. Each moves cost somewhere else.
Server-side
- The ruleset lives in your process; evaluation takes microseconds.
- Context can include anything your server knows: plan, account age, internal IDs.
- Cost: one streaming connection per process.
At the edge
- Decides before your origin is hit, so a page can be cached per variant.
- Context is limited to the request: cookies, headers, geography.
- Best for: routing, redirects, whole-page experiments.
How to choose
Measure two numbers
First, how much of your page is personalised: if a flag only changes one component, evaluate it on the server. Second, your cache hit rate per variant: if splitting the cache in two halves your hit rate, edge evaluation costs more than it saves.
Most teams end up with both: edge for routing and experiments, server for everything that needs account data.

Written by
Avery Lin
Staff Engineer, Edge
Avery builds the edge evaluation layer at Driftwire: the part that answers "is this flag on?" four hundred thousand times a second without asking anyone.
More posts by Avery Lin

