About a month ago, we announced the developer preview of Prisma, initially calling it Graphcool 1.0. The release of Prisma earlier this week was met with lots of positive feedback and excitement.
Both events have resulted in many questions and confusion in our community that I’d like to address in this post.
The Graphcool Framework is an open-source technology, that provides a GraphQL backend solution based on an opinionated stack:
- A powerful GraphQL query engine
- A serverless function component, providing means to implement common workflows like authentication or other business logic
- A permission system, based on GraphQL permission queries
graphcool CLI, that is used to deploy a specific configuration of the above components to a Graphcool service
You can host your Graphcool services yourself, or in our hosting service Graphcool Cloud. You can read more about the Graphcool Framework in the documentation.
Prisma is an open-source GraphQL query engine, turning your database into a GraphQL API. It is based on the query engine used in Graphcool Framework, and comes with a revamped API design.
You can choose to connect to Prisma directly from frontend applications, but most larger applications need a server in front of Prisma to handle business logic.
Concepts like GraphQL Bindings reduce complexity in implementing your GraphQL Server. For Prisma specifically, we recommend the combination of
You can use the
prisma CLI to deploy a data model to a Prisma service, either locally or on a service like Digital Ocean. We will share more information about a hosted Prisma API service soon.
Read more about Prisma here.
Graphcool Framework or Prisma?
Graphcool Framework is an all-in-one backend solution, that’s a great fit if you want to have a fully fledged GraphQL backend.
Prisma is dealing mostly with the data layer itself, and integrates nicely with available GraphQL tools like
graphql-tools and others.
If you like the concepts and features of Graphcool Framework and it fits your use case, you can keep using it like nothing changed. If you like have more flexibility and more choice in how to put together your GraphQL backend stack, then I encourage you to check out Prisma for your next project.
At a later point, we will integrate Prisma back into the Graphcool Framework.
Due to several renamings of repositories and both CLIs during the Prisma developer preview, you might come across inaccurate documentation or broken links. We are currently going through all our resources accordingly. If you encounter anything unexpected, you are welcome to provide your feedback here.
If you have any question at all about the Graphcool Framework or Prisma, don’t hesitate to post it in this thread.