3 ms·
As http://tech.trello.com/why-we-chose-kafka/ http://tech.trello.com/why-we-chose-kafka/ points out, Redis Streams would be another alternative. It seems still
by vemv 8y ago
As http://tech.trello.com/why-we-chose-kafka/ http://tech.trello.com/why-we-chose-kafka/ points out, Redis Streams would be another alternative. It seems still underdocumented though as it's a recent addition.
I created https://github.com/antirez/redis/issues/5582 https://github.com/antirez/redis/issues/5582 asking what should be a basic, necessary, straightworward question, still no luck
- antirez 8y agoHello vemv, we have time complexities in every stream command, and the reason there is no latency documentation is because it follows the Redis normal latency, that is, like blocking lists or Pub/Sub work: as soon as something is available for consumers waiting, it is immediately sent to the socket of such consumers. So you can expect extremely low latencies without any differences compared to other Redis commands. However I'll try to reply to your question in more details in that issue. Btw what is bad is that you did not find your answers in the Streams intro doc. I'll update that too.
- manigandham 8y agoWhile the documentation gets updated, you can think of it as similar to using a Redis list, wish LPUSH and RPOP.