thin-backend VS TypeORM

A tool like https://thin.dev/ might be good for you. You can port and serve functionality a little bit at a time into thin and use their managed postgres db and the schema editor to handle the new fields in the backend.

Check out thin.dev https://thin.dev/ It uses SQL DDL statements literally as the building blocks for everything.

Postgres database has been gaining more popularity because of its advanced database and scalability. Created by digitally induced, Thin Backend is simplifying Postgres by giving users a backend server that has an API that connects with Postgres DB. You can integrate Thin Backend with:

React for UI TypeScript for Type Safety thin.dev for Data + State management

Check out https://thin.dev/ :) It's similar, supports self-hosting and uses postgres. Quick demo video here: https://www.youtube.com/watch?v=-jj19fpkd2c&t=3s

(I'm founder of Thin)

Real-time by default for everything is really a fun way to write web apps. A little bit inspired by Meteor we've build Thin Backend, which provides a real-time API for querying data and writing to a postgres database. If you're interested, check it out at https://thin.dev/ or check the demo video https://www.youtube.com/watch?v=-jj19fpkd2c

If you're curious, give it a try at thin.dev.

TypeORM - ⚠️ o'rtacha, cli tool bor lekin unchalik aniq migration querylar generate qilib bermaydi va asosan buggy

Let's talk databases. In TypeScript, if you want to interact with a database safely and cleanly, you're often forced to use an ORM like Prisma (They dropped Rust for TypeScript. We're not mad, just disappointed.), or TypeORM. These ORMs generate types based on your schema, or vice versa. Sounds good in theory. But in reality, you're juggling SQL migrations, type generation, inconsistent runtime checks, and you're praying to the gods of npx every time you need to change a column name.

Relevant links to read more https://www.prisma.io/ https://typeorm.io/

TypeORM as the ORM

TypeORM GitHub Repository: https://github.com/typeorm/typeorm

In my project I also use TypeORM with plugin for NestJS. To do this I needed to add custom options for esbuild. I implemented a feature similar to custom-esbuild to allow users to add their own plugins to the build.

TypeORM will be the ORM to interact with our PostgreSQL database. An ORM stands for Object-Relational Mapping and is used to interact with relational databases like MySQL, PostgreSQL, or Oracle. Also, we need TypeORM-Nestjs integration. Run the command below to install it.

Let’s walk through an example where we integrate with an SQLite database using TypeORM.

// src/main/database/dataSource.ts import path from "node:path"; import "reflect-metadata"; import { DataSource } from "typeorm"; import { UserEntity } from "./entities/user/user.entity"; import { PostEntity } from "./entities/post/post.entity"; const isElectron = !!process.versions.electron; # simple trick to see if the data source is called from the Electron app or CLI (for migrations scripts) const isProduction = process.env.NODE_ENV === "production"; let databasePath: string; if (isElectron) { // eslint-disable-next-line @typescript-eslint/no-require-imports const { app } = require("electron"); databasePath = path.join( app.getPath("userData"), app.isPackaged ? "app-name.sqlite" : "app-name.dev.sqlite" ); } else { // use hardcoded path for running migrations in development (macOS) databasePath = path.join( "/Users/user/Library/Application Support/app-name/", isProduction ? "app-name.sqlite" : "app-name.dev.sqlite" ); } // https://typeorm.io/data-source-options#better-sqlite3-data-source-options const dataSource = new DataSource({ type: "better-sqlite3", database: databasePath, entities: [UserEntity, PostEntity], migrations: [ path.join(__dirname, isElectron ? "database" : "", "/migrations/*.{js,ts}"), ], synchronize: false, # important logging: true # use this for debugging }); export const entityManager = dataSource.createEntityManager(); export default dataSource;