3 ms·
Although there is a lot of data here, it seems all of it is roughly repetitive, relational data. Why not store it in a central database? I have a (much smaller
by z77dj3kl 6y ago
Although there is a lot of data here, it seems all of it is roughly repetitive, relational data. Why not store it in a central database?
I have a (much smaller project) that stores all data in a postgres datastore.
- elseweather 6y agoThere's an explanation here: https://beepb00p.xyz/unnecessary-db.html https://beepb00p.xyz/unnecessary-db.html (the link behind "Against unnecessary databases")
- z77dj3kl 6y agoTo me, it just seems like the author wants to hoard their data, not make it useful. Making it useful (the first part of which is making it queriable) involves making some kind of interface to access it, and some code to parse it. In my own case, I find that just dumping JSON docs around the place gives me an unmanageable mess of unstructured data that I never come back to. If all you want to do is to hoard your data, then I guess that achieves the purpose... But if you want to do something with it, at some point you have to make sense of it. Doesn't mean you have to go and fully normalize everything and make a production-level database!