Performance of Prisma
is using Prisma in production save ? I have heard so much negativity regarding ORM . One argument with which they come up is if you really want to use ORM use raw query instead of ORM native function ? Is there a really performance lacking in native ORM functions.
3 Replies
Prisma is generally recommended just because of the velocity in can enable you when you are trying to find market fit. Any ORM is an api to clear up some of the more tedious parts of sql but it comes at a cost
Generally you’ll have inefficient queries that would usually be more performant if you did them by hand but sometimes the perf is enough for people
For production it’s fine. I’ve used it and it works but as always there are trade offs
Thanks for the quick response.One more question . DId you use native Prisma function or the raw query with prisma.$rawquery . Did you Prisma native function for relations .
Raw queries are by themselves fine by query standards aside from cold start related issue or waiting for a connection
but you can dig yourself into a hole by poorly defining a schema and having to work w it after 😭
At the start i was def using it more in that way but I've shifted it to mostly being entity management (having structs generated for me) and migrations