4 ms·
It's a pretty question architecture that outsources feature flags to a third party. You're creating a critical path hard dependency and for most apps this is g
by siliconc0w 10y ago
It's a pretty question architecture that outsources feature flags to a third party. You're creating a critical path hard dependency and for most apps this is going to be hit multiple times on every request and is something you're going to want to run locally.
- deleted 10y ago[deleted]
- jkodumal 10y agoWe've thought quite a bit about how to make this work as a service. The key to our architecture is that evaluating a feature flag for a user does not involve a remote call. We make that work by embedding a rule evaluation engine in our SDKs. When you request a flag, the user is compared against these rules (in memory) and served the appropriate variation. We then use a streaming API to serve rule changes, so when you make a change to your dashboard, the new rules are streamed to all your backend servers within a few hundred milliseconds. If you need even more resiliency, you can deploy a small service in your own infrastructure (https://github.com/launchdarkly/ld-relay https://github.com/launchdarkly/ld-relay) that allows you to persist these flag configurations in Redis.
- rch 10y agoYour rules engine sounds interesting - definitely worth a closer look.