Comment by roflyear
5 days ago
I do think that using graphql will solve a lot of problems for people but it's super surprising how many people absolutely hate it.
5 days ago
I do think that using graphql will solve a lot of problems for people but it's super surprising how many people absolutely hate it.
GraphQL is just a typed schema (good) with a server capable of serving any subset of the entire schema at a time (pain in the ass).
It doesn’t actually require that second part. Every time I’ve used it in a production system, we had an approved list of query shapes that were accepted. If the client wanted to use a new kind of query, it was performance tested and sometimes needed to be optimized before approval for use.
If you open it up for any possible query, then give that to uncontrolled clients, it’s a recipe for disaster.
Oh, we have that too! But we call it HTTP endpoints.
9 replies →
Without wishing to take part in a pile on - I am wondering why you're using graphql if you are kneecapping it and restricting it to set queries.
10 replies →
No.
It's a way to transmit a program from client to server. It then executes that program on the server side.
That sounds even worse!
2 replies →
I wish people at least stopped using JavaScript and stopped writing requests to back-end by hand.