by dyscrete on 12/23/13, 2:01 AM
This is just adding an extra layer between your data and redis, which defeats redis' purpose of being fast for particular use cases.
by bsg75 on 12/23/13, 12:30 AM
by rafekett on 12/23/13, 1:30 AM
maybe i'm being a downer, but i feel like the latency of an HTTP request defeats the purpose of using redis in 99% of use cases.
by drdaeman on 12/22/13, 9:43 PM
While this may be somewhat useful (particularly due to more fine-grained auth), I believe Redis is already being mostly-RESTful as REST is not about transporting data using HTTP. It's - going by Wikipedia list on REST constraitns - client-server (check), mostly stateless (check; states are only for pubsub and transactions), cacheable (uhm... partially), layered (check), and even has code-on-demand features.
by notastartup on 12/22/13, 11:06 PM
what would the benefit of this instead of rolling out your own REST api on Flask?