The monolith vs. microservices debate is a false choice. Learn how to design a coherent API surface while distributing implementation across teams with GraphQL Federation.

Wundergraph is a blog or publication focused on GraphQL, a query language and runtime for APIs. Through tutorials, guides, and case studies, Wundergraph explores various aspects of GraphQL development, including schema design, query optimization, and integration with frontend frameworks. Developers can learn how to leverage GraphQL to build efficient and flexible APIs that meet the needs of modern web and mobile applications.

WunderGraph

The monolith vs. microservices debate is framed as a false dichotomy. The real insight is that API design and API implementation are separate concerns that should be handled differently: design top-down as a unified whole (monolith thinking), implement distributed across teams (microservices thinking). Traditional GraphQL Federation merges these concerns, letting each team design and implement their slice, which leads to API fragmentation. WunderGraph's Fission and Hub tools aim to separate these layers — a design phase where the supergraph is treated as a single coherent schema, and an implementation phase where teams independently build their assigned subgraphs. Three trends driving this approach: organizations scaling past coordination thresholds, AI agents needing coherent APIs, and platform engineering demanding golden paths.

Design Like a Monolith, Implement as Microservices

Why Separate API Design From Implementation?

How Do You Design Like a Monolith and Implement as Microservices?

Is Monolith vs. Microservices a False Choice?