this post was submitted on 13 Sep 2023
1508 points (98.9% liked)
Memes
45550 readers
1111 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Kind of related question: Is it okay for me to use JSON as a small DB? I just store basic blog page data there.
I mean it will work, but for a blog I'd store the pages in markdown files, to make it easier to edit. For context, look into how Hugo works
I thought of that as well. I might switch to that. It will make the organization better anyways.
TinyDB literally does this. in general its more of does this work for my use case and am i aware of its limitations.
A few circumstances to consider...
If it's just your own little tool and you don't intend to share it with others: do whatever you want. SQL or NoSQL or JSON, it doesn't matter. Use your own judgement.
In my experience tho most homegrown JSON-based "databases" tend to load all data into the memory, simply because they are very simplistic (serialize everything into JSON and write to disk, deserialize everything into a struct). If your dataset is too big for that, just go straight for a full-fledged database.
If it works then it works.
yep, though IO might bottleneck you at some point, and then you can happily switch to mongoDB