Managing Complexity with Separate Dialects for Specific Databases

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The chapter delves into the importance of supporting multiple technologies in a project while maintaining compatibility and flexibility. It highlights the advantage of using separate dialects per specific database, like PostgreSQL, to ensure efficient feature management and faster iterations.

Scott and Wes chat with Alex Blokh and Andrew Sherman, the co-founders of Drizzle ORM, about building a modern ORM from the ground up. They dive into the importance of type safety, creating filters with Drizzle, and the differences between Drizzle and other ORMs like Prisma.

Show Notes

00:00 Welcome to Syntax!
- Syntax × Drizzle Swag.
01:15 What is Drizzle?
02:36 The genesis of Drizzle.
04:15 The process of building an ORM.
05:38 ‘100% Type-Safe’ and why that’s not a great goal.
07:50 Who is responsible for writing the complicated TypeScript?
09:40 Is an ORM necessary for anyone working with data?
12:15 Creating a product that fits different complexities.
13:19 Brought to you by Sentry.io.
13:44 Creating filters in Drizzle. Callback-based, or imported. Why?
19:22 Drizzle vs Prisma vs Kysely.
22:45 Are you friendly with Prisma?
23:35 Relational queries.
25:17 Query vs select.
27:42 Maintaining so many different technologies.
30:37 Switching databases.
31:39 Drizzle Studio.
- Drizzle Studio Syntax Theme.
35:00 Accessing Cloudflare D1 SQLite requires connection through a worker.
37:40 Drizzle Kit.
41:37 Will you ever support MongoDB?
42:10 Supporting PGlite and local data storage landscape.
- DrizzleORM v0.30.6 release notes.
44:00 Being a developer in Ukraine in 2024.
- How to support Ukraine: Savelife, United24.
51:07 Drizzle is expanding.
53:50 Sick Picks + Shameless Plugs.