Let's compare 8 ways to work with SQL databases in a JavaScript project like Node.js or Next.js. Analyze the pros and cons of libraries and ORMs that can run Postgres queries in a fullstack framework. 

#sql #javascript #webdevelopment 

Learn more in full Next 13 Course https://fireship.io/courses/nextjs/

- pg https://github.com/brianc/node-postgres
- postgres.js https://github.com/porsager/postgres
- knex https://github.com/knex/knex
- kysely https://github.com/kysely-org/kysely
- sequelize https://github.com/sequelize/sequelize
- typeorm https://github.com/typeorm/typeorm
- prisma https://github.com/prisma/prisma
- drizzle https://github.com/drizzle-team/drizzle-orm

Beyond Fireship's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about coding best practices, web development techniques, and software engineering principles. With articles, tutorials, and case studies, Beyond Fireship provides  guidance and inspiration for building modern web applications and advancing technical skills.

Beyond Fireship

The post explores eight different ways to use a SQL database in a back-end JavaScript project, focusing on Postgres ORMs. It discusses the pros and cons of each approach, including tools like PG, Postgres JS, connects JS, keysole, sqlize, typo RM, Prisma, and drizzle orm. The post highlights the importance of developer experience, type safety, intellisense, and runtime performance.

I tried 8 different Postgres ORMs