Closed SachaG closed 1 year ago
Cool idea! I'd love to get an understanding for what schema builder libraries (SDL-first vs various code-first approaches like TypeGraphQL, Pothos, Nexus, ...) as well as HTTP server libraries (Apollo Server, Express, Mercurius, ...) are popular.
Also interested to learn what DBs and ORMs people are typically using to implement their GraphQL servers.
Here's a few more to get you started:
what does the response size of GraphQL requests look like? Are there many cases of multi-megabyte GraphQL responses? Gigabyte responses? 95% of GraphQL payloads are under [how many bytes]?
Interesting, but I don't know if there's an easy way to find out things like that through a survey. Just FYI, generally it's always best if we can stick to questions that fit the multiple-choice format.
it seems that static operations have long become the best practice; is there still a significant portion of people constructing queries dynamically?
I don't know anybody who would do such a thing…
Hi @SachaG,
That's a great idea! 🚀
Here are the ideas/questions gathered with all The Guild members:
If you use GraphQL, which questions would you hope the survey would answer?
@live
@defer
@stream
@deprecated
Which areas should it cover?
Which features/architecture patterns/libraries/services should be included?
What other questions can we ask to get a better picture of the GraphQL community?
What are the main current GraphQL pain points we should ask about?
What are the main currently missing features we should ask about?
How do you stay up to date with GraphQL?
@charlypoly oh wow thanks, that's an awesome list!
Awesome list indeed! My own questions mostly revolves around the point of view of an app developper:
Hey all!
This is a great initiative and we already have an amazing list.
I'm listing down some more ideas based on conversations with the Hasura team.
Additional inputs from @gavinray97
I'm really excited to see this come to fruition to the level that State of JS
has delivered amazing data on the Javascript ecosystem!
I've done some good progress on the outline and hope to be able to share a preview version of the survey soon! I did have a couple questions for you all:
Hello! thanks for asking these questions! I'm the PM of Apollo Client so here is my personal take on these 😄
Should we make a difference between Apollo Client React/iOS/Kotlin or group them all under "Apollo Client"?
A: 💯 Yes. It be great to break these out as they serve different use cases and we actually have 3 different client teams working on these.
Should we ask about things like Next.js which will often consume GraphQL but are not related to GraphQL directly? If so under which category? I
A: Yes, At Apollo we are super curious on the use of these React frameworks and their growing popularity as it relates to GraphQL. I'd think you could group them under a category like Web Development Frameworks w/ GraphQL
Where would something like Gatsby fit in, since it both produces and consumes its own GraphQL API? What about Redwood?
A: See the answer above.
Should we ask about databases?
A: Yes! It be super interesting to know what databases are being used behind GraphQL across the industry.
Additional question I have that would be amazing to add into this survey are:
Some that I keep my eye on:
iOS
Android
OK, I have a preliminary outline ready! Thanks all for your patience: https://github.com/StateOfJS/Monorepo/issues/90
I'm exploring the idea of doing a "State of GraphQL" survey, so I'm opening this thread to gather feedback.
Let me know here!