whatgotdone VS pgxtutorial

I wrote a tool specifically for this, mostly inspired by the Snippets tool at Google. I've been publishing my weekly log in it every week for almost three years:

https://whatgotdone.com/michael/2021-12-03

The code is all open source if you're interested in playing around with it:

https://github.com/mtlynch/whatgotdone

I had the same objection to SQLite, and then I heard about Litestream, and it won me over.[0]

Litestream watches your SQLite database and then streams changes to a cloud storage provider (e.g., S3, Backblaze). You get the performance and simplicity of writing SQLite to the local filesystem, but it's syncing to the cloud. And the cool part is that you don't have to change any of your application code to do it - as far as your app is concerned, it's writing to a local SQLite file.

I wrote a little log uploading utility for my business that uses Litestream, and it's been fantastic.[1] It essentially carries around its data with it, so I can deploy my app to Heroku, blow away the instance and then launch it on fly.io, and it pops up with the exact same data.[2]

I'm currently in the process of rewriting an open-source AppEngine app to use SQLite + Litestream instead of Google Firestore.[2] It's such a relief to get away from all the complexity of GCP and Firestore and get back to simple SQLite.

[0] https://litestream.io/

[1] https://mtlynch.io/litestream/

[2] https://asciinema.org/a/I2HcYheYayeh7aHj23QSY9Vyf/embed?size...

[3] https://github.com/mtlynch/whatgotdone/pull/639

# Clone my repository with any of the following commands: $ gh repo clone henvic/pgxtutorial $ git clone https://github.com/henvic/pgxtutorial.git $ git clone [email protected]:henvic/pgxtutorial.git # then: $ cd pgxtutorial # Create a database $ psql -c "CREATE DATABASE pgxtutorial;" # Set the environment variable PGDATABASE $ export PGDATABASE=pgxtutorial # Run migrations $ tern migrate -m ./migrations # Run all tests passing INTEGRATION_TESTDB explicitly $ INTEGRATION_TESTDB=true go test -v ./... # Execute application $ go run ./cmd/pgxtutorial 2021/11/22 07:21:21 HTTP server listening at localhost:8080 2021/11/22 07:21:21 gRPC server listening at 127.0.0.1:8082

oh, I also have defined database.PGX (https://github.com/henvic/pgxtutorial/blob/main/internal/dat...), which is a little more scarier. I'll get back about that too, but this one is perhaps even more useless, and there might be a better way to solve the issue I want to try to avoid with it.