If you use Twemproxy, what you get is automatic sharding, without
automatic rebalancing and fault tolerance.
So my suggestion is that that your team should evaluate Redis Cluster
as it is in the current beta for automatic sharding of data + fault
tolerance, and avoid for now to use what Twemproxy would not allow
anyway, like online add/removal of nodes or live resharding of data.
You can use those advanced features later maybe, as the project gets
more stable.
So if you find that for your uses Redis Cluster is working well during
the next weeks, you may start directly with it.
Otherwise if you find the project to be still to immature for your
users, you may go for Twemproxy and upgrade to Redis Cluster later.
Cheers,
Salvatore
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
redis-db+u...@googlegroups.com.
> To post to this group, send email to
redi...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/redis-db.
> For more options, visit
https://groups.google.com/d/optout.
--
Salvatore 'antirez' Sanfilippo
open source developer - GoPivotal
http://invece.org
To "attack a straw man" is to create the illusion of having refuted a
proposition by replacing it with a superficially similar yet
unequivalent proposition (the "straw man"), and to refute it
— Wikipedia (Straw man page)