DEV Community

Discussion on: Introduction to GraphQL

Collapse
 
n1ru4l profile image
Laurin Quast

Regarding the Memory Leak: Have you tried building a minimal reproduction repository and filed in a bug report? I am sure that the apollo team and other contributors would appreciate that.

I also agree that modeling good GraphQL APIs is an art form, however basic things like only mutations should create/change stuff can be vague. What if you want to increase a counter each time an user visits a site that fires a certain query? We can either increase the counter as part of the query execution or as a separate mutation aka an additional request.

Furthermore, in my 3 years of working with react-apollo, I have not experienced the not update the data or pass malformed information into the component errors yet. As with the SSR issue it could be valuable if you can submit a minimal reproduction repository to the apollo team!

While there might be some issues with apollo-client, we should also keep in mind they started making GraphQL easily usable. When they started the only react client with a comparable feature set was relay classic. Today we have a wider variety and I encourage you to try Relay Modern or URQL. I personally really like the features of Relay Modern. However, for now I will stick with apollo.

Collapse
 
hugoliconv profile image
Hugo

How difficult is it to start with GraphQL? We are about to start a redesign of a project that is currently in laravel and Vue to GraphQL and React + Apollo, the main problem is that nobody from the team has experience working with GraphQL and I was wondering how much that can affect