Hey Team, Could anyone help me decide if prisma is ready for production or not ? I've used it for small projects but haven't seen an industry project for this. There are 2k + issues currently. Migration can't be rolled back schema file gets too large even my personal projects so not sure how can I break the file. I'm not sure but the ORM scene in node is bad, the Django ORM although using python is very nice and does everything you need from it. I wish I could find something like that on node

👋 @AnimeshRy that's an excellent question, thank you for joining the community and asking! The full Prisma ORM toolkit and the Prisma Data Platform are production-ready. We have more than 100k developers using Prisma and quite a few success stories, spanning from Enterprise use cases to open source and startup projects. It's true that we have lots of open GitHub Issues, but that's because we open an issue for all levels of issues and feature requests, we're very keen on recording all feedback! 😊 However, you raise interesting concerns here - @Austin or @nikolasburk could you address them, please?

Migration can't be rolled back schema file gets too large even my personal projects so not sure how can I break the file.

The number of issues on Github can be misleading. If you filter them by label, you would find that the actual confirmed bugs that have been re-produced are as low as 264

I also responded to a similar concern about the number of open issues on Reddit recently:

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 :)

Hope this gives somme additional perspective, Vladi and Omar were definitely on point here already!

Migration can’t be rolled back schema file gets too large even my personal projects so not sure how can I break the file.

• Regarding migrations: You _can_ generate down migrations with Prisma and also roll back migrations. However, we currently don’t have the familiar

up

and

down

commands that I think you might rather be referring to? That being said, our Product and Engineering teams have already acknowledged this as a problem and we’ll likely built these commands into the CLI in the future 👍 • Regarding the large schema file: This is indeed a limitation of Prisma, however the workarounds are pretty straightforward (either using simple bash scripts or one of the community tools like Autrora, you can find all of these workarounds in the GitHub issue)