Flags sit on the request path of everything, so a slow flag service is a site-wide outage waiting to happen. Local snapshots, propagation numbers, and audit trails are what interviewers dig for.
an account raises the per-topic limit · no card
← DevOps System Design & Architecture / 17
mediumNewAtlassianGoldman SachsWalmart Global Tech
Design a feature flag service used by 200 services. Why keep ordinary evaluation off the network path?
Flags sit on the request path of everything, so a slow flag service is a site-wide outage waiting to happen. Local snapshots, propagation numbers, and audit trails are what interviewers dig for.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackPostgres is out of headroom. How do you choose a shard key, and how do you reshard later without downtime?Next in this trackDesign type-ahead search for a marketplace with fifty million products. It must feel instant.Next in this trackCheckout calls five downstream services. Design backpressure so overload degrades instead of collapsing.
DISCUSSION · 0
Nothing here yet. Say how you would answer it.