(6) Robey* Pointer, and I was the third guy in the room… We had already chosen the Yahoo! “Feeding Frenzy” design at that point, had started the design using Redis based on experience I gained at an previous company, and were working out the data structures using what was available in Redis, as I recall. We put together a few PRs against Redis shortly thereafter to make Redis a practical option for Haplocheirus in production.
There’s more to say of course, but we appreciated having these sorts of conversations with upstream authors of software we adopted at Twitter whenever possible.
Thank you so much for this comment! Exactly, the chat was mostly a validation thing. And I remember that even back then we had identified an idea that went into the Twitter fork of Redis very soon (implemented by Yao maybe?), and later into official Redis itself: lists with many collapsed elements per node.
Thanks for laying the groundwork for us with Redis!
Before I moved on to working on our Ruby VM, I was doing the work on our Redis fork for Haplo. Robey was working on the routing middleware in Scala.
Yao would have taken over from me when the cache team sprang into existence around that same time, with the emergence of twemproxy and twemcache. Most anything written in C would eventually land on her team.
Comments
(6) Robey* Pointer, and I was the third guy in the room… We had already chosen the Yahoo! “Feeding Frenzy” design at that point, had started the design using Redis based on experience I gained at an previous company, and were working out the data structures using what was available in Redis, as I recall. We put together a few PRs against Redis shortly thereafter to make Redis a practical option for Haplocheirus in production.
There’s more to say of course, but we appreciated having these sorts of conversations with upstream authors of software we adopted at Twitter whenever possible.
Thank you so much for this comment! Exactly, the chat was mostly a validation thing. And I remember that even back then we had identified an idea that went into the Twitter fork of Redis very soon (implemented by Yao maybe?), and later into official Redis itself: lists with many collapsed elements per node.
Thanks for laying the groundwork for us with Redis!
Before I moved on to working on our Ruby VM, I was doing the work on our Redis fork for Haplo. Robey was working on the routing middleware in Scala.
Yao would have taken over from me when the cache team sprang into existence around that same time, with the emergence of twemproxy and twemcache. Most anything written in C would eventually land on her team.
Feeding frenzy is referenced here: http://highscalability.com/blog/2012/1/17/paper-feeding-fren...