Currently only works by merging/replacing with maps and then pull/push-ing.

In the future, this should implement Access, Enumerable and Collectable - meaning this could then be used with Elixir’s Enum w/o limitations. These should work independant of whether or not local caching is used.

You can let this cache its values locally and commit them back to the repo on demand. This doesn’t handle inconsistencies etc. - the use case is to have a relatively longer term storage (redis semantics) for process related data. In case a process gets restarted etc. it can quickly commit and refetch its state later on. Obviously gets tricky if multiple processes use the same redis-hash.

Conflicts and race conditions are tried to be avoided, but essentially this is a very simplistic grow-only set. (You can delete the whole thing, but not single entries for now)

This will fetch the state of the hash when it is created, and will try to keep it up to date with the external version whenever you do pulls and pushes to redis.