I'm trying to understand the use case for a persistent embedded DB for Go. SQLite is embedded all over the place, often in clients.
But presuming Go is a server language, and you are running stateless web nodes, why do you need persistence?
It's awesome because it's just a go package - no external dependency... Your application still ships as a single binary.
Note that using a sqlite wrapper like https://github.com/mattn/go-sqlite3, you also don't have any external dependencies and your application still ships as a single binary. However, there are other advantages of a Go-native storage library (e.g., doesn't require cgo, better integration with tools like pprof, etc.)