Replacing TypeORM with Drizzle ORM in Vendure #2873
asonnleitner
started this conversation in
General
Replies: 1 comment
-
Thanks for your thoughtful proposal. Of all the TypeORM alternatives out there, Drizzle looks the most interesting to me. I'd be especially interested to hear anybody's experience using Drizzle on a very complex, high-data-volume project. If we would ever choose to move away from TypeORM, the effort involved would be truly huge. Not just for us, but for everyone who has a significant amount of plugin code which inevitably touches lots of TypeORM APIs. In fact, the amount of work, plus the inevitable fracturing of the ecosystem is such a huge risk that I'd consider forking TypeORM before going that route. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Discussion Topic: Replacing TypeORM with Drizzle ORM in Vendure
Hello Vendure Community,
I would like to open a discussion regarding the replacement of TypeORM with the more modern Drizzle ORM for Vendure's database interactions.
Current Situation:
TypeORM has been a go-to ORM, but it has shown several drawbacks, especially for larger projects. It can be slow, has become cumbersome to manage, and is not as actively maintained.
Proposal:
I would like to suggest considering migrating to Drizzle ORM. Here are the key benefits:
Advantages of Drizzle ORM:
Concerns and Considerations:
Call to Action:
I would love to hear the community's thoughts on this proposal. Have you experienced similar issues with TypeORM? Have you used Drizzle ORM, and if so, what has your experience been like? Let's discuss the potential challenges and benefits of making this switch.
Looking forward to a productive discussion!
Beta Was this translation helpful? Give feedback.
All reactions