Why

Test redis on Heroku

What to Do

Deploy a redis on heroku, and test the connection to it locally and from remote

Why

Test the browser fingerprint. Also, we want to limit the number of seuqence up to 4 per day

What to do

When the client requires /magicnumbers.json, the client should send a fingerprint of the browser. The server shall then store

• this fingerprint
• the ip of the client
• the date and time

Why

The backend and the frontend will run on heroku, so...

What to do

• Deploy the application on Heroku exposing an endpoint HTTP GET /magicnumbers that returns a JSON response {score: <float[0,100]>, numbers:[<integer[1,90]..5>]}

Why

To try Redis on Heroku and to collect some statistics

What to Do

• Launch Redis on Heroku
• Add a counter to track the number of request received by single ip

Why

We run our service under Acceptable Use Policy - each user can run up to 4 requests per day

What to Do

• Add a fingerprinting on the client
• Send the fingerprint as a cookie to each request to the server
• After 4 requests, the bakend reject the request. In this case the user can retrieve the list of its number calling a new endpoint at HTTP GET /mynumbers

Why

We want our great service to be used by other people! We need a way for them to interact with this great tool!

What to do

• Add a landing page as static content
• This page should have a button that if pressed opens a pop-up with a sequence generated by magicnumber

Why