Looking for an optimal setup for a stream directory

[BarryCarlyon]

@Kodiak

The last point is a bit of a hanging up for because of the limited number of api calls a single client id can make. If I say for example have 30 people all hitting the stream root page at the same time that’s roughly 30 api calls. Some solutions:

If you create a App Access Token, you get 120 API calls.

Or you can make the Client/Browser do the API calls as limits are by ClientID/IP KeyPair. So 30 requests per browser using your site… But I’d redis cache and use that data. But I wouldn’t do that myself…

@Kodiak

I can cache the result in the backend using redis and clear the cache If I get a stream up / down notification.

This is the best option which is what I do. I grab a incoming stream webhook and throw it in Redis. So I refer to Redis instead of API. It’s also quicker/more performant.