3 ms·
Isn't the main feature of nosql supposed to be easy horizontal scalability, the exact opposite of storing everything in a single file? If you just need a r/w s
by quantumofalpha 5y ago
Isn't the main feature of nosql supposed to be easy horizontal scalability, the exact opposite of storing everything in a single file?
If you just need a r/w store for some jsons in a single file, why not sqlite? You can put arbitrary-length blobs into it. Some sql will be involved but you can hide it in a wrapper class tailored to your application with a few dozen lines of code or so.
- etaioinshrdlu 5y agoPractically, NoSQL also seems to just mean "Not-SQL" as stuff like Redis is often lumped in it, which is about the opposite of easy horizontal scalability.
- gary_0 5y ago> You can put arbitrary-length blobs into it. And it's quite suitable for this purpose: https://www.sqlite.org/fasterthanfs.html https://www.sqlite.org/fasterthanfs.html
- Jare 5y ago> Isn't the main feature of nosql supposed to be easy horizontal scalability There's no strict definition of nosql so everyone can choose their own. My personal take (in broad terms) follows: No, that's not a feature of nosql. Nosql means not relational, which in turn means no guarantees about the relationship between two objects, i.e. no atomicity of access across multiple objects (for either read or write operations). A consequence of this lack of atomicity is that it's easy to store different objects in different places, thus opening up opportunities for horizontal scalability. Caveat: those opportunities can be taken away by other choices you make. If you decide to offer and enforce transactions, you are bringing atomicity back into the system, and thus making horizontal scalability hard again. Or you may decide you want a nosql-in-a-file.