4 ms·

Thanks for the clarification. It's great to hear that scripting will reduce the need to create new commands. I'm sure some people have been getting slightly ann

by kijin 15y ago

Thanks for the clarification. It's great to hear that scripting will reduce the need to create new commands. I'm sure some people have been getting slightly annoyed with the rapid proliferation of Redis commands, which already number well over 100. Can't remember them all!

xnxn 15y ago
That reminds me, I'd really like to see an official wiki (or just a simple pastebin-like thing like the Flask snippets site) for Redis scripts, use cases, best practices... I've seen quite a few blog posts that highlight some amazing way to use Redis and it would be very helpful to have them all in one place.
- edanm 15y ago
  I agree. But I would also like to add that Redis's documentation is one of the best I've seen anywhere. Incredibly easy to find information about any command.
- catwell 15y ago
  Nothing official but you can fork https://github.com/mkrecny/redis-extend https://github.com/mkrecny/redis-extend and make a pull request. There was also http://evalsha.com/ http://evalsha.com/ which looked cool but went nowhere...
doug1001 15y ago
"rapid proliferation of Redis commands"? If the total is indeed, well over 100, that figure is spread among completely different data structures--lists, hashes, strings, sets, sorted sets--so i'm not sure it's even meaningful to compare the number of commands in redis with the number in some other DB which is based on a single data structure. Also, the increase in the number of commands might indeed just most reflect the incremental addition of new data structures to redis since its beginning (just strings, i believe).