# Modularizing your GraphQL schema code

DevFeed: [Modularizing your GraphQL schema code](<https://devfeed.tech/articles/modularizing-your-graphql-schema-code-23458.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/modularizing-your-graphql-schema-code>)

Author: Dhaivat Pandya

Published: 2018-04-12T19:58:00Z

Content type: tutorial

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Code](<https://devfeed.tech/topics/code.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [files](<https://devfeed.tech/tags/files.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [resolvers](<https://devfeed.tech/tags/resolvers.md>), [schema](<https://devfeed.tech/tags/schema.md>), [sdl](<https://devfeed.tech/tags/sdl.md>), [types](<https://devfeed.tech/tags/types.md>)

## AI overview

This tutorial explains how to modularize a growing GraphQL schema by splitting schema type definitions and resolvers into multiple files. It uses simple JavaScript concepts to import and combine the definitions and resolver objects.

## Source excerpt

As your GraphQL application grows from demo, to proof of concept, to production, the complexity of your schema and resolvers will grow in tandem. To organize your code, you'll want to split up your schema types and the associated resolvers into multiple files. We get this question frequently since there are a lot of different approaches to splitting up your schema code, and it might seem that you need a complex setup to get a good result.