Thank you everyone for the great commentary thus far. Please keep it coming!
@xzion - please do not consider the text to be final by any means. Contextual supporting information will be included too.
@Seravy and @xzion - the 10 request rate limit is actually a little different to what both of you have specified. Good callout from a clarity perspective though! Current configuration is returned on extension load. As discussed in the first point in drawbacks, live updates will not be a part of the initial roll out for the Configuration Service.
Reading between the lines: live updates is something that many people at Twitch are extremely passionate about, and is something that we will continue to work towards. We did not want it to block the rollout of the Configuration Service, and we did not want to propose a solution that would be deprecated shortly there after.
The get endpoint is most pertinent for the 10 request per segment per minute rate limit. This is what EBSs use to retrieve broadcaster configuration updates. I’d suggest that this limit is slightly less relevant to the put method.
@tf2casperr, given the incremental nature of service adoption, we will be putting the Configuration Service directly into General Availability. Prior to launch, its functionality should be available for extensions running in local mode in the Developer Rig though.