> 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 3 hours ago | parent [-]

You 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 3 hours ago | parent [-]

It’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 2 hours ago | parent [-]

Not 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! :)

▲

gnabgib an hour ago | parent [-]

No it's not.. the context of other threads on this post (which mention jq) do not apply here. How poorly coded are you?

	▲	kellogah an hour ago \| parent [-]
		Like how poorly did Jesus code my DNA? Ask him. By him I mean ChatGPT Jesus mode.