ernat.blogg.se - Twitch labs

| Request(s) | => | Application Load Balancer | => | Auto Scaling | => | Launch Application Server(s) | By setting Auto scaling policy, it will automatically put new server in place depending on the traffic or load. So it can be easily deployed with docker or a webserver(apach2/ngnix) and PHP, which can be further automated through any CI/CD tool like Jenkins to automate the build process for deployment.Īnd to talk about the architecture, so in AWS context, I will use AWS Auto Scaling service, which ensures the high availablity of the system.

How would you deploy the above on AWS? (ideally a rough architecture diagram will help)Īs already mentioned above, this project has very few dependency.

Hence it is un-documented and so it can change any time.Īdditionally please answer following questions at the bottom of your README: On home.php, you will be able to see top 10 events of logged in OR searched user.Īccording to this, Twitch don't have official events api for third party use. This pageĭoesn’t poll the backend and rather leverages web sockets and relevant Twitch API.ĭone. The second/streamer page shows an embedded livestream, chat and list of 10 most recent events for your favorite streamer.

And by default it shows live chat window and upcoming events of the logged in user.

After successful login, it redirects user to home.php where they can search their favorite streamer by name. So first page lets the user to login with his/her Twitch account. Listener which listens to all events for given streamer.ĭone. The first/home page lets a user login with Twitch and set their favorite Twitch streamer name. You are required to build an application which exposes two simple pages to the browser Change clientId, clientSecret, redirectUri in classes/twitch.php Or one can even use PHP's official docker image. PHP 7+ (with required extensions enabled)