Redis - An Introduction
•Download as KEY, PDF•
6 likes•2,241 views
This talk gives an introduction into what Redis is, what you can do with it and why it is cool.
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Redis - An Introduction
- 1. Redis Thorsten Böttger Sharesight.co.nz WellRailed 23/05/2012 http://www.flickr.com/photos/linecon0/1085617988
- 5. key-value store http://www.flickr.com/photos/jamesclay/2312912612/
- 7. no document database http://www.flickr.com/photos/linneberg/4481309196/
- 8. no relational database http://www.flickr.com/photos/lencioni/203030529/
- 9. Salvatore Sanfilippo Pieter Noordhuis
- 10. Open Source
- 11. design principle “I see Redis definitely more as a flexible tool than as a solution specialized to solve a specific problem.” — Salvatore Sanfilippo
- 12. Characteristics http://www.flickr.com/photos/gjw/487364375/
- 14. Craftmanship http://www.flickr.com/photos/gte491n/4335439637/
- 16. Love Not like this guy... http://www.flickr.com/photos/brettmorrison/4718717523/
- 17. Alive and kicking +
- 18. Well documented
- 19. Easy to install
- 20. Easy to configure http://www.flickr.com/photos/mag3737/3176598270/
- 21. XML
- 22. plain text # By default Redis does not run as a daemon. Use 'yes' if you need it. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized. daemonize no # When running daemonized, Redis writes a pid file in /var/run/redis.pid by # default. You can specify a custom pid file location here. pidfile /var/run/redis.pid # Accept connections on the specified port, default is 6379. # If port 0 is specified Redis will not listen on a TCP socket. port 6379 # If you want you can bind a single interface, if the bind option is not # specified all the interfaces will listen for incoming connections. # # bind 127.0.0.1 # Specify the path for the unix socket that will be used to listen for # incoming connections. There is no default, so Redis will not listen # on a unix socket when not specified. # # unixsocket /tmp/redis.sock # unixsocketperm 755 # Close the connection after a client is idle for N seconds (0 to disable) timeout 0 # Set server verbosity to 'debug' # it can be one of: # debug (a lot of information, useful for development/testing) # verbose (many rarely useful info, but not a mess like the debug level) # notice (moderately verbose, what you want in production probably) # warning (only very important / critical messages are logged) loglevel notice
- 23. or on-the-fly $ redis-cli CONFIG SET loglevel debug
- 25. Administration
- 26. Replication Master Slave Slave Slave Slave Slave
- 27. Persistence Redis Data Backup Redis Redis Redis Redis Redis time
- 28. Persistence Append-Only File Redis ∂ ∂ ∂ ∂ time
- 29. Security
- 31. Cache Store https://github.com/jodosha/redis-store Session Store https://github.com/mattmatt/redis-session-store Counters stats, API requests per hour, DoS, Spam
- 32. Url Shortener Redis string a6hz89z: https://mysite/ a/very/deep/ link? with=params
- 33. Wizards Redis Form Step 1 hash a: ‘name’ b: ‘email’ Form Step 2 after 3rd step intermediate results ... DB k: ... Form Step 3
- 34. Map-Reduce Redis hash Worker sums[a] Map { Worker sums[b] sums[c] } Reduce Worker
- 35. Job Queue Redis list Rails App Push now 1.hour.ago ... 2.hours.ago Pop Worker Resque https://github.com/defunkt/resque Sidekiq https://github.com/mperham/sidekiq
- 36. Unique Visitors Redis set user A user K user Y
- 37. List of online users Redis set ⌚ user A ⌚ user K ⌚ user Y
- 38. Todo lists Redis sorted set 1. this 2. that 3. ...
- 39. Leaderboard Redis sorted set 7. top 3. middle 1. loser
- 40. Push Notifications Redis Event pubsub channel A Event Publish channel B Pusher Subscribe ... Event
- 41. Chat system Redis pubsub Publish channel A Subscribe Subscribe Publish user A channel B user B
- 42. Communication between Apps Redis pubsub Rails Publish channel A Subscribe Any Subscribe Publish other channel B
- 43. Activity Feed Redis action list } A wrote B is following display A added LTRIM A wrote
- 44. Activity Feed 2 where every user shows up only once Redis action sorted set hash t3: A A: ‘A wrote’ t2: B B: ‘B is following’ t1: C C: ‘C added’
- 45. Tagging Redis hash hash hash book_1 book_2 book_2 name: ... name: ... name: ... author: ... author: ... author: ... set set tag:redis tag:rails 1 2 3
- 47. Limits & drawbacks http://www.flickr.com/photos/36117591@N04/3558894634/
- 48. Big Data
- 49. Scalability
- 50. To the rescue: Clustering Master Master Master consistent Master Master hashing Master Master Master
- 51. It’s not a Database
- 52. Not Exchangeable
- 55. Thank you! Thorsten Böttger @enebo http://mt7.de http://www.flickr.com/photos/analogian/5913840143/ http://Sharesight.co.nz
Editor's Notes
- Kiwi accent, still lose me on the phone\n#bedrooms instead of square meters\nThanks, Driver!\n
- Salvatore Sanfilippo, Pieter Noordhuis, Paul Maritz, Jose Valim, DHH\nthey have something in common\n
- \n
- \n
- NoSQL, REmote DIctionary Server, written in C, single-threaded, all data in memory\n\n...like memcached\n
- advanced data structures\npersistence\n
- supports advanced data structures\nbut not THAT advanced \n
- set-based queries, but not with that highly sophisticated selects or joins or type-supporting\n
- 10.4.2009 initial release\n
- Paul Maritz, CEO vmware\n
- \n
- \n
- how fast is fast? (> 100,000 SETs per second)\n
- following and respecting the Big O notation (describe limiting behaviour, and classify algorithms)\n
- \n
- maintainers care and are very responsive\n
- \n
- \n
- brew install redis, apt packages, standard make\nport 6379\n- no major dependencies\n
- \n
- just kidding\n
- with lots of comments\n
- \n
- lots of clients (redis-rb, hiredis-rb, em-redis)\nnerdy DSL, but follows a logic\nCONSOLE!!!\nhttp://try.redis-db.com/\n
- \n
- slaves are read-only by default\nnon-blocking for master (logging incoming commands)\nnon-blocking for slaves (just a short switch-over)\n\n
- Redis Data Backup (+easier to backup, +fast recover, -may lose data, -fork() slow for bigdata)\nsave 900 1\nsave 300 10\nsave 60 10000\n
- Append-Only File (+readable, +faster to write, -bigger file, maybe slower if writing too often)\nrun both!\n
- Redis is designed to be accessed by trusted clients inside trusted environments\n-> bind to local address\n-> Auth is possible\n-> strings are not escaped in any way\n-> rename certain commands\n\n
- \n
- \n
- based on Redis strings\nuseful for permanent links or when urls get too long\nor to obsfuscate urls\n\n
- based on Redis hashes\n
- based on Redis hashes\n\n\n
- based on Redis lists (FIFO)\n
- based on Redis sets\n\n\n
- based on Redis sets with expire\n\n\n
- based on Redis sorted sets\nwhere you update a lot of items at once\n\n
- based on Redis sorted sets\nwhere you update a lot of items at once\n\n
- based on Redis pubsub\n
- based on Redis pubsub\n\n
- based on Redis pubsub\n\n
- based on Redis lists\nLTRIM makes sure the list doesn’t get longer\n\n\n
- based on Redis sorted set, in combi with a Hash\n\n\n\n
- in combination with sort\n\n\n
- \n
- \n
- kept in memory\n100M entries => 16GB RAM\n
- not seamless\n- short blockings when syncing with slaves\n- just one master\n
- every node has some portion of the data\n- native cluster is in the works\n- redis-rb simulates this\n
- don’t try to treat it that way, it’s not a replacement\n- data structures not flexible enough\n- queries not detailed enough\n
- DSL is unique\n
- \n
- \n
- \n