Get the latest tech news

It's Time to Stop Building KV Databases

I'm so sick of Key-Value. The most unopinionated, uninspired data model that is a pain to use for anything. They're very popular! Among database vendors. Or,...

Application programs and terminal activities remain logically unimpaired whenever any changes are made in either storage representations or access methods. For a very limited use case, where we know for the most part, ahead of time what our access patterns will be, and have a small set of queries, this risk (and headache) might not be worth the benefits of data independence. Perhaps the biggest decision that has to be made is "how deeply do your records permeate your data model," meaning, do you have types that you write to disk and then know how to compare?

Get the Android app