You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have considered graphql-mesh as gateway server for existing project which represents itself a distributed system, i.e. set of microservies which works and exposes rest api(which implements openapi spec) and graphql. The graphql-mesh looks like a silver bullet for us, but during the simple check I've observed the latency in avg for 300 ms for a server which exposes graphql api. Is it something which expected as overhead ? and what is the average latency should be expected in this case?
For test we took https://api.spacex.land/graphql/ and simply compared the response time for direct calls and over the graphql-mesh.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I have considered graphql-mesh as gateway server for existing project which represents itself a distributed system, i.e. set of microservies which works and exposes rest api(which implements openapi spec) and graphql. The graphql-mesh looks like a silver bullet for us, but during the simple check I've observed the latency in avg for 300 ms for a server which exposes graphql api. Is it something which expected as overhead ? and what is the average latency should be expected in this case?
For test we took https://api.spacex.land/graphql/ and simply compared the response time for direct calls and over the graphql-mesh.
example of config:
query for testing
Where is the original response time

and response time over the graphql-mesh

Beta Was this translation helpful? Give feedback.
All reactions