Live data from Hacker News

Learn GraphQL by querying JSON

graphql.college

1–10 of 20 posts

Re: Learn GraphQL by querying JSON

#7

For me GraphQL adds a lot of complexity when setting up the API for only an incremental benefit when querying. Do others feel the same? Or am I missing something?

It's a pretty great format for rapid prototyping, but very complex and wouldn't deploy it as a public API that needs to be supported for a long time.

Re: Learn GraphQL by querying JSON

#8
post #7

For me GraphQL adds a lot of complexity when setting up the API for only an incremental benefit when querying. Do others feel the same? Or am I missing something?

It's a pretty great format for rapid prototyping, but very complex and wouldn't deploy it as a public API that needs to be supported for a long time.

Thats what I thought at first as well. But as I started working deeper and using more frameworks (had to write some as well) that made the complexity go away. Adding data sources can be very easy and the frameworks, like Apollo, take care of all the things you had to think about previously. I know that there are of course frameworks that handle cacheing and query routing for REST apis, but the flexibility of GraphQL is unparalleled. I find them to be best suited to backing UI's that may get rethought and reworked every 6mo to a year. As well as for data analytics ad hoc queries.

My point is the can be very complex, but they don't have to be. I have a number of them deployed right now that are far more hands off for me than our other APIs.

Re: Learn GraphQL by querying JSON

#9
Looks like a low friction way to bring on new team members to GraphQL.

However, the tools is either broken or not finished yet. I tried to change posts to books in the JSON tab and I get an error below: "Cannot extend type "Post" because it does not exist in the existing schema."

Post reply on HN