Prisma – An open-source GraphQL API layer for your database
blog.graph.cool
Prisma – An open-source GraphQL API layer for your database
1–10 of 36 posts
Re: Prisma – An open-source GraphQL API layer for your database
#2These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments.
Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code.
In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: https://www.graphile.org/
Re: Prisma – An open-source GraphQL API layer for your database
#3These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments. Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code. In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: http…
I think the point of this release is to open up operations outside of CRUD. I'm not sure if you've been following graph.cool, but they've been having a lot of churn over the past few months. The issue you bring up about CRUD has been addressed and is one of the main reasons for this new release, as far as I understand.
Re: Prisma – An open-source GraphQL API layer for your database
#4These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments. Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code. In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: http…
How does Prisma cause your backend logic to move into the database? I don't believe you need to add stored procedures to use it, you just write GraphQL resolvers for nodejs as per usual.
Re: Prisma – An open-source GraphQL API layer for your database
#5I tried to deploy this the other day and got stuck waiting in it's wizard to create a bunch of docker containers. (which I waited 30 minutes then gave up)
I'd like it more if it was just a standalone server and not a bunch of "magic" scripts to standup/deploy.
Re: Prisma – An open-source GraphQL API layer for your database
#6These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments. Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code. In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: http…
Thanks everdev!
Postgraphile is a pretty cool project that was on hn yesterday actually https://news.ycombinator.com/item?id=16150663
PostGraphile and Prisma takes different approaches in that PostGraphile embraces the power of PostgreSQL and encourages you to place business logic in the database.
Prisma on the other hand is a separate piece of infrastructure that you deploy in front of a database to add extra functionality such as realtime subscriptions, rate limiting etc.
If you haven't checked it out yet, then I'd encourage you to take a look at GraphQL bindings and how that allows you to work with your own server for more complex scenarios: https://blog.graph.cool/reusing-composing-graphql-apis-with-...
Re: Prisma – An open-source GraphQL API layer for your database
#7I tried to deploy this the other day and got stuck waiting in it's wizard to create a bunch of docker containers. (which I waited 30 minutes then gave up) I'd like it more if it was just a standalone server and not a bunch of "magic" scripts to standup/deploy.
Hi Turtlebits.
I'm sorry you got stuck setting up docker on your local machine. We have put a lot of work into making sure local clusters "just work". It would be a big help if you could start a thread on the forum so we can help identify the issue.
The reason we are using docker to run Prisma locally is that we believe it is super important to have the same environment locally when you develop as when you run in production.
If you are familiar with docker you can follow the guide in the docs to set it all up without relying on the CLI. That should give you a little more transparency into what is going on :-)
Re: Prisma – An open-source GraphQL API layer for your database
#8These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments. Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code. In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: http…
Ha ha I love when I get excited about something "new" only to find that I've already starred it on GitHub. I might have a "star and forget" problem...
Re: Prisma – An open-source GraphQL API layer for your database
#9I've been using graphcool (0.1) for quite some time, on a paid plan.
I feel so lost with so many changes lately, graphcool 1.0, now prisma, first it was a baas, then open sourced, then only a graphql database, etc.
My question are (and I totally thank you guys for the great tool you created)
#1 how will you profit from it? I need to make sure we invest in a tool that will be supported.
#2, how do I migrate? I understand that now I have to take care of a lot more than before, but the information available ain't clear, instead of saying "Hey, we no longer will create everything for you, make sure you learn how to tie graphql-yoga + bindings+ prisma" you were saying "We will focus on graphql database" which led us wonder what it meant.
I think your decision to focus on the hard problem is the right one, it just that our relation as users/customers of graphcool has changed and that wasn't very well explained.
keep the great work!
Re: Prisma – An open-source GraphQL API layer for your database
#10These DB -> API tools show promise, until you want to do something outside the CRUD box like upload images or process payments. Also, I've found it much harder to modify functionality because now your business logic is embedded in your DB which is harder to version than backend code. In any event, if you want a GraphQL/DB API and don't want to pay for graph.cool, there's a great similar tool called PostGraphile: http…
should not your business login be in the database where it will runfaster as SPROCS