Yikes

Yep! City is a little wild already 😵‍💫

classic 😛

Sounds similar to “learned helplessness”

💯 yes

🤣

😅💦

Yeah, at least it’s super cacheable so not generally a huge issue (although the miss can be nasty in JS)

Yeah I think that’s part of the true overhead 👍

Most commonly this leads to data-loading issues. Note that a sufficiently complex codebase will lead to very similar problems no matter the API style. GraphQL does put them in front of you sooner in the process.

"resolvers" are almost always at the source of issues. Compared with endpoint-based APIs, in GraphQL, most fields operate with very local information and have a smaller "horizon" for optimization.

GraphQL is slow, they usually fail to identify what is slow, and are rarely describing GraphQL's true overhead. Now, I do think GraphQL doesn't do a great job at creating a "pit of success" as far as performance goes. A naively implemented GraphQL API is most likely going to have serious perf issues

Eventually showed up :)

It was wild! Fun to bump into each other on slack 😅

Ah its at build time 😄