Re-architecture - Githubissues

jacobmort commented 5 years ago

Right now the pieces are a webserver (hosts badge images and html), react/web3 frontend, and firebase DB. This has a big drawback of needing the front end to communicate status of the quantstamp audit to the backend. So users would need to sit at the page for 4+ minutes or refresh periodically.

This is the new architecture I'm kicking around: img_20181010_083325

Benefits:

Node watches ethereum events so user doesn't have to in browser
Removes dedicated webserver
Heroku goes to sleep and causes badge images to be slow to load or timeout. Hosting on s3 will mean they are always available.

jacobmort commented 5 years ago

Serverless functions will need to save quanstamp report results json somewhere.

jacobmort commented 5 years ago

This is too big for an issue- moving to project board

jacobmort / QuantstampBadge

Re-architecture #1