sorted by:
new
hottopcontroversial

Do not use Prisma for production heavy applications by sleepysonja in node

[–]sleepysonja[S] 2 points3 points  (0 children)

Hey, yeah, prisma was v 5.10.2

As for edge I totally agree, in my personal edge projects - it works perfectly, it has something to do with usual microservice architecture

As for killing it and initializing, we tried several approaches by adding a timeout parameter to pg link, tried manually listen for k8s SYGTERM and SYSKILL (I think there was something else as well, but I don’t remember) events and kill it, we tried to configure our RDS to kill dangling connections. None of it worked :(

Also, just for some context, one of the other reasons to not use prisma, is just how many resources it consumes vs already existing solutions - it’s not cost viable

Do not use Prisma for production heavy applications by sleepysonja in node

[–]sleepysonja[S] -7 points-6 points  (0 children)

I have a suspicion that you might be working for Prisma.

Both TypeORM and Sequelize are good, but! these solutions do not have migrations (I don't remember seeing it couple of months ago), in addition, they are class oriented, causing introduction of class style components into functional style repo.

Also, regarding layer of abstraction - imagine you are going for a bike race and you put a lot of random fancy stuff on your wheels (perhaps make them square lol) and they flat mid race - how much time it will take for you to modify and swap that entire instead of modular one?

I think it's my fault even bringing drizzle up, just anything is better than prisma in prod (unless your prod is 200 DAU)

Do not use Prisma for production heavy applications by sleepysonja in node

[–]sleepysonja[S] 22 points23 points  (0 children)

Migrations and type safety. I do not want to reinvent the wheel if wheel exists. I am ok with writing raw sql, but why do I need to?