https://graphql.org/_next/static/chunks/pages/blog/2016-09-14-production-ready-90e2e316e9d2b875.js

1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[1172],{33440:function(e,n,t){(window.__NEXT_P=window.__NEXT_P||[]).push(["/blog/2016-09-14-production-ready",function(){return t(22041)}])},22041:function(e,n,t){"use strict";t.r(n),t.d(n,{useTOC:function(){return s}});var r=t(52676),a=t(92937),o=t(45043),i=t(79428);function s(e){return[]}n.default=(0,a.c)(function(e){let n={a:"a",p:"p",...(0,i.a)(),...e.components};return(0,r.jsxs)(r.Fragment,{children:[(0,r.jsxs)(n.p,{children:["After over a year of being open sourced we’re bringing GraphQL out of “technical preview” and relaunching ",(0,r.jsx)(n.a,{href:"/",children:"graphql.org"}),"."]}),"\n",(0,r.jsx)(n.p,{children:"For us at Facebook, GraphQL isn’t a new technology. GraphQL has been delivering data to mobile News Feed since 2012. Since then it’s expanded to support the majority of the Facebook mobile product and evolved in the process."}),"\n",(0,r.jsxs)(n.p,{children:["Early last year when we first ",(0,r.jsx)(n.a,{href:"https://youtube.com/watch?v=9sc8Pyc51uU",children:"spoke publicly about GraphQL"})," we received overwhelming demand to share more about this technology. That sparked an internal project to revisit GraphQL, make improvements, draft a specification, produce a reference implementation you could use to try it out, and build new versions of some of our favorite tools, like ",(0,r.jsx)(n.a,{href:"https://github.com/graphql/graphiql",children:"GraphiQL"}),". We moved quickly, and released parts that were ready along the way."]}),"\n",(0,r.jsx)(n.p,{children:"Part of Facebook’s open source philosophy is that we want to only open source what is ready for production. While it’s true that we had been using GraphQL in production at Facebook for years, we knew that these newly released pieces had yet to be proven. We expected feedback. So we carefully released GraphQL as a “technical preview.”"}),"\n",(0,r.jsxs)(n.p,{children:["Exactly one year ago, we published graphql.org, with a ",(0,r.jsx)(n.a,{href:"/blog/graphql-a-query-language",children:"formal announcement"})," that GraphQL was open source and ready to be “technically previewed”. Since then, we’ve seen GraphQL implemented ",(0,r.jsx)(n.a,{href:"/code",children:"in many languages"}),", and successfully adopted by other companies. That includes today’s exciting announcement of the ",(0,r.jsx)(n.a,{href:"http://githubengineering.com/the-github-graphql-api",children:"GitHub GraphQL API"}),", the first major public API to use GraphQL."]}),"\n",(0,r.jsx)(n.p,{children:"In recognition of the fact that GraphQL is now being used in production by many companies, we’re excited to remove the “technical preview” moniker. GraphQL is production ready."}),"\n",(0,r.jsxs)(n.p,{children:["We’ve also revamped this website, ",(0,r.jsx)(n.a,{href:"/",children:"graphql.org"}),", with clearer and more relevant content in response to some the most common questions we’ve received over the last year."]}),"\n",(0,r.jsx)(n.p,{children:"We think GraphQL can greatly simplify data needs for both client product developers and server-side engineers, regardless of what languages you’re using in either environment, and we’re excited to continue to improve GraphQL, support the already growing community, and see what we can build together."})]})},"/blog/2016-09-14-production-ready",{filePath:"src/pages/blog/2016-09-14-production-ready.mdx",timestamp:1789481543e3,pageMap:o.v,frontMatter:{title:"Leaving technical preview",tags:["blog"],date:"2016-09-14",byline:"Lee Byron"},title:"Leaving technical preview"},"undefined"==typeof RemoteContent?s:RemoteContent.useTOC)}},function(e){e.O(0,[3556,5043,2888,9774,179],function(){return e(e.s=33440)}),_N_E=e.O()}]);