database-lab-engine
goose
| database-lab-engine | goose | |
|---|---|---|
| 20 | 30 | |
| 2,121 | 7,484 | |
| 0.6% | 3.8% | |
| 8.8 | 8.6 | |
| 7 days ago | 7 days ago | |
| TypeScript | Go | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
database-lab-engine
-
Pg_branch: Pre-alpha Postgres extension brings Neon-like branching
Underlying DBLab Engine is FOSS (Apache 2.0), with API, CLI and UI https://github.com/postgres-ai/database-lab-engine
-
Want to avoid MySQL but find PlanetScale really appealing
That said, there are a few folks out there attempting it. As mentioned, Neon attempts branching but has no "merge". Postgres.ai has "thin clones" for similar migration testing but again, no "merge".
-
Neon – Serverless Postgres
Agreed, this direction is underestimated and should be developed better -- we (Postgres.ai) do it for any Postgres with our Database Lab Engine [1], and Neon would bring even more power if it's installed on production
[1] https://github.com/postgres-ai/database-lab-engine
- Changing Tires at 100mph: A Guide to Zero Downtime Migrations
- Database Lab Engine 3.1 for PostgreSQL
- Database Lab Engine 3.1 released: native support for pgBackRest, timezones in CLI, more
- Database Lab Engine: Thin PostgreSQL Clones. DLE provides blazing-fast database cloning to build powerful development, test, QA, staging environments.
- Thin PostgreSQL clones
goose
-
How to handle migrations in Golang
goose
-
GORM and Goose Migrations
Let's get started with handling migrations in Go with GORM and Goose.
-
Recent improvements to the pressly/goose migration tool
In v3.16.0 we added a new Provider feature that unlocks the ability to implement a lot of highly requested features. More details in the blog post:
- How are y'all that are using raw sql doing DB Migrations?
- Why elixir over Golang
- Is there a similar tool or alternative in Go like strong_migrations?
-
How do you handle migrations ?
Next try https://github.com/pressly/goose We have this setup to be run by the CI-CD pipeline to be run before the application is started. BTW, this utility is compatible with https://sqlc.dev , so they work good together.
-
Does this project structure make sense?
For database migration I recommend https://github.com/pressly/goose As it works with sqlc and is a powerful tool for complex migrations. This is something a lot of ORMs are really weak with. I was on a large project with Gorm as the ORM and what a nightmare when we pushed to production!
- Are there any decent ORMs in Golang?
- Don't Mock the Database
What are some alternatives?
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
liquibase - Main Liquibase Source
wal-g - Archival and Restoration for databases in the Cloud
migrate - Database migrations. CLI and Golang library.
reshape - An easy-to-use, zero-downtime schema migration tool for Postgres
go-migrate - Abstract task migration tool written in Go for Golang services. Database and non database migration management brought to the CLI. [Moved to: https://github.com/g14a/metana]
blog - Opensource,Database,AI,Business,Minds. git clone --depth 1 https://github.com/digoal/blog
dbmate - 🚀 A lightweight, framework-agnostic database migration tool.
libschema - database schema migrations on a per-library basis [Go]
tern - The SQL Fan's Migrator
awesome-nodered - A collection of interesting nodes and resources for Node-RED
alembic - A database migrations tool for SQLAlchemy.