node-pg-migrate VS graphjin

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.

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.

You’ll probably want something like this too: https://github.com/salsita/node-pg-migrate

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

This one looks interesting if you like GraphQL… https://graphjin.com

You're right. Django made a ton of tables, and it's pretty insightful to think about all the stuff it's trying to consider and a nightmare to migrate that framework. Django might have simplified some stuff, but it's still too opaque for my taste and the overall end goals of the project. Currently, I'm testing using graphjin (it doesn't have the best documentation, but it does boast an SQL generation capability that I philosophically think is the best way to do things).

Checkout GraphJin it's an automatic GraphQL to SQL compiler, you write your database queries in GraphQL instead of SQL and it compiles them into efficient SQL on the fly. Works as a library in GO and NodeJS. https://github.com/dosco/graphjin

In GraphJin an automatic GraphQL to SQL compiler we use the gnomock library it startups a database instance (docker) then create the schema and tests data and finally our code connects to it and runs a series of tests. We run these across Mysql, Postgres and a few other DB's. Gnomock supports a wide range of them. Right now we don't take down the db for every test only between test runs but its fast enough that we could. This whole thing runs of a simple `go test -v .` command and we run it on every commit using a githook. https://github.com/dosco/graphjin/blob/master/tests/dbint_te...

This was a bug in GraphJin it has since been fixed. The issue was that you were trying to have multiple subscriptions over a single websocket this did not work (it should) and now it does. https://github.com/dosco/graphjin/commit/43e619b2ff392dd42b99a4d56074a041a54b0e1c

Not exactly GraphQL is just a format to define what data you want back from someplace. You can use it in a browser app to request data from a backend GraphQL server or you can use it as an ORM within your backend app to fetch data from a database using a library like GraphJin. https://github.com/dosco/graphjin