One quick thing I can think of is multiple writers [0]

[0]: https://turso.tech/blog/beyond-the-single-writer-limitation-...

What's the isolation level? They only mention write-write conflicts.

The reason SQLite's BEGIN CONCURRENT does not greatly increase concurrency (unless you're very careful with your schema and queries) is as much due to page level conflict detection as it is because it enforces serializable isolation.

▲

ZeroCool2u 15 hours ago | parent | prev | next [-]

This is a huge differentiator. I built our internal meme platform with Turso. Really fun and easy to use.

▲

zdragnar 14 hours ago | parent [-]

How much internal traffic are you generating that single thread sqlite writes can't keep up?

	▲	ZeroCool2u 14 hours ago \| parent [-]
		The meme machine cannot be stopped. It's really not that much, but this has the nice side effect of I simply don't need to worry about it.

▲

tonymet 15 hours ago | parent | prev [-]

isn't this just pushing the complexity around? Either my write thread manages the lock, or turso's does.

▲

gpm 15 hours ago | parent [-]

MVCC is a non-locking algorithm for concurrent writers that the big databases like postgres use (with caveats like aborting some transactions if conflicts would exist). It's not a matter of pushing locks around but allowing multiple threads to operate on the data concurrently.

	▲	tonymet 14 hours ago \| parent [-]
		thanks helpful thanks. seems to have some tradeoffs. I would likely lean toward the simpler thread model but it sounds compelling.