Re:That won't scale Or present cost vs. future value
by once_inc on Monday April 24, 2023 @05:52AM
(#35685525)
The text file example is pretty flawed. There are quite a few benefits to using databases over text files aside from being a place to store data. Structuring, availability, race conditions, etc. Including and using a NoSQL database is hardly the bottleneck in producing a production-level app/website/whatever.
Re:That won't scale Or present cost vs. future value
by moffkalast on Monday April 24, 2023 @07:30AM
(#35686265)
This site being a prime example of how storing production data in text files on a file system leads to terrible performance.
Re:That won't scale Or present cost vs. future value
by dgb23 on Monday April 24, 2023 @09:12AM
(#35687237)
It's a perfect use case for SQLite or similar. It's a low overhead solution (just a library) and you get a lot of benefits out of the box.
A text file? Maybe if it's an append only kind of deal.
Do you really want do deal with durability and parsing a flat file, etc? Is that really easier that using a simple database? I see these kinds of arguments a lot from developers who think things like relational databases are hard to use, which artificially inflates the argument against "extra complexity"
There are hard tradeoffs to make, and the interesting arguments are in the place where reasonable people disagree about what kind of robustness will be needed over a particular timescale. It's never as simple as "it won't scale" where it's obvious to everyone that having millions of users tomorrow isn't realistic.