#politics #computers #business 2023q4 2023q3 2023q2 2023q1 2022q4 2022q3 2022q1 2021q1 2020q3 2020q1 2019q4 2019q3 2019q2 2019q1 2018q3 2018q2
==> Charles Leifer writes on Kyoto Tycoon in 2019.
KyotoCabinet, the storage engine beneath KyotoTycoon, is one of the most important weapons in my holster as a data scientist.
For a data scientist, there are essentially two different kinds of job environments. One is where it’s all about infrastructure and implementing the database to end all databases (and finding stuff out is a mere afterthought). The other is where 100% of the focus is on finding stuff out by next week with zero mandate for any infrastructure investment. When I find myself in the latter kind of work environment, and I need to quickly get sortable and/or indexable data structures of any kind, then a key-value store is the way to go, and KyotoCabinet is a really good one that I’ve used lots and has never let me down.
Just keep your boss from finding out about it if yours is of the pointy-haired variety. He will be less than pleased if he finds out it’s an open-source project that saw its last commit some 6 years ago. – As for myself, this doesn’t bother me all too much. It’s feature-complete w.r.t. anything I’ve ever wanted to do with it, and its feature set is way richer than most of the younger alternatives that are still being actively developed (because they still need active development and aren’t nearly as well battle-tested). Plus, what’s the worst that could happen? Get & set is basically all there is to it, and if you should ever be in a position where you need to replace it with something else that has get & set, there should be tons of options. The migration should be easy to do.
#computers | Jan-12 2019
#politics #computers #business 2023q4 2023q3 2023q2 2023q1 2022q4 2022q3 2022q1 2021q1 2020q3 2020q1 2019q4 2019q3 2019q2 2019q1 2018q3 2018q2