@felixgallo @bpot @mxavier @mperham it's using asynchronous replication without 2PC/quorum writes, so yes: http://aphyr.com/posts/283-call-me-maybe-redis …
-
-
@bascule@felixgallo@mxavier@mperham kafka has its own data loss issueshttps://twitter.com/aphyr/status/370450880107016192 … -
@bpot@felixgallo@mxavier@mperham apples and oranges. Kafka has a real distribution strategy. Redis does not -
@bascule@bpot@felixgallo@mxavier from the users perspective, data loss is data loss. -
@mperham@bpot@felixgallo@mxavier every time you pop from a Redis list you risk data loss. Reading from Kafka has no side effects
End of conversation
New conversation -
-
-
-
@felixgallo@bpot@mxavier@mperham the more general problems are "high availability" and "single points of failure" -
@bascule@felixgallo@bpot@mperham > that redis is not good for any use cases. Now you're just focusing on use cases redis doesn't target. -
@mxavier@felixgallo@bpot@mperham Redis wasn't designed to be a distributed system but everyone is almost certainly using it as one -
@bascule@felixgallo@bpot@mperham That's quite a leap/assumption, but I guess no more so than your assumption that redis users are novices
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.