News for hackers. Stuff that matters.

A comment on Why, after 6 years, I'm over GraphQL. Parent comment

Re:Why, after 6 years, I'm over GraphQL by randomdata on Thursday May 30, 2024 @10:35PM (#40530928)
If you go back to the early stuff coming out of Facebook about GraphQL, it was designed to roll up all the REST services (or similar) into a single request for high latency clients. Occupying what has become known as the backends for frontends (BFF) layer.

In theory, it should be just as obvious either way as your actual services are going to be REST (or similar) either way. I recognize that some people have started using it as a poor man's SQL, but that's not really what it is for.

[ Parent | on HN ]
Re:Why, after 6 years, I'm over GraphQL by hamandcheese on Thursday May 30, 2024 @10:50PM (#40531029)
In the wild, I primarily have seen graphql implemented instead of, or perhaps next to, REST. Not on top of REST.

I'm not sure what you mean about a poor man's SQL. Whether it's backed by micro-services via REST, or just a graphql API in a single app, the value prop for frontend<>backend communication is the same. It's not "using graphql wrong" to not have a micro service architecture.

[ Parent | on HN ]
Re:Why, after 6 years, I'm over GraphQL by randomdata on Thursday May 30, 2024 @10:54PM (#40531044)
Using it as a poor man’s SQL was addressed, but using it that way doesn’t mean that’s what it is for.
[ Parent | on HN ]