Positioning of Drizzle

[balupton]

How does Drizzle position itself against other stack choices?

Context...

For myself, I'm primarily a devops dev the past 10 years, and need to get back into web site and app frameworks; I've built a few tiny apps over the years on cloudflare workers and kv, such as a billing an invoicing system a few years ago, however have spent a week researching my modern options... seems it is astro for web sites, remix for web apps; however for database, ideally I'd like to keep the entire stack cloudflare native, for performance, capability, and affordability reasons.... ideally there would be an orm + headless-crm + api-generator combo for cloudflare, but that combo isn't there yet, so been evaluating prisma, planetscale, fauna, kysely, trpc; and now found drizzle, which seems great, and meets my requirements for selecting cloudflare. Fauna has great features, however its pricing has always been the bottleneck for me.

I do imagine however that prisma will eventually bring out d1 support in a year or two, in which case, what is drizzle's plan or positioning then?

kysely also seems to be the most similar project to drizzle right now, so also wondering about that

[AlexBlokh]

hey, @balupton
If I'd to put our ORM into one liner, it'd be Take control over your data layer back. Drizzle ORM is aiming to fulfill vacuum of developer needs for in-between query builders on one hand and monstrous ORMs frameworks on the other.

I've wrote a couple of short articles [1, 2] about our philosophy of development tools for developers.

As of upcoming priorities:

1. We're going to have a completed list of dialects and driver plugins for all widespread/popular self-hosted databases or databases as services.
2. Invest a lot in DrizzleKit automatic migration generation tool we have
3. We're building SaaS for migrations management.
4. GraphQL and REST libraries for Drizzle ORM

In term of minor short term improvements - we're implementing next version of joins syntax, prepared statements for PostgreSQL(x2-x4 performance improvements), with operator and table views.

[AndriiSherman]

@mvp-joe Drizzle is open-source and released under Apache-2.0 license

[mvp-joe]

Awesome, thanks for the quick reply!

[SamueleBarbiera]

we can definitely make any adapter on top of our current implementation and we were designing our implementation keeping in mind every potential use case like graphql, zod, rest, etc. we're 100% pluggable in any developer environment

would also love to discuss the way you see how the best possible interface will look like as a user of the library, particularly for trpc+drizzle

it would be cool to have a zod crud schema created from the tables as the input for all the procedures

[205g0]

We're building SaaS for migrations management.

Do you mind do elaborate? Some extra visuals for your current mirgation cli tool? Or exxtra features. Or branching like with PlanetScale?

[tonyxiao]

@AlexBlokh could you guys make it possible to generate migration statements programmatically and give user the control to choose when to run it rather than directly running it with db push?

More specifically we are using drizzle to create and write to a bunch of dynamic tables that we don't know the names / schemas of ahead of time. Therefore it's not possible for us to easily use the traditional migration files approach.

[Azarattum]

I see a clear win in terms of TypeScript integration over Prisma. But what are your advantages over something like Kysely? They have tons of adapters as well and you query syntax is very similar. Are there any benefits to migrate existing projects from Kysely currently?

Also I see you have first class support for Zod. Do you plan to support other validation libraries? I personally like superstruct which is a faster simpler smaller alternative to Zod that also has a first class support from tRPC.

[hanssonduck]

@AndriiSherman exited to see db push come to drizzle. Is there any timeframe for when it will launch?

[AndriiSherman]

@hanssonduck it was just today! It's not latest, but just internal release that we opened for those, who wants to test it out and help us to find as much bugs as possible

You can read small docs on how to start testing db push
https://github.com/drizzle-team/drizzle-orm/blob/db-push-docs/docs/db-push.preview.md

[JoshStwrt]

@hanssonduck it was just today! It's not latest, but just internal release that we opened for those, who wants to test it out and help us to find as much bugs as possible

You can read small docs on how to start testing db push https://github.com/drizzle-team/drizzle-orm/blob/db-push-docs/docs/db-push.preview.md

Hi @AndriiSherman,

I was very happy to see the db push command making progress. One thought I had is instead of adding the database connection details to the config file, will you support environment variables? We're currently using Doppler and prefer keeping all our secrets there as opposed to adding them to our codebase.

[AndriiSherman]

@JoshStwrt yes!
It should be released in db-push tag this week
Join our Discord to get updates about db-push releases, before it goes to latest

[AndriiSherman]

@JoshStwrt you can check update docs for env variables

https://github.com/drizzle-team/drizzle-orm/blob/db-push-docs/docs/db-push.preview.md