<story><title>KeyDB – A Multithreaded Fork of Redis</title><url>https://docs.keydb.dev/</url></story><parent_chain></parent_chain><comment><author>dig1</author><text>Without the intention to undermine anyone&amp;#x27;s work (and I truly appreciate the work the KeyDB guys did), I would not use this (in production) unless I see Jepsen test results [1] either by Kyle or someone supervised by Kyle. But, unfortunately, databases are complex enough and distributed systems even more, and I&amp;#x27;ve lost many sleepless nights debugging obscure alternatives that claimed to be faster in edge cases. And the worst thing is that these projects get abandoned by the original authors after a few years, leaving me with (to quote a movie) &amp;quot;a big bag of odor&amp;quot;.&lt;p&gt;I see databases as a programming languages - if they have a proven track record of frequent releases and responsive authors after 5-7 years, they are usable for wider adoption.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jepsen.io&amp;#x2F;analyses&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jepsen.io&amp;#x2F;analyses&lt;/a&gt;</text></comment>
<story><title>KeyDB – A Multithreaded Fork of Redis</title><url>https://docs.keydb.dev/</url></story><parent_chain></parent_chain><comment><author>mgaunard</author><text>Whenever I see someone arguing their code is better because it&amp;#x27;s multithreaded, I cringe.&lt;p&gt;Most developers cannot do multithreading correctly, and unless you&amp;#x27;re particularly good about it it&amp;#x27;s just going to introduce not only lots of bugs but also performance problems.&lt;p&gt;The only folks in that space that seem to do it well are ScyllaDB.</text></comment>