Actually, I don't see any reinvention of Erlang's core features here:
- Erlang: a functional language based on actor model that allows to create distributed applications easily as actors don't share state (plus much more that I won't mention here for the sake of brevity). To share state among various Erlang clusters you have to use something like Mnesia (bundled with Erlang stdlib) or Riak (distributed database built using Erlang).
- Redis Cluster: a way to distribute state among multiple Redis (a simple database application) nodes in a manner transparent for the applications using Redis.
Like execution is more important then idea in a startup, implementation in the right "scope" and with the right tradeoffs is more important than idea in a software system. So while for sure Redis Cluster will look a lot like any other distributed hash table I think it is important that we implement it inside our system, with our system language, and with Redis specific tradeoffs.
- Erlang: a functional language based on actor model that allows to create distributed applications easily as actors don't share state (plus much more that I won't mention here for the sake of brevity). To share state among various Erlang clusters you have to use something like Mnesia (bundled with Erlang stdlib) or Riak (distributed database built using Erlang).
- Redis Cluster: a way to distribute state among multiple Redis (a simple database application) nodes in a manner transparent for the applications using Redis.