I actually did understand that and I think it’s super cool from a technical perspective. I was just curious as to the use case where this was a strong contender to beat out the built-in stuff you can get from Redis server. It’s a “small” implementation but you still have to test it and own it throughtout the lifecycle of the product that’s using it.
It's pretty common that you won't have a specific use case in mind when learning something new, but I've often found that later it ends up fitting in somehow.