Add List-Backed Redis Message Group Store for QueueChannel Use [INT-3325]

[spring-operator]

Gary Russell opened INT-3325 and commented

The current RedisMessageGroupStore maintains all messages (for a group) under a single key (the group id). This is not particularly efficient when the store is used to back a QueueChannel, especially if messages accumulate in the channel.

Implement a RedisChannelMessageGroupStore that is specialized for this purpose, backed by LIST keys which are LPUSH ed and RPOP ed.

A similar optimization was previously made in JDBC.

---

Issue Links:

• Message store option is not available for priority-queue channel [INT-1870] #5858 Message store option is not available for priority-queue channel

Referenced from: pull request #1084

[spring-operator]

Artem Bilan commented

Great!
Should we take a look to other MessageStore implementations for the same purpose?

[spring-operator]

Gary Russell commented

I don't think, for example, that MongoDb has an equivalent.

I just happened to notice this while researching an answer to a forum post.

I do see that Gemfire has something called a RegionQueue, so perhaps that's another candidate.

[spring-operator]

Artem Bilan commented

What is bad the RedisList solution will liquidate the priority ability for PriorityChannel...

[spring-operator]

Gary Russell commented

Prototype RedisChannelPriorityMessageStore here... garyrussell@d09a758

It supports 10 priorities (0-9) + no priority by using up to 11 discrete LIST s for each channel.