From 23661b37bd4e17a3dfc72d22d6ada37dd4e5e1a9 Mon Sep 17 00:00:00 2001 From: Patrick Mylund Nielsen Date: Fri, 22 Jun 2012 03:11:31 +0100 Subject: [PATCH] Point out why using go-cache might be desirable --- README | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/README b/README index 3e70f88..3e99d04 100644 --- a/README +++ b/README @@ -1,11 +1,14 @@ go-cache is an in-memory key:value store/cache similar to memcached that is -suitable for applications running on a single machine. Any object can be stored, -for a given duration or forever, and the cache can be safely used by multiple -goroutines. +suitable for applications running on a single machine. Its major advantage is +that, being essentially a thread-safe map[string]interface{} with expiration +times, it doesn't need to serialize or transmit its contents over the network. + +Any object can be stored, for a given duration or forever, and the cache can be +safely used by multiple goroutines. Although go-cache isn't meant to be used as a persistent datastore, the entire -cache may be saved to and loaded from a file (or any io.Reader/Writer) to recover -from downtime quickly. +cache may be saved to and loaded from a file (or any io.Reader/Writer) to +recover from downtime quickly. == Installation