Is drizzle safe to use in production?
I would like to use drizzle(orm and kit) on new projects.
I get confronted with arguments like, is it battle tested, or drizzle is still in beta, or it's new and there might be some hidden bugs that would lead to data loss, like accidentally dropping some columns, tables, etc...
I think that time will battle test drizzle,
And I think that drizzle will just be better and better over time.
I am not sure what the current state is.
What do other people think,
what are your experiences?
4 Replies
My company is using it in production for multiple applications, and we have had zero issues. Drizzle is mostly just wrapping battle-tested drivers to execute the SQL you tell it to. So we feel pretty confident that we shouldn't expect any surprises.
However, there was a recent bug in the migrations functionality that DID cause tables to be dropped, so certainly take that into consideration. Even newer, battle-tested libraries can introduce bugs. We test everything locally and in staging before things ever make it to prod. We have regular database backups. A table-dropping bug is definitely serious, but you should be approaching EVERY library, old or new, with caution.
Drizzle-kit is in schedule to be open-sourced by the end of the month, I think it will get a lot better
@soulsizzle have you got a link to any GH issues regarding that?
GitHub
Generating Migrations: Update to 0.20.0 causes dropping of all tabl...
Issue Description: After a recent update to drizzle-kit 0.20.0, we've encountered a critical issue where generating new SQL migrations results in the unintended dropping of all tables, with the...