My week on redis

1. PERSISTING
DATA
It's literally going to kill me
Brian Best - github.com/brianbest

2. REDIS
In memory database
system

3. THE GOOD
• Set my server up as git
remote. No more
cyberduck.

4. PROBLEMS
• Installation guilds suck
• Documentation for node module sketchy
• Sidetracked

8. SOLUTION

9. LAST NIGHT

10. MAKE THE CLIENT DO
IT The server can stay on the beach

11. INDEX.JS (SERVER)
Capture Messages - Save to DB
socket.on("chat message", function(msg){
//Print message to db
client.rpush('mes1', msg, redis.print);
io.emit('chat message', msg);
});
Send Messages On Connection As Array
client.lrange(['mes1',0,-1], function (err, reply) {
io.emit('past messages', reply);
}, redis.print);

12. PURE.JS (CLIENT)
Catch array from DB
socket.on('past messages', function(msg){
pastPast(msg);
});
function pastPast(msg){
var messages = msg;
for(var i = 0; i < messages.length; i++){
$('#msg_area').prepend($('<p>').text(messages[i]));
}
}

13. NOW WHAT
• Data needs to save to
disk
• UI needs help

14. I'M FLYING AWAY
FROM YOU PEOPLE
But more on that next week