Create a project using Spring Initializr and add Spring for GraphQL dependencies; 2. Define GraphQL schema in the schema.graphqls file; 3. Create Book record class as data model; 4. Implement query parser with @Controller and @QueryMapping; 5. Start the application and test queries through http://localhost:8080/graphql; 6. Enable GraphiQL in the configuration file to use an interactive UI; 7. Optionally add Mutation in the schema and implement the change method with @MutationMapping; finally build a type-safe, production-ready GraphQL API through schema-first. The whole process integrates naturally and smoothly with Spring Boot, and runs without additional configuration.
Building a GraphQL API with Java and Spring is straightforward thanks to Spring for GraphQL , a module introduced by the Spring team to simplify integrating GraphQL into Spring Boot applications. It provides first-class support for building GraphQL servers using familiar Spring patterns—like annotations, dependency injection, and testing utilities.

Here's how to set up a working GraphQL API in Java with Spring Boot.
? 1. Set Up the Project with Required Dependencies
Start by creating a Spring Boot project using Spring Initializr and include:

- Spring Web (for embedded server)
- Spring for GraphQL (the core module)
- Spring Boot DevTools (optional, for hot reload)
- Lombok (optional, reduces boilerplate)
Or manually add the dependency in pom.xml
(for Maven):
<dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-graphql</artifactId> </dependency>
For Gradle:

implementation 'org.springframework.boot:spring-boot-starter-graphql'
Spring Boot 3 includes automatic configuration for GraphQL, so no extra setup is needed to get started.
? 2. Define Your Schema ( .graphqls
file)
Create a file named schema.graphqls
under src/main/resources/graphql
:
type Query { bookById(id: ID!): Book allBooks: [Book!]! } type Book { id: ID! title: String! author: String! pages: Int chapterCount: Int }
This defines:
- Two queries:
bookById
andallBooks
- A
Book
type with several fields
? Note: Spring for GraphQL automatically detects
.graphqls
files on the classpath.
? 3. Create Data Models
Map the GraphQL types to Java classes:
// Book.java public record Book(String id, String title, String author, Integer pages, Integer chapterCount) {}
Using record
(Java 16 ) keeps it clean. Otherwise, use a standard class with getters.
? 4. Implement a Data Fetcher with @Controller
Use a Spring @Controller
to implement resolvers:
import org.springframework.graphql.data.method.annotation.QueryMapping; import org.springframework.stereotype.Controller; import java.util.List; import java.util.concurrent.atomic.AtomicInteger; @Controller public class BookController { private static final List<Book> BOOKS = List.of( new Book("1", "The Great Gatsby", "F. Scott Fitzgerald", 180, 9), new Book("2", "1984", "George Orwell", 328, 25), new Book("3", "Dune", "Frank Herbert", 688, 75) ); private final AtomicInteger counter = new AtomicInteger(100); @QueryMapping public Book bookById(String id) { return BOOKS.stream() .filter(book -> book.id().equals(id)) .findFirst() .orElse(null); } @QueryMapping public List<Book> allBooks() { return BOOKS; } }
?
@QueryMapping
maps methods to GraphQL query fields. Parameter names must match schema input fields.
? 5. Test the API
Start the app with mvn spring-boot:run
or via your IDE.
Go to: http://ipnx.cn/link/1d22a89ef605339c5e6580b577a57ad5 (if using GraphiQL)
Or send a POST request to http://localhost:8080/graphql
:
{ "query": "{ allBooks { id title author pages } }" }
Sample response:
{ "data": { "allBooks": [ { "id": "1", "title": "The Great Gatsby", "author": "F. Scott Fitzgerald", "pages": 180 }, ... ] } }
You can also query a single book:
{ bookById(id: "2") { title author } }
? 6. Enable GraphiQL (Interactive UI)
Add this to application.properties
:
spring.graphql.graphhiql.enabled=true
Or in application.yml
:
spring: graphql: graphiql: enabled: true
Now you can explore and test your schema interactively.
? 7. Add Mutations (Optional)
Extend schema in schema.graphqls
:
type Mutation { createBook(title: String!, author: String!, pages: Int): Book! } extend type Query { bookById(id: ID!): Book }
Add a mutation method:
@MutationMapping public Book createBook(String title, String author, Integer pages) { String id = String.valueOf(counter.incrementAndGet()); Book newBook = new Book(id, title, author, pages, null); // In real apps: save to DB return newBook; }
Now you can run:
mutation { createBook(title: "New Book", author: "Me") { id title } }
Final Notes
- No need for controllers with
@RequestMapping
– Spring for GraphQL uses annotated methods directly. - Supports annotations like
@SchemaMapping
for more complex nested resolvers. - Integrates with Spring Security , Data Fetching (DataLoader) , and Reactive Streams .
- Schema-first approach encourages clear contract design.
Building a GraphQL API with Java and Spring is now as natural as REST—just define your schema, write annotated methods, and let Spring handle the wiring. It's clean, type-safe, and production-ready.
Basically, if you know Spring and a bit of GraphQL, you're already halfway there.
The above is the detailed content of Building a GraphQL API with Java and Spring for GraphQL. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Enums in Java are special classes that represent fixed number of constant values. 1. Use the enum keyword definition; 2. Each enum value is a public static final instance of the enum type; 3. It can include fields, constructors and methods to add behavior to each constant; 4. It can be used in switch statements, supports direct comparison, and provides built-in methods such as name(), ordinal(), values() and valueOf(); 5. Enumeration can improve the type safety, readability and flexibility of the code, and is suitable for limited collection scenarios such as status codes, colors or week.

Interface Isolation Principle (ISP) requires that clients not rely on unused interfaces. The core is to replace large and complete interfaces with multiple small and refined interfaces. Violations of this principle include: an unimplemented exception was thrown when the class implements an interface, a large number of invalid methods are implemented, and irrelevant functions are forcibly classified into the same interface. Application methods include: dividing interfaces according to common methods, using split interfaces according to clients, and using combinations instead of multi-interface implementations if necessary. For example, split the Machine interfaces containing printing, scanning, and fax methods into Printer, Scanner, and FaxMachine. Rules can be relaxed appropriately when using all methods on small projects or all clients.

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity

There are three main differences between Callable and Runnable in Java. First, the callable method can return the result, suitable for tasks that need to return values, such as Callable; while the run() method of Runnable has no return value, suitable for tasks that do not need to return, such as logging. Second, Callable allows to throw checked exceptions to facilitate error transmission; while Runnable must handle exceptions internally. Third, Runnable can be directly passed to Thread or ExecutorService, while Callable can only be submitted to ExecutorService and returns the Future object to

In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.

JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.

Javaprovidesmultiplesynchronizationtoolsforthreadsafety.1.synchronizedblocksensuremutualexclusionbylockingmethodsorspecificcodesections.2.ReentrantLockoffersadvancedcontrol,includingtryLockandfairnesspolicies.3.Conditionvariablesallowthreadstowaitfor

Java's class loading mechanism is implemented through ClassLoader, and its core workflow is divided into three stages: loading, linking and initialization. During the loading phase, ClassLoader dynamically reads the bytecode of the class and creates Class objects; links include verifying the correctness of the class, allocating memory to static variables, and parsing symbol references; initialization performs static code blocks and static variable assignments. Class loading adopts the parent delegation model, and prioritizes the parent class loader to find classes, and try Bootstrap, Extension, and ApplicationClassLoader in turn to ensure that the core class library is safe and avoids duplicate loading. Developers can customize ClassLoader, such as URLClassL
