Yes for a lot of applications - even ones with lots of nodes - this makes sense - just let each node build and manage its own cache and you’ll still have lots of cache hits. But that isn’t a distributed cache. cachex does look like an excellent system.
My original interest in this space was a distributed session store - which is another use case where people turn to memcached and redis today and that is why there are Plugs to use both of those as backing stores. For this use case there must be strong consistency. I don’t see any great option for it. Building something backed by mnesia or ets - possibly leveraging riak_kv - does seem worthwhile to me.
