The GraphQL Modules approach lets you separate your backend implementation into small, reusable, easy-to-implement and easy-to-test pieces.
In GraphQL Modules, each module has its own GraphQL type definitions and resolver implementations.
unions declared in GraphQL Modules are also extensible: modules can re-declare types and extend them as they wish.
The idea behind this is to implement the Separation of Concerns design pattern in GraphQL and to allow you to write simple modules that only do what they need to. This way, they're easier to write, maintain and test.
module is built using the basics of GraphQL:
- Type definitions
As your application grows, modules can have:
- External configurations
- Dependencies on other modules
- Providers (we will elaborate on this in the Dependency Injection section)
To get a better understanding of the structure and extensibility of modules, let's make an example app with four modules:
- User (define what a user in our app should have)
- Authentication (define only what is needed to authenticate users)
- Profile (define a user's profile)
- Gallery (define a user's photo gallery)
Let's understand how to define each module's schema and how to separate it into smaller pieces.
This module allows querying users by id and defines only the very basic fields.
This module declares the authentication basics in
The profile module declares the
Profile type and adds the
profile field to
The gallery module is similar to the
profile module. It declares only the parts of the schema that are required by the gallery feature: