Five years of GraphQL 🎉

2020 will mark five years since GraphQL was released!

To celebrate, we asked some of the usual suspects 😎 in the community, including Lee Byron, co-creator of GraphQL, to reflect on their journey, and where GraphQL is headed next.

Takeaways

  • GraphQL is more than just a tool: it changes how teams communicate. It empowers developers to request for the data they want, reducing their dependency and communication overhead with API teams. It thrives on community and collaboration.
  • GraphiQL rocks: it’s the feature people would miss the most if it went away.
  • 🕷🕸The most popular mascot choice for GraphQL is spiders. Honorable mention: “Humans... Humans are also nice animals.” - Uri Goldshtein
  • We got a variety of answers for what to change about GraphQL:
    • an approach to GraphQL that works well with microservices; less coupled to a monolithic design,
    • a more opinionated stance on authorization, especially with the introspection schema,
    • make it easy for beginners to get started,
    • the ability to handle errors in the query.
    • See video for more!
  • Among the hardest parts of using GraphQL are the need for a heavy client-side library, initial adoption, and building a good GraphQL server that leverages modern serverless and cloud native trends.
  • The most popular way to convince someone to migrate to GraphQL is to show them GraphiQL and get them started on the frontend. Don’t forget to tell them it’s sunny all the time, they can wear flip-flops, and the food is great!

What about you? How would you convince someone today to migrate to GraphQL? And how would you answer the other questions? Please share in the comments! And if you’d like to tweet us a video of your answers, we won’t stop you 😈


The Questions

  1. What have you learned in the last five years of GraphQL that you’d use in the next five years?

2. Describe GraphQL in five words.

3. What feature of GraphQL would you really miss if it were to go away?

4. Which animal or plant would be your GraphQL mascot?

5. What would you want to change about GraphQL?

6. How did you and GraphQL meet?

7. What stack did you migrate to GraphQL from?

8. What do you think is the hardest part of using GraphQL?

9. What is the biggest challenge you faced when adopting GraphQL?

10. How would you convince someone today to migrate to GraphQL?

🎥 Starring (in order of appearance)

  • Alex Banks & Eve Porcello, Moon Highway
  • Jon Wong, Coursera
  • Uri Goldshtein, The Guild
  • Ivan Goncharov, APIs.guru
  • Sasha Solomon, Twitter
  • Lee Byron, Co-creator of GraphQL
  • Shruti Kapoor, Paypal
  • Tanmai Gopal, Hasura
  • Manish Jain, Dgraph Labs

Hasura is an open-source engine that gives you realtime GraphQL APIs on new or existing Postgres databases, with built-in support for stitching custom GraphQL APIs and triggering webhooks on database changes.


PS: We’re hiring!


This post was a collaboration between

Shraddha, Sezgi Ulucam

  • Shraddha

    Works at Hasura.

    More posts by Shraddha.

  • Sezgi Ulucam

    Sezgi Ulucam

    Developer Advocate 🥑 @ Hasura | Front-End Dev | Baker | Dancer | Massage Therapist | WFR

    More posts by Sezgi Ulucam.

    Sezgi Ulucam