2 ms·
Last time I did this, we ended up routing our flags through a reloadable config system which used Consul for distribution. We almost never shared flags across
by hinkley 2y ago
Last time I did this, we ended up routing our flags through a reloadable config system which used Consul for distribution.
We almost never shared flags across our fairly chunky servicees. We usually found a softer way to do it.
Even with Consul, you can still have enough skew that a few requests in the middle might see A and !A if your request rate is high enough. So it depends on your business model and architecture if that’s acceptable.