You certainly built in a lot of end-user choice for backend storage of the flags, ways to access and change them (jmx, cli, rest), and so on. I read some of th

You certainly built in a lot of end-user choice for backend storage of the flags, ways to access and change them (jmx, cli, rest), and so on. I read some of the code, and there seems to be an opportunity. I don't see a lot of namespacing. So, for example, you might have a group of services that use the same backend to store flags. A pattern where you have a namespace (appname/service1, appname/service2) tied to get/set would relieve the end user from having to prepend prefixes on every call. I see something like that in your redis client...a default prefix. But then for some of the other backends, there's no similar concept.