On July 5th, the Spring GraphQL project was officially removed from experimental and is now a Spring top-level project. And I hear from sources that the first milestone release is coming soon.
The project was developed by the GraphQL Java team in collaboration with the Spring team.
GraphQL Java has been maturing for 6 years now. GraphQL Java has always been just an engine that performs GraphQL requests, focusing only on HTTP and IO facets. Now people need a real HTTP GraphQL adapter. Over the past 12 months there has been extensive collaboration and discussion between the GraphQL Java and Spring teams to achieve this goal.
This project is a huge step forward for GraphQL Java and the broader GraphQL ecosystem: The Spring integration maintained and developed by Spring engineers has been a key factor in GraphQL’s success.
Spring GraphQL is the successor to GraphQL Java Spring. The goal is to make Spring GraphQL the foundation for all GraphQL applications, which are built on GraphQL Java.
Our overall philosophy for GraphQL Java and Spring GraphQL is to be unbiased and focused on comprehensive and broad support. We wanted the combination of Spring and GraphQL Java to be built on top of Spring GraphQL, rather than messing around and developing smug features.
The GraphQL Java team and the Spring team will give the Spring GraphQL keynote at the Spring One conference in September.
About GraphQL
GraphQL is a Query Language that is particularly advantageous for querying Graph data. In other words, it is an API syntax that describes how clients request data from servers, similar to the RESTful specification.
It was open-source by Facebook in 2015. It is designed to represent data in a graph-like fashion, where it is not partitioned by API endpoints as in RESTful, but rather organized together by associations and hierarchies. For more information, go to the GraphQL website.