Hmm, how does this compare to sequelize? Seems like the only reason to use prisma is the GraphQL integration. If anyone has used both please share. I've being mainly using sequelize and have being quite happy with it.
Can you elaborate what exactly you mean with "GraphQL integration"? You might be referring to Prisma 1 which was a "GraphQL layer for your database". Prisma 2 (which we are referring to with this article) doesn't have a native GraphQL integration any more :)
Prisma is very different from Sequelize in various ways (see our docs [1]):
- Your data model lives in the Prisma schema
- Database access doesn't happen via model instances but via the Prisma Client API [2] which always returns plain JS objects making your queries much easier to reason about
- Prisma Migrate auto-generates migrations based on your data model (and lets you customize these migrations when needed)
- Prisma comes with Prisma Studio out of the box – a modern database GUI
- Prisma is not a community-project but built by a VC-funded company
– We care a lot about our community, documentation, and providing support (something we've seen lots of developers complain about with other ORMs)
>Prisma is not a community-project but built by a VC-funded company
Thanks for clarifying this. I know there tend to be a kneejerk reaction towards VC-funded software projects. How do you guys plan to make money on this?
I think this quote summarizes our plans nicely: Prisma's vision is to democratize the custom data access layer used by companies like Facebook, Twitter and Airbnb and make it available to development teams and organizations of all sizes.
The open-source ORM we're launching today will of course remain open-source and we'll keep investing into it since it's be the foundation for the commercial tools that folks will be able to use on top.
