A Spring Boot starter for GraphQL servers with built-in support for GraphiQL, Altair, Playground, and Voyager.
GraphQL Spring Boot Starters is a library that provides auto-configuration for building GraphQL servers in Spring Boot applications. It automatically sets up a GraphQL servlet endpoint and integrates multiple GraphQL IDEs (GraphiQL, Altair, Playground, Voyager) with minimal configuration. The project simplifies GraphQL API development by handling schema creation, subscriptions, tracing, and metrics out-of-the-box.
Java developers building GraphQL APIs with Spring Boot who want a production-ready setup with embedded GraphQL IDEs and support for popular GraphQL Java libraries.
It eliminates manual GraphQL server configuration by providing a comprehensive, opinionated starter that integrates seamlessly with Spring Boot's auto-configuration and supports multiple GraphQL tooling options in a single dependency.
GraphQL and GraphiQL Spring Framework Boot Starters - Forked from oembedler/graphql-spring-boot due to inactivity.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates multiple IDEs (GraphiQL, Altair, Playground, Voyager) with customizable settings and CDN options, eliminating separate setup for testing and exploration.
Automatically exposes a GraphQL servlet at `/graphql` with configurable CORS, async support, and exception handling, reducing boilerplate code for production-ready endpoints.
Supports both GraphQL Java Tools for schema-first development and GraphQL Annotations for code-first approaches, offering choice in schema definition strategies.
Provides out-of-the-box support for extended scalars like BigDecimal, Date, and UUID, and allows aliasing for custom type names via configuration.
Enables Apollo-style tracing and Micrometer metrics for queries and subscriptions, facilitating performance monitoring without manual instrumentation.
The project is no longer updated or supported, with maintainers recommending migration to Spring for GraphQL, posing security and compatibility risks.
Dependency injection does not work properly with GraphQL Annotations resolvers, requiring cumbersome workarounds as admitted in the README.
Specific Kotlin version requirements (e.g., 1.3.70) and NoClassDefFoundErrors with GraphQL Java Tools add complexity and potential breaking changes.
With no active maintenance, features like Spring Boot 3 compatibility or newer GraphQL specifications are unavailable, forcing teams to fork for updates.