Log in to GraphQL Editor
Why development teams are adopting GraphQL?

Tomek Poniatowicz


Why development teams are adopting GraphQL?

GraphQL is a query language for APIs that was originally built by Facebook, it describes how to ask & fetch the data from the server to the client, what's unique the response format is described in the query and defined by the client rather than the server.

By the end of 2018, the npm Inc. published its annual prediction about the insights and predictions about JavaScript for 2019, where they mentioned that:

There is a strong likelihood that developers will use GraphQL in new projects in 2019 and the GraphQL will become a technical force to reckon in 2019.

Guess what? They were right! More and more companies are adopting GraphQL with tremendous success!

Why Companies are Adopting GraphQL?

The survey made by one of the GraphQL adopting companies asked the CTOs and lead developers of a variety of companies about their experience with the implementation of GraphQL & its results. They made a great job gathering data from both top companies like Uber, Paypal, as well as those with smaller/medium development teams ranging from 1 to 100+ software engineers.

The result of the survey gives us insights on:

  • why they have chosen to implement GraphQL,
  • what obstacles they faced during the transition process,
  • what main benefits they were able to identify after the successful implementation.

Let's take a look at the questions the developers had to face.

Questions & answers

Well, technically these are not questions, but the survey asked responders to rank reasons why they decided to pivot in a scale from 1–6, where 1 is most important reason & 6 is least important. The makers of the survey identified six main benefits (Development Velocity, Modularity, Scalability, Performance, Reliability, Security), and asked how strongly they agree/disagree with the following statements:

We were able to speed up our development using GraphQL

We were able to scale our projects faster with GraphQL

It was easier to unify our APIs (e.g., Microservices, legacy endpoints, third-party services, etc.)

There has been an increase in performance using GraphQL

Our architecture is more stable, with decreased downtime, and fewer errors

Here are the results:

Chart presenting why companies adopted GraphQL

Chart presenting benefits of implementing GraphQL

Source: Movvum @medium

The interpretation of the survey's results was summed up closed in the table below. The most important thought is that GraphQL managed to provide what teams were looking for that small to medium as well as large enterprise teams.

Team sizeWhat they wanted to achieveWhat they've achived
50-100 & 100+ devsFaster development speed, better scalability, better modularityFaster development, better scalability
10-50 devsBetter modularity, higher performanceFaster development, better infrastructure
up to 10 devsFaster development, better modularityFaster development, better scalability

Bonus: Get inspired!

If somehow you haven't seen it make sure to check out the documentary about the GraphQL origins and how it became what it is now. A great production starring co-creators of GraphQL: Lee Byron, Dan Schafer, and Nick Schrock as well as other big names from the community.

GraphQL: The Documentary" explores the story of why and how GraphQL came to be and the impact it's having on big tech companies worldwide, including Facebook, Twitter, Airbnb & Github.


Check out our other blogposts

Inspiring talks from GraphQL Berlin Meetup
Tomek Poniatowicz
Tomek Poniatowicz
Inspiring talks from GraphQL Berlin Meetup
2 min read
over 4 years ago
GraphQL vs REST vs gRPC
Michał Tyszkiewicz
Michał Tyszkiewicz
GraphQL vs REST vs gRPC
4 min read
almost 4 years ago
GraphQL benefits and why you should adopt it in 2024
Tomek Poniatowicz
Tomek Poniatowicz
GraphQL benefits and why you should adopt it in 2024
7 min read
5 months ago

Ready for take-off?

Elevate your work with our editor that combines world-class visual graph, documentation and API console

Get Started with GraphQL Editor