Hello everyone! I'm kind of confused now... I'm currently creating my first react-based website and I want to use GRAPHQL in it. Currently I'm using the console on graph.cool as my API endpoint. After experimenting with PRISMA, I came to the conclusion, that my planned service would probably be better off, if I keep using Graphcool BaaS, because I'm hosting the service beside my regular job and don't want to spend the extra amount of time for creating and hosting a complete backend for this "application". I'm just wondering, if Graphcool BaaS is still the way to go, respectively if it won't be outdated with the release of Prisma. Additional to that I don't know the necessary steps to make an api endpoint from Graphcool BaaS production ready. I couldn't find any resources concerning the production state of an API service provided by Graphcool BaaS. Could anyone of you bring light in my darkness? 🙂

https://www.graph.cool/docs/reference/service-definition/deploying-services-ioqu7arooj, https://www.graph.cool/docs/reference/graphcool-cli/graphcoolrc-zoug8seen4#managing-targets-in-a-local-.graphcoolrc

as far as making it production ready, make sure you have permissions locked down, and pay for an account so you have backups and it should be good to go

@tsdexterThank you! Yeah, I know about the dependency regarding the reliability of the cloud, when using a BaaS. The most important thing I'm concerned about is the future capability of the cloud. I'm worried that some features of the cloud might be changed with the inclusion of prisma.

thats a good thing though. you’ll start to run into the limts of the current api pretty quick… can’t wait for upsertMany for example in the gc baas… but hopefully they’ll launch it with a new endpoint or at least keep all existing api queries/mutations intact

@Matt Sutkowski Thank you, but your links cover only the cli as far as I could see. I was talking about the cloud service of graphcool.

ps. cli pertains to cloud too… we use the cli to dev and push to graphcool

Ah I see.

for example,

gcf deploy -t production

deploys to graphcool baas associated with production target in the .graphcoolrc file

But is it really necessary to "Upgrade Project"?

no

Hey @pasa, thanks for your question 🙂 Graphcool Cloud received continued support! We're improving its reliability and performance on an on-going basis as well. However, Graphcool will not receive Prisma features in the foreseeable future. Also check https://graphcool.slack.com/archives/C0MQJ62NL/p1520267649000271?thread_ts=1520260367.000430&cid=C0MQJ62NL

just nicer when you start doing a lot of custom resolvers and having multiple baas’s

I don't think that I will need custom resolvers. I just stumbled upon a simple problem, which eventually lead to a situation, where a very helpful community member adviced me to switch over to prisma. But actually I don't see a really good reason to have to handle another server for the backend and maybe a third one for the database, when I consider the actual size of my application.

@pasa keep in mind Prisma also comes with development clusters that take care of the DB as well 🙂

yeah, the web console can accommodate many scenarios and you may never need to switch out of it… but keep in mind, you can upgrade and use CLI without going to prisma..

@tsdexter I do understand the possibilities of handling multiple backends trough the cli. Thank you! 🙂 I just don't think my application will reach a level of complexity, where this will be necessary.

yeah, i’d just stick to web console configuration until you outgrow it

@nilan I'm not worried about the dev stage, but about the prod stage. I do have a private dev server, where I could host a mysql service, but I would never do that for a prod stage. 😉 @tsdexter Thank you very much! You were a great help! 🙂 I'm not trying to close up on all of those capabilities, which will and have come with Prisma or the CLI for Graphcool, I'm just trying to keep the overhead as small as possible, as I'm working on multiple projects at once (in different languages and frameworks).

👍 no problem. Good luck.