|Sent on:||Friday, March 14, 2014 10:22 AM|
I'm delighted to say that today marks the day of exactly 3 months since I started this group on meetup.com. To celebrate the occasion I'm sending out our first (hopefully monthly) newsletter.
We had three live meetups already and judging by your ratings they were off the hook! As you might have seen the next meetup is going to take place on 28th of March in Kiberpipa and it will be something completely different. What I mean by that is that this time there will be talks. @otobrglez will say a few things about RSpec/TDD bad practices and @mfilej will talk why we are afraid of deleting our own code. There might also be some lightning talks and if you have something to talk about please let me know, I'm sure we all would love to hear it.
Redis is a networked key-value data store. Apart from strings (blobs) in other popular key-value stores like Riak or Memcached, the values in Redis can also be hashes, lists and (sorted) sets. Redis writes to memory, so it is fast, but it also supports durability via an append-only log and will work as a cluster in the near future. Installation is quite simple, be it via apt, homebrew or compiling from source and there is also a plethora of online hosting options. You can try Redis' commands online.
You can use Redis with Ruby/Rails to roll your own custom persistence layer but that is probably not its primary purpose. Rather than that, you can use it in addition to a main database e.g. as a session store, which comes in handy if you need to store a lot of information in session, want a shared session across multiple Rails instances or just want to avoid the pain of implementing the "cookie disclaimer" imposed by ZEKom-1. There are also several options which expose Redis also as a cache store for model layer, view layer or http caching. While Memcached could also be used in both of these cases, there is almost no escaping Redis when it comes to serious background jobs processing, as both Resque and Sidekiq depend on it. Last, but not least, Redis can be inserted into Rails' i18n backend chain to read and write translations at runtime.
So, if you're not already using Redis, give it a try and give us some feedback!
Just a reminder that O'Reilly Media is supporting our user group with two perks:
Oh, and do spread the word about Ruby and our meetup to your friends (and/or foes). The more the merrier :)