Feature flags API in Go

Hootsuite wrote a blog post on doing this sort of thing with Consul: <a href="http:&#x2F;&#x2F;code.hootsuite.com&#x2F;distributed-configuration-management-and-dark-launching-using-consul&#x2F;" rel="nofollow">http:&#x2F;&#x2F;code.hootsuite.com&#x2F;distributed-configuration-manageme...</a> (The post itself is over a year old but the concepts still apply today)<p>You can use the Go API client[1] to make this possible from Go. I&#x27;m biased as I work for HashiCorp but just wanted to add a server-based option to the mix if a local BoltDB won&#x27;t work for you.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;hashicorp&#x2F;consul&#x2F;tree&#x2F;master&#x2F;api" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;hashicorp&#x2F;consul&#x2F;tree&#x2F;master&#x2F;api</a>

The API usage is very inefficent when using it for every feature-flag in an app. If you could call the API with user-ID and group and it returns all the feature-flags active there would be a far greater use-case.

Rollout flags are IMHO best implemented when they are pushed to the machines that need to read them by a technology like zookeeper. Pushed updates are then cached in memory by the machines receiving the updates and can be queried in the hotpath without having to worry about cache invalidation and the extra overhead of network calls.

We&#x27;ve been working on something very similar at work. I don&#x27;t know if this solution scales very well, as others have mentioned here. One thing that seems unusual to me is the decision to use a POST request instead of GET for the &#x2F;access endpoint.