Facebook's GraphQL Gets Its Own Open-Source Foundation

TechCrunch is reporting that GraphQL, the Facebook-incubated data query language, is moving into its own open-source foundation. "Like so many other similar open-source foundations, the aptly named GraphQL Foundation will be hosted by the Linux Foundation." From the report: Facebook announced GraphQL back in 2012 and open sourced it in 2015. Today, it's being used by companies that range from Airbnb to Audi, GitHub, Netflix, Shopify, Twitter and The New York Times . At Facebook itself, the GraphQL API powers billions of API calls every day. At its core, GraphQL is basically a language for querying databases from client-side applications and a set of specifications for how the API on the backend should present this data to the client. It presents an alternative to REST-based APIs and promises to offer developers more flexibility and the ability to write faster and more secure applications. Virtually every major programming language now supports it through a variety of libraries.

"GraphQL has redefined how developers work with APIs and client-server interactions. We look forward to working with the GraphQL community to become an independent foundation, draft their governance and continue to foster the growth and adoption of GraphQL," said Chris Aniszczyk, vice president of Developer Relations at the Linux Foundation. As Aniszczyk noted, the new foundation will have an open governance model, similar to that of other Linux Foundation projects. The exact details are still a work in progress, though. The list of founding members is also still in flux, but for now, it includes Airbnb, Apollo, Coursera, Elementl, Facebook, GitHub, Hasura, Prisma, Shopify and Twitter.

Linux Foundation

[110010001000]

Those guys are still around?

Re:

[Hognoxious]

I think his host file app is supposed to fill them in.

Re:

[null etc.]

Alternative?

Poor man's SQL

[aberglas]

Plus the things that SQL should have added decades ago, like easy syntax for things like
Select invoice.customer.salesman.name from invoice...

Re:

[Chrisq]

Plus the things that SQL should have added decades ago, like easy syntax for things like Select invoice.customer.salesman.name from invoice...

I want to be more insane than you when I grow up but that's likely impossible at this point.

I can prove you wrong by proposing the API ESP version

select The record I want FROM the right table;

Re:

[Torvac]

lets just join all the tables ... still faster than one with everything

GraphQL Alternative

[null etc.]

Anyone who finds GraphQL to be a little, uhm, heavy for their needs might consider restQL [b2w.io], which is a middle ground between GraphQL and REST.

Re:

[jessicaroberts]

GraphQL shifts complexity to the server instead of the client. That can be an advantage when there's multiple clients or just one client iterating faster than the underlying logic. There's certainly a short term cost to GraphQL compared to REST, but there's a lot of use cases with positive ROI outside FANGs. run 3 [run2.online]