RedisConfNano – A Look Back
Last month, more than 50 users and developers got together at RedisConfNano in Portland, Ore. to see Salvatore Sanfilippo (@antirez) talk about future development paths for Redis, and to discover more about how the Redis community is pushing usage forward.
RedisToGo and Rackspace hosted the one-day event.
Here are some highlights of the day (and over the next week or so we will post videos of some of the presentations).
The Morning – Voodoo Doughnuts and Developer Time
It wouldn’t be Portland without Voodoo Doughnuts. We started the day with stacks of pink doughnut boxes and spent time in groups dishing on Redis use cases and problems. The RedisToGo team had some great conversations with companies such as moot.it, which is using Redis as its primary datastore and Regenology, a UK company with a time lapse photography service that uses Redis on a camera-attached Raspberry Pi for queuing and messaging.
The Afternoon – The Main Event – Antirez & Uber
Uber Takes The Stage
After an obligatory Portland Food Truck lunch – again, when in Portland! – we returned to see Uber’s Amos Baretto present “Building a Distributed State Machine with Node.js and Redis.”
Uber uses Redis for its driver dispatch service. Uber investigated Redis after experiencing problems scaling its datastore architecture. With the holiday season fast approaching, it had some decisions to make. So why Redis? From Amos’ presentation:
“Mongo couldn’t keep up with GPS points, node-mongodb-native was buggy with regard to replica sets… and we heard it was fast, so why not? [And we were] already using as a cache.”
Today, Uber’s architecture serves roughly 200 dispatch workers and still growing. Uber serves more than 40 cities and Redis is now its datastore, not a cache.
A Short Term Plan From Antirez
Next up, Antirez spoke about “A short term plan for Redis.”
Salvatore hit on a number of development themes for Redis including Redis Cluster. Here are three potential development areas he mentioned for future versions of Redis during his presentation:
1. Persistence – combine AOF and RDB formats; gain faster AOF rewrites and reloads; one format is better than two.
2. Redis Doctor – an evolution of INFO; check the latency of many operations; store metrics as a time series; tell the user if there are problems
3. Sentinel – here to stay but needs changes; use Redis Cluster algorithms (versioned changes); use persistent state like Redis Cluster
Or, he suggested, just use Redis Cluster itself, only enabling monitoring and failover.
Overall, it was a packed day with enough Redis insight to make whet your appetite for Redis’ bright future.
If you want to see more from the presentations, stay tuned as we will post videos of the day over the next week or so.
Finally, thanks to Ben Arent for organizing and turning around a great event at the last minute.