i don't know graphql

but the schema.graphql file is over 100 000 lines long and lags intellij

how bad is this?

Graph is a S-tier solution.

The "S" stands for shit.

It's literally how a FE developer thinks an API should work.

The insidious part of graph, as you have found out, happens after several years after you have supported it in your app stack.

I feel like if you've got an <anything> that's 100k lines, unless it's auto generated from a higher level language, it's probably wrong...

If it is generated from a higher level language, you're asking the wrong question.

GraphQL is crazy bad. If you only have one database (not counting redis and caches), GraphQL is the worst performance penalty you can introduce, on every level.

I see most people dog on GraphQL but I've used it in Shopify's ecosystem. And it performs better than REST.

Just my 2 cents.

@Sid2006 because that's what they provide. If you're doing things from scratch, and you have, say, postgres, and you compare its native joins perf vs graphql-level joins perf (that n + 1 ordeal), oh will somebody lose.