Kyoto Tycoon in 2019
KyotoCabinet is one of the most important weapons in my holster as a data scientist.<p>With that kind of a specialty, there are essentially two different kinds of jobs &#x2F; work environments.  One is where it&#x27;s all about infrastructure and implementing the database to end all databases (and &quot;finding stuff out&quot; is a mere afterthought to that.  The other is where 100% of the focus is on &quot;finding stuff out BY NEXT WEEK&quot; with zero mandate for any infrastructure investment of any kind.  When I find myself in the latter kind of work environment and I need to quickly get sortable and&#x2F;or indexable datastructures of any kind, then a key-value store is the way to go and KyotoCabinet is a really good one that I&#x27;ve used LOTS and it has never let me down.<p>Just don&#x27;t let your boss find out about it if yours is of the pointy-haired variety.  If he finds out that it&#x27;s an open source project that has seen its last commit some 6 years ago and has been abandoned since, he will be less than pleased.  -- Personally I find that&#x27;s a really bad argument.  It&#x27;s feature-complete w.r.t. anything I&#x27;ve ever wanted to do with it, and its feature set is actually way richer than most of the younger alternatives that are still being actively developed (because they are still in <i>need</i> of very active development, and aren&#x27;t nearly as well battle-tested).  Plus what&#x27;s the worst that could happen?  That you will one day want to move to an environment where it will no longer work.  Well in that case it shouldn&#x27;t be so hard to substitute another key-value store for this one.  After all, the simplicity of the API around a key-value store where get &amp; set is basically all you need, should make that really easy.