TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Lark – A REST interface for Redis

35 pointsby voidfilesover 11 years ago

5 comments

dyscreteover 11 years ago
This is just adding an extra layer between your data and redis, which defeats redis' purpose of being fast for particular use cases.
bsg75over 11 years ago
How does this compare (use cases?) to Webdis?<p><a href="http://webd.is/" rel="nofollow">http:&#x2F;&#x2F;webd.is&#x2F;</a>
评论 #6952481 未加载
rafekettover 11 years ago
maybe i&#x27;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.
drdaemanover 11 years ago
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&#x27;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.
评论 #6952032 未加载
notastartupover 11 years ago
what would the benefit of this instead of rolling out your own REST api on Flask?