4 ms·
Because the answer is not the answer to the question I asked, so if you think it is, I didn't ask it the right way. If I ask: -- why can't sqlite just scale f
by projectramo 10y ago
Because the answer is not the answer to the question I asked, so if you think it is, I didn't ask it the right way.
If I ask:
-- why can't sqlite just scale for me.
And you say:
-- Well, its meant to be lightweight. There are other more powerful databases, or you can add more code to sqlite to make it scale.
Its not that I didn't know all those things. Those were the premise to the question I asked.
- Kalium 10y agoThe things that make a database scale are fundamentally at odds with the things that make a database zero-configuration. You can get one or the other. The thing you want, a zero-configuration self-tuning automagical smart RDBMS, is not considered feasible. There. An answer to the question you asked. Incidentally, if you think that's unsatisfactory answer, I remind you that you're on a website linked to a startup accelerator.
- dorfsmay 10y ago> why can't sqlite just scale for me. Because it's not a client/server implementation, it's a single embedded library, and because part of the requirements were to use a single data file. Therefore, each process (all completely independent) accessing that file: -needs to lock the entire file (rather than tables/rows) -needs to flush and close the file after each write -cannot prioritize I/O across processes, one file open the file, read or write, close the file (as opposed to do all the writes at once for example) -cannot cache very effectively, every time a process writes, all the other processes have to re-load the file etc...