Prisma - Build a GraphQL server with any database

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

Amazing product by an incedible team!

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