node-pg-migrate VS diagrams

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

diagrams - Diagram as Code.

Mingrammer is an intriguing tool for individuals who prefer coding diagrams rather than creating them through graphical interfaces. It operates using Python code and offers a relatively quick setup process. It is compatible with AWS, Azure, GCP, Alibaba, and Oracle. Notably, the project is open source and has garnered significant attention on GitHub with over 31K stars.

Ja sam koristio ovo: https://diagrams.mingrammer.com/

That’s another option: https://diagrams.mingrammer.com Guessing with IaC done with Pulumi (Python) and this, it could pretty powerful and automatically generated.

Diagrams allow you to draw cloud system architectures using Python code.

I use excalidraw a lot for short conversations. If I have to go into major detail I use diagrams https://diagrams.mingrammer.com