Database migrations. CLI and Golang library. (by golang-migrate)

Migrate Alternatives

Similar projects and alternatives to migrate

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better migrate alternative or higher similarity.

migrate reviews and mentions

Posts with mentions or reviews of migrate. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-17.
  • Using migrations with Golang
    5 projects | dev.to | 17 Apr 2024
    Go does not natively support the use of migrations, but we could use the ORM that has this functionality, such as GORM which is the most used by the community, but We can use migrations without using an ORM, for this we will use the golang-migrate package.
  • Looking for recommendations for model/schema/migration management in Golang
    2 projects | /r/golang | 7 Dec 2023
  • API completa em Golang - Parte 1
    8 projects | dev.to | 1 Dec 2023
  • Building RESTful API with Hexagonal Architecture in Go
    21 projects | dev.to | 27 Sep 2023
    Golang-migrate is a database migration tool designed for Go applications. It helps manage and apply changes to the database schema as the application grows, ensuring that the code and database structure stay in sync.
  • Python: Just Write SQL
    21 projects | news.ycombinator.com | 14 Aug 2023
    First of all, thank you for SQLAlchemy! If I ever had to make a final choice in how I would interact with a database for a very large project that involves a considerable dev team, I would always bet on SQLAlchemy. Not that I would necessarily like all aspects of it, but when it comes to Python and SQL - “Nobody ever got fired for picking SQLAlchemy.”.

    With that out of the way, despite ORMs doing much more than "just writing SQL", it is exactly on that point that I flinch: Most devs should be exposed to SQL. And if your project allows you to build around simple enough abstractions so that you aren't reinventing the wheel, you should definitely be writing SQL. Especially if you don't know SQL yet - which is the growing case of new devs coming into the job market.

    You can achieve a lot with SQlAlchemy Core, a tool that I absolutely recommend, but my post is just a simple alternative to get developers to think about their approach. If that results in some devs reconsidering using "full fat" SQLAlchemy and to try SQLAlchemy Core, that's a win for me!

    Your gist tries to highlight the difficulty of doing certain things without an ORM. Migrations (as just 1 example) doesn't need to be hard, simple tools like flyway, or migrate (https://github.com/golang-migrate/migrate) achieve a similar result (while also keeping you on the path of writing SQL!). Deep and complex relationships between objects also don't need to be hard - typically people approach this subject with a requirement to be very flexible in the way they want to build queries and objects, but that to me in a sign that maybe they should reconsider their business logic AND reconsider that, just maybe, their project doesn't require all that flexibility, it is fairly straightforward to extend objects and introduce some more complex representations as and when it is needed - will all of this make me write code faster? Absolutely not. That is why you have spent so much time perfecting SQLAlchemy, but then again, I am not advocating for devs to go and replace their usage of ORMs, just presenting an alternative that may or may not fit their needs for a new project + give devs the chance to learn something that the ORM might have taken away.

    21 projects | news.ycombinator.com | 14 Aug 2023
    When it comes to migrations, I've been fine with https://github.com/golang-migrate/migrate

    There are a multitude of extra things to consider, but none of those things are, in my opinion, imperative to having success with SQL in Python. Will it be hard to achieve the same level of convenience that modern ORMs provide? Absolutely. But there is always a cost.

    I firmly believe that for most projects (especially in the age of "services"), an approach like this is very much good enough. Also, a great way to onboard new developers and present both SQL and simple abstractions that can be applied to many other areas of building software.

  • Database migration tool
    4 projects | /r/golang | 10 Jul 2023
  • REST API with Go, Chi, MySQL and sqlx
    6 projects | dev.to | 23 Jun 2023
    Before we can start using MySQL we need to create a table to store our data. I will be using excellent migrate database migrations tool, it can also be imported as a libraray.
  • How do your teams run DB migrations?
    4 projects | /r/devops | 1 Jun 2023
    By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up.
  • From Golang Beginner to Building Basic Web Server in 4 Days!
    5 projects | /r/golang | 21 May 2023
    For building my web server, I chose to use the Gin framework as the foundation of my app. It was incredibly easy to understand and work with, and I was pleasantly surprised by how seamlessly it integrated with writing unit tests for the server. To handle the database, I leveraged the power of go-sqlite and migrate for efficient SQL queries and migrations. These libraries proved to be both powerful and user-friendly, making the development process a breeze.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 17 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →


Basic migrate repo stats
3 days ago

golang-migrate/migrate is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

The primary programming language of migrate is Go.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives