blog VS node-pg-migrate

Compare blog vs node-pg-migrate and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
blog node-pg-migrate
1 4
7,814 1,215
- 0.6%
9.9 8.9
7 days ago 5 days ago
PLpgSQL TypeScript
GNU General Public License v3.0 only MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

blog

Posts with mentions or reviews of blog. We have used some of these posts to build our list of alternatives and similar projects.

node-pg-migrate

Posts with mentions or reviews of node-pg-migrate. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-20.
  • Fully featured Repository Pattern with Typescript and native PostgreSQL driver
    5 projects | dev.to | 20 Mar 2022
    Why PG? For the clarity of the article to a large circle of developers, the entire explanation will be built by PostgreSQL and PG package. And in a real project, the database schema will change over time, and in order to be able to perform migrations, we will use Node PG migrate.
  • New to PostgreSQL - Best way to use it?
    6 projects | /r/PostgreSQL | 25 Jan 2022
    b) How you will manage schema migrations: every time you change tables, columns, foreign keys, every time you create or modify stored procedures, and so on, you need to do this through a migration. Here I'm at loss to recommend anything specific, but if you went with Prisma, I would read their docs and use whatever they are recommending you (if they actually recommend something). If you want something more neutral but still in the node ecosystem, node-pg-migrate might be the winner here? I'm not sure.
  • Postgres: What is the development process?
    3 projects | /r/PostgreSQL | 17 Oct 2021
    You’ll probably want something like this too: https://github.com/salsita/node-pg-migrate
  • The Architecture of a One-Man SaaS
    16 projects | news.ycombinator.com | 8 Apr 2021
    You can use any normal DB migration tool. For k8s, I put the app's readiness probe to false, run the migrations and then toggle the probe back to true.

    Here are some migration libraries:

    Go - https://github.com/golang-migrate/migrate

    Node - https://github.com/salsita/node-pg-migrate

What are some alternatives?

When comparing blog and node-pg-migrate you can also consider the following projects:

crystal - 🔮 Graphile's Crystal Monorepo; home to Grafast, PostGraphile, pg-introspection, pg-sql2 and much more!

sql-lint - An SQL linter

postgres-aws-s3 - aws_s3 postgres extension to import/export data from/to s3 (compatible with aws_s3 extension on AWS RDS)

graphjin - GraphJin - Build NodeJS / GO APIs in 5 minutes not weeks

omdb-postgresql - PostgreSQL Schema for OMDB

logpaste - A simple web service for storing text log files

pgddl - DDL eXtractor functions for PostgreSQL (ddlx)

prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React

database-lab-engine - DBLab enables 🖖 database branching and ⚡️ thin cloning for any Postgres database and empowers DB testing in CI/CD. This optimizes database-related costs while improving time-to-market and software quality. Follow to stay updated.

flan - A tasty tool that lets you save, load and share postgres snapshots with ease

aurora - CLI tool that orchestrates prisma files in a way that allows multiple .prisma files with cross-relations

migrate - Database migrations. CLI and Golang library.