3 ms·
You seem to have a rather limited understanding of what kinds of concurrency exist and how those needs are best met. Whether something is a server or not is not
by jph00 4mo ago
You seem to have a rather limited understanding of what kinds of concurrency exist and how those needs are best met. Whether something is a server or not is not very relevant to this discussion.
SQLite is an excellent production db for many real world workloads, as has been widely documented. It is very different to Postgres, so requires learning a whole new skill set.
One way to think about it is that SQLite can work well for the parts of your system where there is naturally strong partitioning.
- tasuki 4mo ago> SQLite can work well for the parts of your system where there is naturally strong partitioning. Or the parts of your system that don't have big data and no need for massively concurrent writes. And that's the vast majority of systems!
- MattJ100 4mo agoYou can do big data in SQLite. Concurrent writes, sure, I'd recommend something else. If you think the majority of systems require massively concurrent writes, I think you need to look a bit harder. SQLite is, after all, the most widely deployed database system, ever.
- therealdrag0 4mo agoIt’s widely deployed as a local DB for local apps like phones, desktops, and web browsers. But it’s not the most used for distributed, concurrent web apps, which db servers were designed for. Maybe people are talking past each other, but that’s the debate I see.
- kellogah 4mo agoNot sure why there’s a debate at all. The discussion is on using SQLite instead of jq and markdown files. People got lost on a tangent! :)
- petre 4mo agoWe recently just partitioned the data into many SQLite databases and got away with it. It's telemetry data from IoT devices: one device, one database. Backups are an easy rsync job now instead of streaming a multi gigabyte database with compression that take hours. Reporting will just open each database and aggregate multi device data into another database (Duckdb, SQLite or something else, we'll see). Duckdb is not readable when locked so it's probably also going to be SQLite. Even it it's going to spit out JSON it will go into SQLite rows instead of many files.
- datadrivenangel 4mo agoCheck out Quack for DuckDB.
- petre 4mo agoI saw that but it's a bit too much friction. We'd rather attach a SQLite database and copy the results into that. Also no worries about version changes and compatibility, the types are not too restrictive. But we'll see.
- sharts 4mo agoInternet Explorer 6 was the most widely deployed awesome piece of software. Those that hated it need to look a bit harder.
- Gud 4mo agoIt was not really “deployed” by a lot of people in the same sense. It was forced upon most of us(not me, I used BeOS then Debian then FreeBSD). I deployed phoenix.
- HighGoldstein 4mo agoThe reason SQLite is the most deployed is that it's used by Android.
- velcrovan 4mo ago…and iOS, and Windows, and Mac OS, and Boeing, and Sony, and Firefox and Chrome and Safari…
- HighGoldstein 4mo agoYes, which goes in line with the argument that claiming that it's "the most deployed" as proof of superiority or suitability for any use case is equivalent to claiming the same for Internet Explorer. It's the most deployed because it's bundled in a lot of systems, not because people are purposefully using it as a DBMS.
- velcrovan 4mo agoBut it doesn't, because none of those systems are presenting SQLite to the user as something they should be using; they don't even make SQLite available to the user at all. Those systems all use SQLite internally to manage data.
- andersmurphy 4mo agoWhat's massive amount concurrent writes? What's big data?
- whatisthiseven 4mo agoSuch an exercise is left for the reader.
- leowoo91 4mo agoWhat additional skill set do you need to "learn" for SQLite? Copying files around?
- Culonavirus 4mo agoYeah these are deeply unserious people.