Hacker News new | ask | show | jobs
by bhaney 806 days ago
It's impossible to give you advice on performance improvement without knowing why your performance sucks, and that's not a conversation that's reasonably going to happen here. I can't even tell from what you've posted if migrating to GraphQL degraded your perf and you're looking for a solution to get it back, or if GraphQL improved your perf but not as much as you wanted.

Ultimately if your app performance sucks and you need help, then hire people who can help.
1 comments
bruchim 806 days ago
We are using Apollo on top of our Postgres db, which is also used for other CRUD REST APIs.

I'm basically looking for more perspective of other teams, if they are feeling the same after migrating to graphQL (the same query in simple node + SQL ORM took half of the time), and if there is something that helped them solve these problems.

e.g. caching graphql is not as easy as caching GET API, something that I didn't know before.

link