goose

> I still use Django for models and migration There are dozens of us! It's a great db management toolkit. I've used it to much success many times for things like managing migrations from mysql to postgres and php to python. My opinions: - Django apps are an anitipattern for large internal / single purpose products due to migration overhead as FKs cross application boundaries. I will die on this hill. No team is ever disciplined enough to keep apps as boundaries for relationships and constraints. Strong contrast to the rails crowd that doesn't rely on referential integrity in the db by default where this isn't "a thing". - Goose[0] migrations in Go are really great but you have to let go of the dsl and the idea that your ORM drives your migrations, as you explicitly called out. Laravel[1] is on par with django IMO and a delight to use when

I use goose[1] for db migrations. [1]: https://github.com/pressly/goose

For the last few months, we've been running our database migrations using Go and Goose [1] within our Github Actions workflows as a step that completes after a successful asset deployment. For the sake of the post, assume that the deployed "thing" is a lambda function. Installing Go and Goose for each deployment run costs us about a minute and a half, to two minutes, depending on Github Actions' mood that day. It's a chunk that I'd like to remove from our deployment runs, as maybe 1 out of every 100 deployments has a database migration in tow. Separating the db migrations and Go/Goose installs into a separate job that runs based on whether or not the migrations directory has changes, dependent on the deployment job (or vise versa), seems like a good way to go. However, that presents some race conditions and there doesn't seem to be much (

I wasn't happy with the current database access packages (https://github.com/jmoiron/sqlx, https://gorm.io), so I wrote my own for PostgreSQL. It takes existing queries and generates type-safe Go methods (https://github.com/kyleconroy/sqlc). I enjoy using it and thought others might too. As for migrations, I've had success with https://github.com/pressly/goose. It's lightweight and is also just SQL.

For us, database migrations are a separate step, and we make sure to know whether a migration results in breakage. If it does, we take the app down first (with a maintenance message) so that errors won't bubble up to the users and APIs. If we need to roll back a deploy that has migrations, we just roll back the migration. Every migration requires a "down" step that reverses itself. Our Go apps use Goose [1], but there are many other solutions. [1] https://github.com/pressly/goose

For ORM we use GORM: http://gorm.io For migrations we use goose: https://github.com/pressly/goose

how does it differentiate from * https://github.com/mattes/migrate * https://github.com/rubenv/sql-migrate * https://github.com/pressly/goose