Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Prisma – An open-source GraphQL API layer for your database

blog.graph.cool

Post reply on HN
Print view View original

31–36 of 36 posts

Re: Prisma – An open-source GraphQL API layer for your database

#31

Post by sorenbs »

chewchew wrote: post #23

Graphcool is awesome. I think you guys made the right choice moving to a code-first, open-source platform. Obviously you still need to make money. Besides hosting and automatic backups, how will you monetize? What are your plans for Graphcool Enterprise on-premise?

Thanks a lot!

It was awesome to see how Graphcool enabled so many frontend developers to get started with backend development.

And it has been even more exciting to see these same developers move to a combination of Prisma and GraphQL bindings with relative ease.

The GraphQL ecosystem is maturing to a point where the tools are now easy enough to be used by small dev shops and powerful enough to be used by large enterprises. There was an episode on GraphQL Radio (https://graphqlradio.com/) diving into how IBM build their own library to standardise schema composition. This is a fairly advanced concept, but with GraphQL binding this is now part of day-to-day development for thousands of developers.

To address the money part - Enterprise and on-premise is certainly a thing. We get a lot of requests for custom setups. If you are interested to explore this option, please get in touch!

Re: Prisma – An open-source GraphQL API layer for your database

#33

Post by sorenbs »

d0100 wrote: post #24

I tried to use graph.cool as my first graphql project, everything was a breeze, except: * I couldn't for the life of me find out how to implement user auth. * The json fields are sooo small, it's a huge no-go for developers (like me) who are used to postgres's amazing json support. I ended up just using neelance's Go lib and postgres.

Thanks! Your experience match the feedback we are getting from a lot of people.

With Prisma we are focusing on the core technology and exposing as much raw database power as possible. We will implement native PostgreSQL support in the future to take advantage of the superior json handling

Re: Prisma – An open-source GraphQL API layer for your database

#34

Post by sorenbs »

rozenmd wrote: post #20
everdev wrote: post #2

These 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…

What's so difficult about just writing resolvers?

Implementing a single resolver is not difficult. The trouble starts when you need your server to operate fast and efficiently on a broad range of query patterns.

The switch from REST to GraphQL moves the burden of data fetching from client to server. As GraphQL is dynamic in nature you have to handle any query the frontend might send and can no longer rely on the static shape of a REST API when optimising your data access pattern.

The fundamental issue is that there is a big gap between the GraphQL API you want to expose and the underlying data layer you have available. Sometimes you need to combine data from several underlying databases making it critically important to perform data queries in the right order and in parallel when possible.

Think of Prisma as a GraphQL database query engine that analyses every incoming query in order to generate an optimal execution plan for your underlying databases.

Re: Prisma – An open-source GraphQL API layer for your database

#35

Post by caymanbruce »

sorenbs wrote: post #7
turtlebits wrote: post #5

I 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 pro…

The error messages need to be improved. Especially when the docker server logins failed.

Re: Prisma – An open-source GraphQL API layer for your database

#36

Post by TomMarius »

ruslan_talpa wrote: post #19
walshemj wrote: post #10

Earlier quoted context omitted.

should not your business login be in the database where it will runfaster as SPROCS

Usually people say the opposite, logic in db does not scale, though i don't know what scale are they talking about when modern databases (PostgreSQL/MySQL), on a single decent box can handle 1M+ TPS (and that is before using replicas to scale reads). As to your comment, nothing is black and white, but if the logic operates strictly on the data (not interfacing with 3rd party systems), having it in the db imo is bette…

They often mean "badly written logic in badly configured MySQL". Logic in DB(2) literally powers our world.
Post reply on HN