xgo VS sqlite

Yes, the project is still alive and well! It also powers our very alive commercial service, Write.as, which has most of my attention. The open source project is just moving at a one-maintainer pace because it only has one maintainer :)

There will definitely be future releases, especially once we get through a roadblock with the tool we use to cross-compile WriteFreely [0]. Otherwise, anyone who wants to see the project move faster is more than welcome to contribute, especially with tasks like code review, to help clear out those PRs [1].

[0] https://github.com/techknowlogick/xgo/issues/155

[1] https://github.com/writefreely/writefreely/discussions/550

Wow this is awesome, thanks! I'm working on a Go project that uses sqlite right now, and I thought I was going to have to use xgo[1], which is cool and all, but it's like an 8 GB docker container, and I'd still be worried about glibc issues.

[1]: https://github.com/techknowlogick/xgo

> You can get substantially better performance out of sqlite by using the lower level https://github.com/crawshaw/sqlite, turning on WAL etc, using a connection per goroutine for reads, and sending batches of writes over a buffered channel / queue to a dedicated writer thread. That way you can turn off SQLite’s built in per-connection mutex but still be thread safe since each connection is only used on a single thread at a time.

Would this protect against a row update in the middle of a read? e.g. would a row at least be internally consistent at the time it was read?

The default go sqlite driver is https://github.com/mattn/go-sqlite3, which is quite lovely, but I ran into issues with concurrency on read only databases.

I'm now using https://github.com/crawshaw/sqlite and it seems to address those issues (but I haven't gotten around to setting up a proper test to confirm). It may be worth perusing if you do run into performance problems. It does come with the caveat of not being a database/sql driver though.

crawshaw/sqlite - Low-level Go interface to SQLite

crawshaw/sqlite actually uses CGo -- it's a wrapper around the C version of SQLite. For example, see https://github.com/crawshaw/sqlite/blob/23d646f8ac00d9dd2390...

zombiezen/go-sqlite uses cznic's pure Go converted version of SQLite, so avoids CGo. It's explicitly stated to be "a fork of crawshaw.io/sqlite that uses modernc.org/sqlite, a CGo-free SQLite package. It aims to be a mostly drop-in replacement for crawshaw.io/sqlite."

The second well known driver is https://github.com/crawshaw/sqlite