[erlang-questions] Caching server

Klaus Trainer <>
Sat Feb 19 15:10:00 CET 2011


Let me throw another one into the ring that I like due to its
simplicity: Filipe Manana's term_cache.

Depending on your needs and preferences, you can choose one of four
implementations.

cit. README.md:

1. term_cache_ets: keys and values are stored in ets tables (one ordered set ets table plus on set ets table);

2. term_cache_trees: keys and values are stored in trees (Erlang module gb_trees, 1 tree for keys, 1 tree for values);

3. term_cache_pdict: keys are stored in a tree and values are stored in the process dictionary;

4. term_cache_dict: keys are stored in a tree and values in a dictionary (Erlang dict module).''


https://github.com/fdmanana/term_cache


On Sat, 2011-02-19 at 14:11 +0100, nox wrote:
> I don't have the answer to your question, but if you want to explore that idea you could take a look at pcache [1] and ecache [2].
> 
> Regards.
> 
> [1] https://github.com/mattsta/pcache
> [2] https://github.com/mattsta/ecache
> 
> Le 19 févr. 2011 à 03:19, Nicholas Wieland a écrit :
> 
> > Hi *, I'm reading the Manning book.
> > My question is very simple: a full chapter of the book is devoted to the implementation of a simple caching server. The author, if I got it correctly, at one point states that in Erlang, thanks to its lightweight processes, it's ok to have a caching server that spawns a process for every key/value pair.
> > Of course I don't expect that the example in the book is a production ready implementation, but I would like to ask if it would be possible for an architecture like this to be production ready (say, something like Redis), or if I should take it with a pinch of salt, only as a demonstration.
> > This thing made me curious because there's no language or technology that would permit something like this, hence my question :)
> > 
> > TIA,
> > -- 
> > Nicholas Wieland
> > 
> > StyleJam BDFL
> > 
> > The only "intuitive" interface is the nipple. After that it's all learned. – Bruce Ediger
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > ________________________________________________________________
> > erlang-questions (at) erlang.org mailing list.
> > See http://www.erlang.org/faq.html
> > To unsubscribe; mailto:
> > 
> 
> --
> Anthony Ramine
> Dev:Extend
> http://dev-extend.eu
> 
> 
> 
> 
> 
> ________________________________________________________________
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:
> 




More information about the erlang-questions mailing list