3 ms·

At my job feature flags (and other configuration) get distributed as static files that replaced by config updates, so if there’s ever a disruption the hosts sti

by phyrex 3y ago

At my job feature flags (and other configuration) get distributed as static files that replaced by config updates, so if there’s ever a disruption the hosts still have the last valid code configuration values

malfist 3y ago
That works for simple on off flags that can wait for a deploy to change. Adding rules on top of that become complex
- phyrex 3y ago
  No, the deploy mechanism is separate from a code deploy. The rules themselves can get very complex and are distributed in the same way
  - malfist 3y ago
    Interesting, I'd like to know more. Is it home grown? Or do you use something COTS?
    - phyrex 3y ago
      It's homegrown. This paper talks about it: https://research.facebook.com/file/877841159827226/holistic-configuration-management-at-facebook.pdf https://research.facebook.com/file/877841159827226/holistic-... It also mentions Gatekeeper, which is the rule-based engine I mentioned built on top of it, but there are other feature flag solutions that use configerator for different use cases like killswitches or gradual rollout.
      - malfist 3y ago
        Thank you for that!