GraphQL APIs with Spring Boot · 课时

使用类型扩展实现模式模块化

通过将大型 GraphQL 模式拆分为多个 SDL 文件，并在 Spring Boot 中使用 extend 关键字扩展共享根类型，让模式更易于维护。

使用类型扩展实现模式模块化 是 CoddyKit 上的免费 GraphQL APIs with Spring Boot 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 GraphQL APIs with Spring Boot 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 GraphQL APIs with Spring Boot 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

The Monolithic Schema Problem

As an API grows, a single schema.graphqls file becomes thousands of lines, hard to navigate and prone to merge conflicts.

Modularization splits the schema by feature so each team owns a focused slice.

Modularization vs Stitching

This is different from schema stitching. Stitching merges schemas from separate services. Modularization splits one service's schema into many files that load into the same runtime.

Multiple SDL Files in Spring

Spring for GraphQL automatically loads every .graphqls file under src/main/resources/graphql/ and merges them into one schema.

graphql/
  book.graphqls
  author.graphqls
  review.graphqls

The Single Root Problem

GraphQL allows only one Query type. If two files both declare type Query, the schema fails to build with a duplicate-type error.

Extending the Root Type

Declare type Query once, then use extend type Query in other files to add fields. The pieces merge into one root.

# book.graphqls
type Query { books: [Book!]! }

# author.graphqls
extend type Query { authors: [Author!]! }

Extending Object Types

extend works on any object type, not just roots. A reviews module can add a field to Book without editing the book file.

# review.graphqls
extend type Book {
  reviews: [Review!]!
}

Resolvers Stay Modular Too

Each module gets its own controller. The extended field on Book is resolved by a @SchemaMapping in the review module's controller.

@Controller
public class ReviewController {
    @SchemaMapping(typeName = "Book")
    public List<Review> reviews(Book book) {
        return reviewService.forBook(book.getId());
    }
}

Sharing Common Types

Cross-cutting types like PageInfo or shared enums live in a common.graphqls file. Every module references them without redefining.

# common.graphqls
type PageInfo {
  hasNextPage: Boolean!
  endCursor: String
}

Organizing by Feature

Group SDL files and controllers by feature, not by GraphQL kind. Keep book.graphqls next to BookController mentally, so a feature change touches one cohesive area.

Validation at Startup

Spring assembles and validates the merged schema at startup. If an extend references a type that does not exist, the application fails fast with a clear error, catching mistakes early.

Best Practices

Keep modular schemas healthy:

Declare each root type once, extend elsewhere
One SDL file and controller per feature
Centralize shared types in a common file
Let startup validation guard your merges

Quick Check

Test your schema modularization knowledge.

Recap

You modularized a large schema:

Split SDL into multiple feature files Spring auto-merges
Declare root types once, add fields with extend
Extend any object type from another module
Centralize shared types and keep resolvers modular

Modular schemas scale cleanly across teams and features.

常见问题解答

「使用类型扩展实现模式模块化」课时是免费的吗？

是的 — 「使用类型扩展实现模式模块化」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 GraphQL APIs with Spring Boot 课程的其余内容，请升级到 CoddyKit PRO。 GraphQL APIs with Spring Boot 课程共包含 4 节课。

「使用类型扩展实现模式模块化」这节课中我会学到什么？

通过将大型 GraphQL 模式拆分为多个 SDL 文件，并在 Spring Boot 中使用 extend 关键字扩展共享根类型，让模式更易于维护。你通过在浏览器中直接运行的动手代码来练习 GraphQL APIs with Spring Boot，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 GraphQL APIs with Spring Boot 需要有经验吗？

无需任何先前经验。CoddyKit 上的 GraphQL APIs with Spring Boot 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「使用类型扩展实现模式模块化」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 GraphQL APIs with Spring Boot 课中编写并运行代码吗？

能。每节 GraphQL APIs with Spring Boot 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 GraphQL APIs with Spring Boot