Chapter 5. Best Practice #3: Make Flagging Decisions on the Server
In addition to logic implemented on the server side, modern web applications often contain rich client-side logic. When applying feature flagging, we usually have a choice between making our toggling decision client side or server side, and there are trade-offs to consider either way.
Performance
By moving flagging decisions to the server side, you gain user-perceived performance. Single-page applications are already making a server-side call to render the data needed for the UI. At this time, you could also make a call to a feature-flag service, so one network call fetches all feature-flag evaluations with the server-side data.
Configuration Lag
One way in which engineers improve performance of an application is to cache data locally, thereby reducing network latency. This has an impact on where the feature flag decision should be made. You could opt to proactively request all flagging decisions for a specific runtime context (i.e., current user, browser, and geolocation) from the server. Or, you could just request the current feature-flagging configuration and make flagging decisions using a client-side toggle router. In both approaches, you are at risk of Configuration Lag.
When a Site Reliability Engineer hits a kill switch to disable a feature that’s going sideways, how does your client-side feature-flagging system find out? Do you poll for updates on a regular basis? Maybe there is a server-side push system ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access