We are using Prisma in production and we are supper happy with it. Prisma offers great flexibility in creating rich APIs. We have prisma 3 months in production and had no problems at all.

Prisma is backed by great team and provides a lot of sources in bleeding edge technology world.

Pros:

Easy to use, flexible, rock solid, offers great developer tools, good support

Cons:

I couldn't find any

I never had a database/backend up and running so fast. Especially loving the new architecture which gives full flexibility to the developer regarding authentication of users and authorisation to change/access data. It is also easy to integrate data from other services into the own API, no vendor lock in at all!

I recently reported an issue on a Friday afternoon on GitHub and it was solved within 24 hours, which is just great.

I can really recommend Prisma!

Pros:

Super easy to get started and iterate

Cons:

No backups yet, but they are coming soon

I have followed the team pretty much since they launched the beta of Graphcool more than two years ago. Since then I've watched them iterate on the product, rewrite it, write a ton of open-source libraries, and rewrite it again to deliver the best tool to build your own GraphQL server.

The GraphQL community today stands on three pillars: Apollo, Prisma, and Facebook itself. It's amazing to see these guys evolve the product and take the company to the next stage.

Pros:

Awesome team that's heavily involved in open-source and pushing GraphQL forward.

Cons:

I liked the cool Graphcool name.

I used Prisma on a pet project only and did like that it gives you db and bindnings to it out of the box, it also helps to generate queries and mutations for new entities and more. Beside that, I really like what guys from graph.cool are doing. Kudos!

Pros:

easy to use, db friendly, nice community

Cons:

still new

Graphcool really makes graphQL a reality! As a frontend developer i'd wish that i'd never had to use REST again! GraphQL is awesome, and I believe that Prisma can help me get the full team on board, and we'll be able to scale and make better apps and sites!

Pros:

Best team behind this fantastic product!

Cons:

None, these guys are the best, and i've used all their former products with no regrets!

I love the way Prisma allows me to describe my data model definitively. Backed by powerful server stack, it is super easy to bring power of GraphQL to my projects. It thoroughly changed the way I approach creating applications.

Pros:

Prisma is extremly easy to use and has super intuitive API! The time I spend on backend has been more than halved.

Cons:

You have to rethink your choices.

GraphQL is a powerful specification that enables APIs to be developed quickly. In the right conditions, new development and redesign of existing systems can benefit. Prisma takes an novel approach to implementing the spec. Tons of potential, in my opinion.

Pros:

Fills a void in an exciting space. Fabulous support from devs and the broader community. Very exciting aspects being actively developed.

Cons:

Still evolving, but doing so quickly and reliably.

Prisma has been an absolute dream to work with. It allows us build our backend way faster then we could have with a regular database -> graphql connection.

The docs are great and easy to read and the (slack) community is active and helpful. This is definitely our number one pick when setting up a new backend stack!

Pros:

Super ease to use, great docs, active community, awesome DX

Cons:

Still relatively new

I have been using prisma for a long time and before that graphcool and for my experience it's amazing!

@

©They are also all incredi people !

Pros:

Everything this guys make is all I ever wanted in web dev

Cons:

None so far

Love this technology and how it makes graphql easier even for complex schemas.

Pros:

Abstracts the database beautifully

Cons:

Have to use Docker

With a few lines of code your app is up and running with a great stack.

Pros:

Easy to start, fully open source, great docs, great slack support

Cons:

Some features missing but they move very fast!

I've used Prisma in a project and it's working great so far! The docs are very good, support is really good (they really think along with you), and the Slack community is active.

While I'd recommend Prisma Cloud, you can also host it yourself. This is a huge deal if you can't use their cloud e.g. due to compliance reasons. I also really appreciate everything that Prisma does for the GraphQL community, packages like graphql-yoga and graphql-import. This really improves the trust I have in the company.

One area that I'd really love to see improvements on is migrations. For example, you have a "lastLogin" field on the user but you want to move this to a separate SQL table without losing data. It might be out-of-scope for Prisma, so this could be a nice opportunity for another OSS package.

Prisma already has a lot of good examples on how to do auth, etc. I look forward to even more real-world examples.

Pros:

Easy to get started, OSS so no vendor lock-in

Cons:

None

I really like the idea of Prisma. It has allowed me to quickly create an API for my last app which would take weeks to do using traditional frameworks. The built-in GraphQl playground is one the best features of Prisma. It enables me to write and test my queries before I put them in my app, the auto-completion really helps here. Overall one of the best development tools I have ever used.

Pros:

Fast API creation with complex relations

Cons:

Very error-prone installation and configuration

We have been working with the Prisma team for almost a year (v0.x to now 1.8.3). Their tireless commitment to quality and leading the GraphQL space is not easy. We have witnessed hyper releases of their product and have rarely been "burned" for early adoption. The latest release is by far their strongest. They provide a multi-tiered software structure in an otherwise immature space and back it up with hosted services. The attitude of the organization is to not "lock" you into their hosted services or any of their tiers. Simply what works for your business is for your organization to decide. They are more interested in the relationship than a one-size fits all solution as they know this space will continue to mature. To that end, the ease of use and design pattern they strongly suggest does offer a lot of capabilities and flexibility to fit the needs of many. We have found ourselves quite comfortable with the solution and are in fact spending all of our time on business logic and custom APIs rather than battling the nuances of graphql and database support. Once you do understand the proposed design patterns though, it is pretty remarkable how fast you can bring capabilities to your applications. We have standardized Prisma as our low-latency database access layer for all our applications.

If you are more than a hobbyist, I do encourage you to try their enterprise package as it does come with dedicated support channels. The more customized solution you intend on having (including hosting one or all of your own tiers), the more in charge you have to be of your own upgrades. We found having dedicated channels as extremely helpful.

Pros:

A true leader in the GraphQL and DB/API as a Service community

Cons:

GraphQL is still early and not a lot of mature competition, potential vendor lock

Use this on my personal projects to build out graphql API's very fast. Extremely fast to get going and great support from the community. I don't think I have ever had a basic API up and running so fast before.

Pros:

very fast to get going, great docs, great community and support

Cons:

Error messages can be ambiguous

we are building a new product based on prisma and were using CakePHP before. It was easy to setup. Any problems we experienced were solved by the Slack / Forum community in no time.

Fantastic product!

Pros:

easy to start, great team that answers questions blazing fast

Cons:

documentation was outdated with a few examples but community helped with all problems

Prisma is magic.

Pros:

Drastically lowers the barrier to entry re GraphQL ecosystem.

Cons:

Because the abstraction is SO good, users w/o backend/DB exp may find discerning bounds of Prisma's capabilities and limitations difficult

I have been shying away from building GraphQL servers because of how resolvers can get intimidating for complex scenarios. Prisma just made it dead simple with its bindings.

Pros:

Prisma just took the entire GraphQL developer experience to the next level

Cons:

None for now.

This is, by far the best GraphQL server solution out there. The out of the box crud queries and mutations are great. Don't have much bad to say at all.

Pros:

Awesome product, great community, would recommend for any new backend.

Cons:

Still a bit new and working out the kinks, but they are few and far between

Nice framework (y)

Pros:

Awesome data layer!

Cons:

No Rest API

Best way to start a GraphQL Server

Pros:

Easy to use, good support and Open Source

Cons:

New price strategy to use their cloud

Very interesting and productive.

Pros:

Interesting tools to develop with. Easy way to migrate your database to graphql.

Cons:

Need better practices. Need better mysql support (Currently no migration is supported).

They fill an important space in the graphQL ecosystem.

Pros:

Ease of getting something up and running. Clear vision for the future.

Cons:

Very new, so some difficulties to be expected.