Live data from Hacker News

Ask HN: Is GraphQL still relevant?

news.ycombinator.com

11–16 of 16 posts

Re: Ask HN: Is GraphQL still relevant?

#11
I'm using it at work to develop an API and I'd say that it's been a great experience. I find that it fits well with our use case.

I find it works well for when we need to collect information from several places at once which in our older API required several requests to REST endpoints. Now we have a single request and a much faster response time.

Re: Ask HN: Is GraphQL still relevant?

#13
post #4
post #2

If you search for "graphql whitepaper", you may find some useful material about that. https://www.google.com/search?q=graphql+whitepaper

Funnily enough, this comment thread is the third result I get.

That's indeed funny. I hope it makes to the top :-)

Re: Ask HN: Is GraphQL still relevant?

#14

I'm using it at work to develop an API and I'd say that it's been a great experience. I find that it fits well with our use case. I find it works well for when we need to collect information from several places at once which in our older API required several requests to REST endpoints. Now we have a single request and a much faster response time.

> I find that it fits well with our use case.

What's your use case? Also, how difficult is it to create and maintain the API? I hear nothing but good things about it from the frontend people, but some of the backend people I've asked about it just mutter to themselves about increased complexity then run away. Which also makes me think I need to become friends with backend people who don't mutter to themselves, but one thing at a time.

Re: Ask HN: Is GraphQL still relevant?

#15

I'm using it at work to develop an API and I'd say that it's been a great experience. I find that it fits well with our use case. I find it works well for when we need to collect information from several places at once which in our older API required several requests to REST endpoints. Now we have a single request and a much faster response time.

> I find that it fits well with our use case. What's your use case? Also, how difficult is it to create and maintain the API? I hear nothing but good things about it from the frontend people, but some of the backend people I've asked about it just mutter to themselves about increased complexity then run away. Which also makes me think I need to become friends with backend people who don't mutter to themselves, but on…

A platform which handles listings and bookings. I work primarily on the backend and haven't really felt any discomfort in terms of complexity. It just gives a lot of flexibility in how we work with the data that we have and what we can offer to the frontend.

The stack is GraphQL Yoga and Prisma which simplifies things quite a bit!

Re: Ask HN: Is GraphQL still relevant?

#16
We tried to migrate an old gigantic legacy software from REST to GraphQL and left it in midway. We were just not convinced by the effort which goes into creating and maintaining the GraphQL layer.

We went ahead with JSON RPC

https://www.jsonrpc.org/specification

JSON/RPC is much simpler to implement and consume. You just have to expose server-side functions as endpoints and when it comes to build authentication and Authorization you can build using (Python or Typescript like) Decorator or just a Higher Order Functions which wraps the functions to be exposed to control the input and output in aspected oriented way.

Post reply on HN