# From Monolith to Federation

DevFeed: [From Monolith to Federation](<https://devfeed.tech/articles/from-monolith-to-federation-23306.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/from-monolith-to-federation>)

Author: Daljit Summan

Published: 2023-08-09T11:33:08Z

Content type: tutorial

Language: en

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

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [API](<https://devfeed.tech/topics/api.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [back-end](<https://devfeed.tech/tags/back-end.md>), [backend](<https://devfeed.tech/tags/backend.md>), [data](<https://devfeed.tech/tags/data.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [incremental](<https://devfeed.tech/tags/incremental.md>)

## AI overview

This article discusses using GraphQL Federation and the Strangler fig pattern to incrementally migrate a monolith. It describes placing a facade in front of the monolith, splitting it by domain, decoupling clients through a Federation interface, and routing data through an API Gateway.

## Source excerpt

Introduction Many organizations own a Monolith (GraphQL or Non-GraphQL) and migrating away always seems an impossible task, most organizations fall into a seemingly endless amount of effort with very little progress to show for it. At Apollo we have seen many different patterns of migrating away from a monolith.