There, I said it.
I've used GraphQL exactly once, and I had inherited it. Someone else's architectural confession left in the codebase like a note that just said "sorry."
Never again.
"But Jake, you must have had a bad experience with it, or not enough, if any experience with it,"
I've also never performed my own appendectomy... some knowledge is best acquired through observation and a healthy respect for scar tissue.
GraphQL is a backend team's white flag dressed up as architecture that you adopted because you couldn't version an API.
Yah sure, it's so exciting and awesome that the frontend clients have to write and maintain their queries and heaven forbid something changes.
Oh, the security model is a screen door on a submarine.
Development speed is crushed.
REST gives you URLs. URLs are cacheable by infrastructure that already exists. GraphQL said "what if we POST everything to one endpoint" like that wasn't the exact mistake we spent twenty years learning not to make.
FACEBOOK CREATED IT, AND, WELL, NODES ARE COOL SO IT MUST BE GREAT!
🥱
Prove me wrong. But since you have to justify it to me, this means you're already losing.
GraphQL sucks.
❤️
Jake