From 25af3b876996f564b710b85b399dc2df16edc804 Mon Sep 17 00:00:00 2001 From: Julio Capote Date: Tue, 6 Nov 2018 17:03:15 -0500 Subject: fix rendering issue here --- content/post/2013-07-28-playing-with-groupcache.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/post/2013-07-28-playing-with-groupcache.markdown') diff --git a/content/post/2013-07-28-playing-with-groupcache.markdown b/content/post/2013-07-28-playing-with-groupcache.markdown index 550a4da..6cb7102 100644 --- a/content/post/2013-07-28-playing-with-groupcache.markdown +++ b/content/post/2013-07-28-playing-with-groupcache.markdown @@ -11,7 +11,7 @@ This week, [@bradfitz](http://twitter.com/bradfitz) (of memcached fame) released By the way, I **strongly** recommend you go through the [slides](http://talks.golang.org/2013/oscon-dl.slide#1) and [README](http://github.com/golang/groupcache) before going further. -## What groupcache isn't +## What groupcache is not After downloading it (without reading the [slides](http://talks.golang.org/2013/oscon-dl.slide#1)), I instinctively searched around for how to actually start the server(s), only to find nothing. Turns out, groupcache is more of a _library_ with a server built in, rather than a traditional standalone server. Another important consideration is that theres **no support for set/update/evict operations**, all you get is GET. Really fast, consistent, distributed GET's. ## What it is -- cgit v1.2.3