Goose vs yoyo-migrations
Goose
pressly.github.ioyoyo-migrations
ollycope.comSide by side
| Figure | Goose | yoyo-migrations |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Database Migration Tools | 8.3 (#8) | 6.6 (#30) |
| License | The GitHub repository states that Goose is licensed under the MIT License. | PyPI lists the license as Apache Software License (Apache). |
| Migration controls | The CLI can apply, roll back, redo, reset, inspect, and version database migrations. | The command line can apply, roll back, reapply, list, mark, and unmark migrations. |
| Migration formats | It manages database schemas with incremental SQL changes and Go migration functions. | Migration scripts can be written as SQL files or Python scripts. |
| Purpose | Goose is a database migration tool for managing database schemas with incremental SQL changes and/or Go functions. | Yoyo is a database schema migration tool whose migrations are SQL files or Python scripts. |
Plans
In their own words
Goose
Goose is a free, open-source database migration tool for managing schema changes through incremental SQL files and Go functions. It is available as both a command-line utility and a library. The CLI can apply, roll back, redo, reset, inspect, and version migrations, with documented drivers for ClickHouse, Microsoft SQL Server, MySQL, PostgreSQL, SQLite, Turso, Vertica, and YDB. SQL migration files use an up annotation and may include a down annotation; filenames can use timestamps or sequential numbers. Statements in a migration file run in one transaction by default, with an annotation for running them outside one. Go migration functions can use a transaction when given a transaction argument. Other listed capabilities include embedded and out-of-order migrations, data seeding, and environment variable substitution in SQL migrations. For library use, a provider accepts a database dialect, connection, migration filesystem, and optional configuration. The provider does not lock the database by default, so callers must arrange safe concurrent migrations or configure a session locker.
yoyo-migrations
yoyo-migrations has no write-up on Specifiction yet; its figures are above.