<story><title>Redcon – Fast Redis-compatible server framework for Go</title><url>https://github.com/tidwall/redcon</url></story><parent_chain><item><author>butabah</author><text>I don&amp;#x27;t see how it&amp;#x27;s useful then. Maybe someone can give me a good use case?&lt;p&gt;redis is already very bare-bones and dead simple to set up and maintain, what more does one want? Wouldn&amp;#x27;t adding more logic into a redis-like environment be a little cumbersome from an architecture perspective?</text></item><item><author>eknkc</author><text>Note that it&amp;#x27;s a redis serialization protocol and tcp server implementation. It&amp;#x27;s up to you to define redis commands such as get, set etc.&lt;p&gt;This can be used coupled with a backend storage to provide custom redis servers.&lt;p&gt;It&amp;#x27;s not a redis implementation by itself.</text></item></parent_chain><comment><author>eknkc</author><text>Could be used for proxying redis connections, be it for clustering or I don&amp;#x27;t know, add sophisticated access control or something.&lt;p&gt;You could expose a memcached cluster as a redis server using this. (Not sure why would you want to do that.. Maybe if you have an existing memcached cluster and have redis client code?)&lt;p&gt;Or you could go crazy and implement the entire set of redis commands on top of sqlite and call it a &amp;quot;strongly persistent redis&amp;quot; or something like that.&lt;p&gt;It&amp;#x27;s just a nice building block, I&amp;#x27;m sure people would find ways to abuse it :)</text></comment>
<story><title>Redcon – Fast Redis-compatible server framework for Go</title><url>https://github.com/tidwall/redcon</url></story><parent_chain><item><author>butabah</author><text>I don&amp;#x27;t see how it&amp;#x27;s useful then. Maybe someone can give me a good use case?&lt;p&gt;redis is already very bare-bones and dead simple to set up and maintain, what more does one want? Wouldn&amp;#x27;t adding more logic into a redis-like environment be a little cumbersome from an architecture perspective?</text></item><item><author>eknkc</author><text>Note that it&amp;#x27;s a redis serialization protocol and tcp server implementation. It&amp;#x27;s up to you to define redis commands such as get, set etc.&lt;p&gt;This can be used coupled with a backend storage to provide custom redis servers.&lt;p&gt;It&amp;#x27;s not a redis implementation by itself.</text></item></parent_chain><comment><author>otterley</author><text>I&amp;#x27;m not sure, either.  By the time you&amp;#x27;ve implemented all the actual Redis functions, there&amp;#x27;s no telling whether the server will be more or less performant than Redis itself.  (Most likely less, since Redis is written in optimized C.)&lt;p&gt;Of course the existing benchmark shows that the example Go implementation is faster.  For one, the Go implementation provided avoids a lot of functionality that the Redis server implements, such as TTL checking.</text></comment>