5 ms·

We expand and shrink clusters in membase under heavy load with no issues. The worst thing that happens is that it takes longer some times. There is no inconsi

by dlsspy 16y ago

We expand and shrink clusters in membase under heavy load with no issues. The worst thing that happens is that it takes longer some times. There is no inconsistency. It doesn't look like redis is doing exactly what we're doing, but since it's been doing it well for a long time now with plenty of documentation, I'm hoping the knowledge we've shared about it can help others learn how to do similar things.

antirez 16y ago
To be honest when I saw the membase design what I thought was: hey, this is from the redis cluster design (that predates membase announcement a lot). But then I realized that it's pretty common to invent the same things. You should try doing the same, especially since the idea was made public by Redis before. Check yourself in the git history.
- dlsspy 16y ago
  The blog post is from June, but the code I'm talking about predates redis by about three years.
  - antirez 16y ago
    "But then I realized that it's pretty common to invent the same things. You should try doing the same". That said, I really don't care at all. I want to build stuff that work, I want to have fun, understand new things. This is why I build Redis.
  - mythz 16y ago
    "I'm hoping the knowledge we've shared about it can help others learn how to do similar things." "The blog post is from June, but the code I'm talking about predates redis by about three years." @dippsy what exactly are you insinuating here? It sounds like your suggesting #Redis somehow has borrowed/learned from concepts in your unreleased code?? It's actually quite rude.
    - janl 16y ago
      No, he was replying to @antirez request of "Check yourself in the git history". I don't think anybody is insinuating anything here. The same solution to a common problem has been found independently. This happens all the time (See the Erlang process model and the Actor model e.g.). Down the line, this isn't even important. Can we move along now and build some awesome databases?
      - mythz 16y ago
        yes please.

by dlsspy 16y ago

antirez 16y ago

To be honest when I saw the membase design what I thought was: hey, this is from the redis cluster design (that predates membase announcement a lot). But then I realized that it's pretty common to invent the same things. You should try doing the same, especially since the idea was made public by Redis before. Check yourself in the git history.

dlsspy 16y ago
The blog post is from June, but the code I'm talking about predates redis by about three years.
- antirez 16y ago
  "But then I realized that it's pretty common to invent the same things. You should try doing the same". That said, I really don't care at all. I want to build stuff that work, I want to have fun, understand new things. This is why I build Redis.
- mythz 16y ago
  "I'm hoping the knowledge we've shared about it can help others learn how to do similar things." "The blog post is from June, but the code I'm talking about predates redis by about three years." @dippsy what exactly are you insinuating here? It sounds like your suggesting #Redis somehow has borrowed/learned from concepts in your unreleased code?? It's actually quite rude.
  - janl 16y ago
    No, he was replying to @antirez request of "Check yourself in the git history". I don't think anybody is insinuating anything here. The same solution to a common problem has been found independently. This happens all the time (See the Erlang process model and the Actor model e.g.). Down the line, this isn't even important. Can we move along now and build some awesome databases?
    - mythz 16y ago
      yes please.