4 ms·

Oh, weird in what way? I was considering using it for horizontal redis scaling recently, under the impression that redis cluster was further away from release

• seiji 12y ago
  The code is just strange. To support Redis, it has a 2,500 line Redis adapter. It has special cases for each Redis command because it doesn't extract key position information from Redis directly. Plus, despite the name and where it's hosted, Twitter never used it in production for Redis. Redis support was just added "because we can." It probably works for very direct use cases, but it's one of those things that could probably bite you very severely under edge cases, and you'd be left on your own to figure out what happened.
  • litewulf 12y ago
    We run twemproxy over about a terabyte of data in Redis, and haven't had any problems...
  • zamio 12y ago
    pinterest, snapshot, vine, wanelo use the twemproxy in prod for redis
    • seiji 12y ago
      Well, companies also use ejabberd, but that doesn't make ejabberd a valid piece of software either. Then there's the massive problem of "everyone" using MongoDB and we know how much pain _that_ sucker causes. Playing popularity contests with software isn't useful. People install software either because of social reasons ("I don't know how anything works, but I hear everybody is using X, so I'm going to use X too!") or because they need the functionality ("redis is AMAZING at 30 different things!"). If install base at well known companies were a valid measure, we'd all be using Windows laptops while talking into our Kin and squirting our Zunes all over each other.