I spoke to the guys from Hasura at graphqlconf. So theoretically there is no downside, but Hasura has a lot of optimizations to make it super fast.
So unless your own server implementation is perfect the chance it becomes the bottleneck is a bit higher than when you do it the other way around.
Hasura is also launching remote relations, which should make adding in logic easier
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is there a big disadvantage to schema stitching Hasura into your (Apollo) server instead of the other way around?
Curious about that too.
I spoke to the guys from Hasura at graphqlconf. So theoretically there is no downside, but Hasura has a lot of optimizations to make it super fast.
So unless your own server implementation is perfect the chance it becomes the bottleneck is a bit higher than when you do it the other way around.
Hasura is also launching remote relations, which should make adding in logic easier