Investigate redis streams for the backplane implementation

[davidfowl]

Investigate redis streams https://redis.io/topics/streams-intro as a backplane.

Support coming in SS.Redis: StackExchange/StackExchange.Redis#860

[analogrelay]

🙄

[BrennanConroy]

What reasons?
Cause it's new?
Cause it has replayability?
Cause it's faster?

[mgravell]

Now available in the 2.0 branch, anything later than 2.0.0-alpha.86 on nuget; we will also do a 1.* drop soon

[yzorg]

What reasons?
Cause it's new?
Cause it has replayability?
Cause it's faster?

@BrennanConroy In short: yes, "replayability" and pub/sub.

Which is not true of other Redis types/structures. For example you can have a list (can contain full history, but no live notifications) or a pub/sub topic (subscribers get notified in real-time, but no history). It looks like Redis streams provide both, ala Kafka.

Faster? I'll leave that to maintainers, but if SignalR no longer has to update separate list and pub/sub topic per message, it has potential to be more efficient, possibly faster.

[davidfowl]

Faster? I'll leave that to maintainers, but if SignalR no longer has to update separate list and pub/sub topic per message, it has potential to be more efficient, possibly faster.

We don't use lists today, we use pub/sub exclusively.

Redis streams would enable a bit more durability and it would scale out better (redis pub/sub doesn't scale very well today in redis cluster).

[davidfowl]

I think we should look at this for 3.0.