The mantra tends to be “just use SQL” or “just use SQL, unless...”. Similar to the advice “just use an int, unless...”. The wisdom in that is usually pretty sa

The mantra tends to be “just use SQL” or “just use SQL, unless...”. Similar to the advice “just use an int, unless...”. The wisdom in that is usually pretty sage. Reach for a SQL database unless there are reasonable and concrete reasons not to. Then, evaluate whether there’s a need to roll your own, or if there’s something you can grab right off the shelf. I’d argue there are plenty of perfectly valid reasons to roll your own, and it’s not particularly difficult if you build on an already-proven storage foundation (file system, LMDB, etc.)