<story><title>Jepsen: Dgraph 1.0.2</title><url>https://jepsen.io/analyses/dgraph-1-0-2</url></story><parent_chain></parent_chain><comment><author>mrjn</author><text>Author of &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;dgraph.io&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;dgraph.io&lt;/a&gt; here. I&amp;#x27;d say this is one of the best collaborations we&amp;#x27;ve done. Due to Jepsen tests, we were able to proactively identify and fix issues in a complex real time distributed graph DB, that is Dgraph. Dgraph&amp;#x27;s graph sharding, replication and transaction implementation is unique and it took more work to make it all work correctly, while still achieving good performance, and without utilizing any third party system.&lt;p&gt;I&amp;#x27;d like to thank Kyle for his work on Dgraph. We&amp;#x27;ll continue to expand Jepsen tests to try and identify more issues and fix the remaining ones.&lt;p&gt;I&amp;#x27;m around if you have questions! Cheers, Manish</text></comment>
<story><title>Jepsen: Dgraph 1.0.2</title><url>https://jepsen.io/analyses/dgraph-1-0-2</url></story><parent_chain></parent_chain><comment><author>BMarkmann</author><text>I honestly don&amp;#x27;t know that there are any posts I get more excited about on HN than Jepsen analyses.  The number of landmines distributed systems create and the ability to suss them out in such detail &amp;#x2F; depth is really incredible.  Kudos.</text></comment>