[uberman]

From our experience graphql made semi technical users more productive from a query perspective but at a cost of literally everything else. Data loading, security, schema building, responders, performance, n+1, and on and on.

We would never do it again if we could.

[bruchim]

Specifically about performance, have you tried to solve it with any caching mechanism or any other out-of-the-box optimization?

[uberman]

We tried a number to cache solutions including those baked into AWS dynamodb but nothing worked correctly for us. We were never able to get resolver specific cache with the correct parameter granularity working correctly.