The Twitch Configuration Service; store persistent data and reduce traffic to your backend


#1

Today we’re announcing the Twitch Configuration Service.

Configuration Service removes the burden of writing a backend to store persistent channel- and Extension-specific data. Additionally, it provides this data to the front-end on extension load, reducing traffic to your Extension backend for this scenario. This means developers can spend more time building a great user experience. In short, with Configuration Service, we’re unlocking a developer’s ability to build better Extensions faster.

We believe that streamers and viewers will benefit greatly (and use Extensions more) from the increased functionality and stability that Configuration Services provides them. For developers, we hope this will motivate them to build more Extensions knowing that they can do so faster and easier than before without having to worry about investing and building costly back-end systems.

There are many ways to learn and get started with Configuration Service.


[x-post] The Twitch Configuration Service
Viewer List in Twitch Configuration Service