3 ms·
I'm pretty sure the mantra is "Never Write Your Own Crypto", not "never write your own database". I know tons of people who roll their own flat-file storage en
by marknadal 8y ago
I'm pretty sure the mantra is "Never Write Your Own Crypto", not "never write your own database".
I know tons of people who roll their own flat-file storage engine and are perfectly happy with it, even scaling up to their moderate couple of tens-of-thousands of users. Nothing fancy.
Personally, I had to write my own database (just like what the author of the article wound up doing), and had a delightful time learning all sorts of things, and now it is one of the most popular databases out there (https://github.com/amark/gun https://github.com/amark/gun) and I encourage others to try (if they have time) building one themselves!
- ovao 8y agoThe 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.)