RedisStore - Using direct Redis commands instead of hash Redis commands - #206

[arvind-bhaskar]

• To avoid iterating all the keys, the max length should not be specified.
• Because of the absence of max length, the size of the Redis hash list increases and instill the memory load in the Redis server.
• Even if the max length is specified, we can use the scan command to iterate through keys 1000 at a time. It optimizes the flow.
• For the namespace, we can prefix the key.
• To overcome this, we can use the direct Redis commands with separate TTL for every key. On the expiration of the TTL, the Redis itself deletes the key.
• We can provide the developers with two different options to use the RedisStore either by hash commands or by direct commands.

This is a fix for the issue
#206

[codecov]

Codecov Report

Merging #216 (55305fb) into master (44d7227) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #216   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           12        13    +1     
  Lines          192       230   +38     
=========================================
+ Hits           192       230   +38     

Impacted Files	Coverage Δ
src/redis-default.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44d7227...55305fb. Read the comment docs.

[ghost]

Hello @arvind-bhaskar!

Thanks for the contribution, would you mind resolving the conflicts and actually remove the dist files from the PR (I'll rebuild everything when I post a release) then I'll gladly merge it 🙂

Thank you!