Jamie Barton

Prisma Cloud - GraphQL database platform

Prisma Cloud is a GraphQL-based database platform and is the easiest way to run Prisma in production.

- Serverless cluster hosting

- Powerful data browser to explore and edit data

- Team collaboration

- Metrics & database insights

Add a comment

Replies

Best
Brandon Bayer
Congrats!! What does the migration path look like from Graphcool cloud (I’m a graphcool customer)? I’m interested in migrating but don’t know where to start or what the changes are. Thanks!
Mo
@beedesignllc I think you're perfectly fine to continue using Graphcool, but feel free to read this for knowing the difference! https://www.graph.cool/forum/t/g...
Søren Bramer Schmidt
Hi Brandon! As Mohammad points out, you can continue to use Graphcool Framework for as long as you like. That being said, there are many benefits to Prisma, so I would suggest at least giving it a try to see if you would benefitting from migrating. The first thing to note is that the generated GraphQL API has been significantly improved. This means you will have to make small adjustments to most of your mutations and queries. The more significant change is that Graphcool Framework has build in constructs for business logic and authorisation. Prisma focuses exclusively on the connection between database and backend application. We have created some nifty open source libraries to bring a lot of the same out-of-the-box experience you know from Graphcool Framework to normal GraphQL backend development with Prisma, including GraphQL Bindings that provide smart schema stitching and auto-complete in your editor as seen in the video on https://www.prismagraphql.com/ Hope this helps you get an overview! Prisma should be very familiar to anyone coming from Graphcool, so I'd encourage you to just set aside half an hour to migrate your SDL and deploy your first Prisma service :-)
Huvik

I used Prisma cloud for 3 weeks and was amazed how good it is. I participated in beta and was satisfied how good support Graphcool provides for Prisma cloud. UI of prisma cloud is super easy to grasp even for not technical users. Everything is included and you don't need to take care of your prisma instance.

Pros:

Cloud provides you with metrics of usage and data browser for better data visualization. No need for your own server to run prisma.

Cons:

I couldn't find any yet

Alex Alexeev

I used their service starting from graphcool and I liked the direction they followed from then - open sourcing things and provide more controlled developer experience. Heads up!

Pros:

To me it is kinda the best approach to setup a new project that needs a DB, period

Cons:

see none:)

Sairam

Few things that would be pretty helpful (feature requests)

- Inbuilt support for authorization(roles/permission) for users at resource level (user/actions/resource - mapping).

- Server side subscriptions are great, Not an optimal solution to build chat applications based on client side subscriptions yet. Hopefully it will improve overtime.

Pros:

- Provides a great way to bootstrap your CRUD endpoints

- Flexible playground

- Data view to browse all the models in the cloud

Cons:

New technology. Not really a con per say - but, interested in seeing how it would scale with data.

Fabien Bernard

I have participated to the alpha/beta version, for me it's the best way to provide data to a GraphQL server (no more long queries, it's just efficient!). It's just a nice to have in every project.

Pros:

Easy to start and make your life really simplier with a graphql server \o/

Cons:

Young product! (but they are really reactive :) )

Flavian Desverne

Using Prisma Cloud with React and React Native can lead to multi-platform, production-ready apps within weeks.

Pros:

- Quick development

- Fast iterations

- We stay completely owner of our own data

- Collaborative

- Beautiful UI

Cons:

Front-end devs are about to steal our jobs.

Max Darque

I believe GraphQL is an incredibly powerful set of standards and querying language. It works really well between client and server. The hard part is building the GraphQL server.

The scope of queries and mutations can be very large and complex. How do you deal with this on the server? Do you write SQL to handle every possible combination? Do you write an SQL query for each field on a node thereby sacrificing performance?

My belief is that Prisma solves this key problem. On top of that it provides you with a powerful admin GUI and direct access to your database with GraphQL. This is a real time saver. Prisma also helps you manage the structure of your data inside your database. Big thumbs up from me.

There are a few teething issues with Prisma Cloud and it's GUI. Having used the beta and Graphcool BaaS, the Graphcool team move fast and are continually improving things.

Pros:

- Solves hardest GraphQL problem between db & app

- Speeds up development of GraphQL servers

- Bring your own database

- Powerful admin GUI

Cons:

- While, the Prisma software is fairly stable, Primsa Cloud has just exited beta and there are a few teething issues with the GUI

Søren Bramer Schmidt
Thanks Max - you are hitting the nail on the head! We se a future where Prisma can give you a unified GraphL API to interact with any kind of database you want. By strictly decoupling data querying from business logic we can optimise access patterns to different databases while keeping the code in your server simple and easy to maintain. We really appreciate your participation in the Prisma Cloud beta as it has helped us ironing out many of the small issues. There is a lot more to come :-D
Rex Raphael

Started using when it first became opensourced on Github. I was working with a REST framework at that that. Having heard of Graphql a year before with never really giving it time to learn. I needed a solution with flexible zigzag relationship query as I like to call it and Graphql seem like the best answer so I decided to give it a shot. I started writing graphql server and query and while it was fine the resolver API was quite something to write. ou just have sweat that part out.

I needed to work fast and get result in weeks and I heard of Graphcool gave it a shot it was awesome, but I still felt something was missing in how API to database should be written and handled.

Then 3 days time I signed back into the Graphcool slack community and there was a huge confusion as to a new service called Prisma or a rename. I treated it with the "are we ever gonna stop trying to catch up with software trends". Then I gave it a go.

And I was blown away by how simple and straight to the point the resolver API was and the typescript support with Visual Studio Code IS was amazing. It changed my perception on how to handle CRUD hooks and events, not that it was flawed but improved. You think that was all and then Prisma Cloud made deploying prisma apps effortless with one simple command, with a modern admin UI

Right now I'm using Prisma Cloud for a client a contract project. called Unizonn it's a social media for students and academia and that fused with the power of Prisma Cloud. Prisma Cloud Rocks

Pros:

Power, simple and easy to understand UI/UX. Easy deployment, with powerful dashboard.

Cons:

None

Noah Miller Davis

Prisma absolutely revolutionized the way we build products at MarketMuse. It has freed our teams from endless conversations and enabled us to just start building. Every new project I start will be using Prisma in the future and then leveraging the power of the Prisma Cloud platform to take all of the annoying work off my plate and let me focus on what my team and I do best.

Pros:

Great features for my entire team to utilize Prisma outside of standard development. Prisma is just plain awesome, so more Prisma == Dreamy

Cons:

Nothing has been negative in my team's experience so far.

Dennis Walsh

This is the easiest and best way to abstract the complexity of database schema and migrations when integrating a GraphQL server. I love it and am excited for the future!

Pros:

Effortless Connections, Subscriptions, Queries, and Mutations

Database schema and migrations reduced to `prisma deploy`

Cons:

GraphQL as a whole is still developing best practices