travellingprog
commented
11 years ago Since I'm not sure which computations you're referring to, would a cache between our frontend and backend, like Varnish, help in this case?
Open shuhaowu opened 11 years ago
travellingprog
commented
11 years ago Since I'm not sure which computations you're referring to, would a cache between our frontend and backend, like Varnish, help in this case?
shuhaowu
commented
11 years ago Varnish is really cool. I'll look into it, but that's another layer for deployment.
Redis with Flask-Cache1 is cool too. The filtering computations could be relatively expensive (if we move to Riak later we could use its map reduce feature)
Shuhao
On 06/07/2013 11:01 AM, Erick Cardenas-Mendez wrote:
Since I'm not sure which computations you're referring to, would a cache between our frontend and backend, like Varnish, help in this case?
Reply to this email directly or view it on GitHub: https://github.com/shuhaowu/projecto/issues/6#issuecomment-19122980
travellingprog
commented
11 years ago Man, I'm gonna be a Flask expert by the time this project gets done lol
shuhaowu
commented
11 years ago Flask is really easy actually. It's only about 1000 lines of code itself (werkzeug is a little bit more, but still). So it shouldn't be hard to be an expert (unlike BIG frameworks like RoR, Django, and Angular ;) )
:D
Shuhao
On 06/07/2013 11:09 AM, Erick Cardenas-Mendez wrote:
Man, I'm gonna be a Flask expert by the time this project gets done lol
Reply to this email directly or view it on GitHub: https://github.com/shuhaowu/projecto/issues/6#issuecomment-19123449
Some of the computations are pretty computationally expensive. We don't use things like a SQL database so that doesn't help.
Simple caches should work fine until we hit problems.