# Federated Schema Design

DevFeed: [Federated Schema Design](<https://devfeed.tech/articles/federated-schema-design-23299.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/federated-schema-design>)

Author: Michael Watson

Published: 2022-04-20T09:23:00Z

Content type: tutorial

Language: en

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

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [apollo-federation](<https://devfeed.tech/tags/apollo-federation.md>), [backend](<https://devfeed.tech/tags/backend.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [mobile-apps](<https://devfeed.tech/tags/mobile-apps.md>), [schema-design](<https://devfeed.tech/tags/schema-design.md>)

## AI overview

This tutorial explains how to design extensible and maintainable federated GraphQL schemas. It presents the supergraph as a platform that can reuse capabilities across products and services, and contrasts federated schema design with a monolithic approach.

## Source excerpt

Introduction If you've been building with GraphQL, you likely know how essential good schema design is. As the entry-point to all your GraphQL operations, it's desirable to design a schema that's easy to understand and work with, serves the needs of our clients today, and can be changed to fit their needs tomorrow. This article teaches about the supergraph, platform thinking, and why it's key to designing your graph for extensibility.