Our great sponsors
-
Prisma
Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
-
amplication
🔥🔥🔥 Open-source backend development platform. Build production-ready services without wasting time on repetitive coding.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Prisma has a lot of open issues on GitHub: Also true, however I'm not sure if this is the right metric to evaluate Prisma's maturity. We're using GitHub as the main way to track engineering tasks and product ideas, so the number of issues doesn't necessarily represent "problems" (even less so "critical bugs"). This also means that there are lots of "internal issues" that are not urgent in any way but rather flesh out ideas where we'd like to get feedback from the community. I also don't think the number of issues indicates a lack of maintenance — on the contrary actually, I'd rather recommend to look at the release notes to get an understanding how many issues are closed with each release to get an understanding about how active the development on the Prisma ORM actually is! Does this mitigate your concern about high number of open GitHub issues? If no, I'd be very curious to hear what exactly you find problematic about this :)
I'm really curious what makes you think that Prisma isn't ready for large projects? We've seen lots of companies building successful businesses (from small startups to enterprises) on top of Prisma already. We're listing a bunch of them on our Showcase page and you can also check out a number of real-world open-source apps that are built on Prisma, e.g. Cal.com (Calendly alternative with ~12k GitHub stars and >20k active users) or umami (Google Analytics alternative with ~12k GitHub stars).
Plus, Prisma is being adopted as the default ORM in popular frameworks like RedwoodJS, Blitz and other successful dev tools like Amplication and Keystone, so I'm wondering where this feeling comes from?
I'm really curious what makes you think that Prisma isn't ready for large projects? We've seen lots of companies building successful businesses (from small startups to enterprises) on top of Prisma already. We're listing a bunch of them on our Showcase page and you can also check out a number of real-world open-source apps that are built on Prisma, e.g. Cal.com (Calendly alternative with ~12k GitHub stars and >20k active users) or umami (Google Analytics alternative with ~12k GitHub stars).
Plus, Prisma is being adopted as the default ORM in popular frameworks like RedwoodJS, Blitz and other successful dev tools like Amplication and Keystone, so I'm wondering where this feeling comes from?
Plus, Prisma is being adopted as the default ORM in popular frameworks like RedwoodJS, Blitz and other successful dev tools like Amplication and Keystone, so I'm wondering where this feeling comes from?
Here is the post, u/BehindTheMath said "Raw SQL could be a viable option is there wasn't any JS logic and all the code was Knex." and I completely agree, and I can't even imagine how would you rewrite this knex code to raw sql.
You can avoid the n+1 problem in Sequelize by using dataloaders https://github.com/mickhansen/dataloader-sequelize