One of the first events of 2022 wrapped up in a spectacular way. The State of GraphQL included many wonderful people and presented a number of interesting topics and questions.
Before we get into the key take-aways, I would highly suggest you watch the live stream for a more in-depth and highly entertaining experience.
Let's get started with introducing our hosts and panelists for The State Of GraphQL.
👉 Dustin Goodman - @dustinsgoodman
👉 Eve Porcello - @eveporcello
👉 Roy Derks - @gethackteam - Hackteam - StepZen
👉 Janessa Garrrow - @janessagarrow - Apollo
👉 Milecia McGregor - @flippedcoding - Iterative
👉 Jamie Barton - @notrab - Graphql Screencasts - Graph CMS: The GraphQL Headless CMS
The State of GraphQL live-stream consisted of numerous questions, and discussions presented by our panelists and viewers on Youtube.
There are a lot of advantages when using GraphQL. Having one endpoint to dynamically and effectively gather different types of information is useful. However, one of the biggest obstacles for people switching from REST to GraphQL is the relatively complexity of setting up and using GraphQL. There are more and more tools coming to market that aim at easing that burden.
Some of the questions that were asked were:
- If you could add one thing to the #graphql spec, what would it be?
- With so many GraphQL tools and options out there, how do you choose which to use? Based on comfort? Requirements? Project scope?
- Are there any community events that you’re excited about?
- Is GraphQL a viable communication protocol for IoT devices?
- Right now the hardest thing about implementing GraphQL is the scheming (coming from REST). Is there anything that has been a blocker for you in implementing GraphQL?
- Where do you lie on the REST vs GraphQL scale?
- What are you most excited about in the GraphQL space right now?