Thanks for contribution!
My initial plans was to implement this cache application as library, meaning that each client application is responsible to inject "cache instance" to their supervisor tree but "default" cache looks reasonable to me.

BTW, the current implementation maintain two ETS tables per cache. One is hash-table with O(1) read/write access but another TTL index with O(log N). Therefore, cache read/write performance is bound to TTL index but there is ability to define custom TTL per item with precise granularity.

After the discussion on the Erlang mailing list, I've created experimental branch where TTL index is dropped... I need to share that branch here.

• Dmitry