Hacker News Reader

Comment by Exuma | Hacker News Reader

Interesting at "apollo is not the way" can you expand more on that? im using vue with a new app im building. we proved our business idea with a 3rd party platform and im now building my own with 1 other person. I wanted to use graphql so I can make our nuxt3 app have leaner requests, and i wouldnt have to always bug the other guy to add endpoints. it was more of just an idea though, not something i have really seriously researched or considered

View on HN

The article I linked has much more information on the concept but essentially Apollo and most other GraphQL clients/servers don't do fragment stitching. Imagine laying out the data dependencies for each of your Vue components and having the frontend automatically refetch or cache invalidate whenever the data changes, with no input on your part. You would thus never over or underfetch your data, you get exactly the data you need at any part of your application. This is what Relay does.

Relay is for React only however since Facebook made all of these technologies. I recommend using React and NextJS if you can, I used to use Vue but found that the ecosystem for non-React frameworks was still worse than React, so I switched.

GraphQL Yoga can do schema stitching. Its a really good project thats been around awhile too[0][1]

[0]: https://the-guild.dev/graphql/yoga-server/docs

[1]: https://the-guild.dev/graphql/stitching/docs

Fragment stitching (also known as fragment colocation), not schema stitching. The Guild is starting to bring in some tools for fragment colocation, however: https://the-guild.dev/blog/unleash-the-power-of-fragments-wi...

Reply on news.ycombinator.com