Skip to main content

A Brief History of GraphQL

Learn a bit of history, and how we got where we are now

A Brief History

TL;DR Timeline

  • Pre-2012 - REST dominates
  • 2012 - Facebook identifies scaling issues
  • 2012–2015 - GraphQL developed internally
  • 2015 - GraphQL open-sourced
  • 2016+ - Ecosystem and enterprise adoption

2012: The Problem Emerges at Facebook​

The official birthday of GraphQL was the 29th of February 2012, when it was an internal proposal at Facebook with the name SuperGraph.

At that time Facebook was transitioning heavily toward mobile-first development, but when they tried to migrate the original web-app to native iOS, they encountered multiple problems, described by co-creator Lee Byron in this 10-minute video Brief History of GraphQL

Challenges they faced:

  • Mobile apps needed very specific data for each screen
  • Network performance was inconsistent
  • REST endpoints returned too much or too little data
  • Rapid product iteration required flexible APIs

Facebook engineers realized they needed:

A way for clients to ask for exactly the data they needed - and nothing more.

2012–2015: GraphQL Is Created Internally​

Between 2012 and 2015, Facebook engineers designed and refined a new API paradigm internally.

Key design goals:

  • Client-driven data fetching
  • Strong typing
  • A single endpoint
  • Predictable responses
  • Backward-compatible evolution

This internal system became GraphQL.

2015: GraphQL Is Open-Sourced​

In July 2015, Facebook publicly released GraphQL as an open-source project.

Two artifacts were published together:

This dual approach of having a clear spec together with a reference implementation led to implementations across every major programming language and ecosystem, including Java, Ruby, PHP, .NET, Python, Go...

The official web page of GraphQL is https://graphql.org. Note that the domain ending in .com (https://graphql.com) is an unrelated page owned by a company.

2016–2017: Tooling and Early Adoption​

Following open-sourcing, the ecosystem grew rapidly:

  • Apollo Client and Server
  • Relay (Facebook's client)
  • Server implementations in many languages

Large companies started adopting GraphQL at scale:

GraphQL proved valuable for complex UIs and microservice architectures.

2018: GraphQL Foundation​

After the open source release in 2015, GraphQL was owned and run by Facebook. In November 2018 creation of the GraphQL Foundation was announced. The GraphQL Foundation is a vendor-neutral entity, comprising over 25 members. The list includes AWS, Airbnb, Atlassian, Microsoft, IBM, and Shopify.

The official description of the foundation is:

to ensure that the GraphQL community is able to focus on the continued evolution of the specification and reference implementations.

2020–Present: Maturity​

GraphQL is now considered a mainstream API technology, so much that for example Netflix announced they are dropping REST completely in favor of GraphQL in this 2025 Java One video

Modern focus areas include:

  • Performance optimization
  • Schema governance
  • Federation
  • Observability
  • Security