3 ms·
I would never use SQLite when there is more than one persistent data memory user.
by makerdiety 2y ago
I would never use SQLite when there is more than one persistent data memory user.
- simonw 2y agoWhy?
- actinium226 2y agoWhat is a persistent data memory user?
- jmull 2y agoI don't know exactly what you mean, but sqlite probably supports your use case. sqlite's defaults balance performance, flexibility, and backwards compatibility. They don't work for every case, but there is almost always a lever to pull. The downside is you have to learn them. The docs are really excellent, though.
- indulona 2y agotrue, concurrency, let alone parallelism, never worked for me when i tried it. never used in anywhere. sounds good in theory but it is unusable for most real world cases. there are endless key-value databases suitable for 90% of what sqlite does. and if you truly need multiple indexes per table and joins, just use a proper rdbms and stop playing around.