4 ms·
It's widespread because they can be used to store values (ephemerally.) For things like session tokens that need to be accessed quickly and often, but change ra
by thirsteh 12y ago
It's widespread because they can be used to store values (ephemerally.) For things like session tokens that need to be accessed quickly and often, but change rarely, using a cache (e.g. in front of an RDBMS) is often a decent choice.
What amazes me is that the best argument against using a cache is "your cache server might run out of memory."
- facorreia 12y agoWhen stored only in memory, the sessions can be evicted at any time for any number of reasons, from eviction to node failure. This would lead to data loss (in this case, session data). Using a cache on top of a permanent data store is the traditional way to use it, for accelerating access, but without risking data loss in case the cache is lost.