This article makes two main arguments, both of which are (sorry to be blunt) just plain dumb.
The first point is that the claim that "SQLite can support up to 281TB in a single database" is wrong, because in practice you can't get a single disk that big, and therefore SQLite is a bad choice for storing 16GB of data.
The second point is that without indexing, retrieving individual data items is very inefficient. Therefore a big distributed MySQL cluster (which supports indexing) is better than a single SQLite database (which also supports indexing).
Most of the rest of the text only serves to beat around the bush and distract from how nonsensical the core arguments are.
One nitpick: Using RAID, can you construct a massive single disk mount from JBOD? It seems possible in 2024 to create a 300GB continuous mount. However, your point stands: For most real world scenarios, anything larger than 10TB is probably unreasonably large for a single-file SQLite DB.
> Most of the rest of the text only serves to beat around the bush
Thank you for saying that outloud. This person goes on and on. It is like the YouTube talking head videos that are 45mins, that could easily be cut to 10-15mins!
Comments
This article makes two main arguments, both of which are (sorry to be blunt) just plain dumb.
The first point is that the claim that "SQLite can support up to 281TB in a single database" is wrong, because in practice you can't get a single disk that big, and therefore SQLite is a bad choice for storing 16GB of data.
The second point is that without indexing, retrieving individual data items is very inefficient. Therefore a big distributed MySQL cluster (which supports indexing) is better than a single SQLite database (which also supports indexing).
Most of the rest of the text only serves to beat around the bush and distract from how nonsensical the core arguments are.
I like your retort. It is well written.
One nitpick: Using RAID, can you construct a massive single disk mount from JBOD? It seems possible in 2024 to create a 300GB continuous mount. However, your point stands: For most real world scenarios, anything larger than 10TB is probably unreasonably large for a single-file SQLite DB.
Thank you for saying that outloud. This person goes on and on. It is like the YouTube talking head videos that are 45mins, that could easily be cut to 10-15mins!