> Markdown version of [/videos/9-graphql-mesh-why-graphql-between-services-is-the-worst-idea-and-the-best-idea-at-the-same-time](https://www.wearedevelopers.com/videos/9-graphql-mesh-why-graphql-between-services-is-the-worst-idea-and-the-best-idea-at-the-same-time). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# GraphQL Mesh – Why GraphQL between services is the worst idea and the best idea at the same time!

Why rewrite legacy APIs just to support GraphQL? Learn how GraphQL Mesh automatically generates a fully typed, unified graph from your existing native protocols in minutes.

- **Speakers:** Uri Goldshtein
- **Event:** WeAreDevelopers LIVE
- **Published:** June 17, 2020
- **Duration:** 34:28
- **URL:** https://www.wearedevelopers.com/videos/9-graphql-mesh-why-graphql-between-services-is-the-worst-idea-and-the-best-idea-at-the-same-time

## Summary

The introduction of GraphQL often accelerates frontend workflows, but backend services frequently become the bottleneck when generic gateways lose end-to-end typing across legacy APIs. Forcing cross-functional backend teams to abandon functional protocols and migrate to a completely new GraphQL system is often unrealistic and highly inefficient.

GraphQL Mesh presents a practical alternative by enabling developers to query any backend data source using GraphQL without modifying the underlying services. By consuming existing machine-readable definitions—such as openapi, GRPC, SQL, and odata—the mesh automatically generates a fully typed GraphQL schema. This automation dramatically accelerates development; converting massive integrations like the Microsoft Graph API from odata to GraphQL drops from months of manual failure to precise, automated generation in minutes. It ultimately preserves the optimized native protocols executed by backend microservices while delivering the predictable query experience required by the client side.

The tool's actual leverage surfaces through advanced schema stitching and apollo federation, which empower developers to seamlessly merge discrete, explicitly unassociated APIs into a single, unified graph. Recognizing differing infrastructure requirements, the execution environment scales adaptively, functioning as either a centralized gateway or as distributed, localized SDKs to mitigate single points of failure. Moving forward, this highly pluggable design sets the foundation for a global, interconnected data graph akin to the semantic web, where open-source modules can be published, linked, and collectively queried on demand.

**Keywords:** graphql mesh, schema stitching, apollo federation, openapi API conversion, GRPC integration, odata API transformation, remote API orchestration, frontend-backend bottleneck, distributed SDK gateways, backend service typings, semantic web data graph, typed API generation, legacy protocol abstraction, microservice query orchestration, endpoint merging, SQL source handlers

## Chapters

1. **Open-source ecosystem tools for gradual GraphQL adoption** (00:17) — How community-maintained utilities streamline API development without requiring complete platform commitments.
1. **Structuring declarative data requests with query schemas** (04:25) — Using resolvers and exact request structures to reduce network overhead for consumer applications.
1. **Automatic data orchestration and compile-time type safety** (07:54) — How backend execution engines parallelize remote calls and utilize code generation for strict typings.
1. **Exposing static typing blind spots in legacy workflows** (10:43) — Why traditional architectures fail to guarantee type safety across decoupled internal microservices.
1. **Generating legacy compliance architectures from modern graphs** (13:06) — Using the SOFA library to automatically compile standardized REST definitions for unmigrated backend consumers.
1. **Merging legacy backend protocols into consolidated graphs** (18:16) — Utilizing GraphQL Mesh to convert gRPC and Swagger integrations into a central schema automatically.
1. **Implementing dynamic endpoint merging across isolated sources** (20:08) — Connecting independent external weather and city endpoints efficiently using schema stitching interfaces.
1. **Converting complex enterprise protocols with automated handlers** (24:37) — Translating heavy data layers like Microsoft Graph and OData directly into modern configurations.
1. **Deploying merged endpoints through distributed execution engines** (26:40) — Reusing Apollo Federation logic to wrap legacy tools within modular containerized SDK environments.
1. **Creating open-source data modules for semantic integration** (30:54) — Sharing publicly maintained protocol handlers to build a unified and globally accessible web ecosystem.

## Related Moments

- [Introduction to the GraphQL, Apollo, and Next.js stack](https://www.wearedevelopers.com/videos/311-graphql-apollo-next-js-a-lovely-trio) (from "GraphQL + Apollo + Next.js: A Lovely Trio")
- [Approaches to building a GraphQL API layer](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) (from "Putting the Graph In GraphQL With The Neo4j GraphQL Library")
- [Comparing GraphQL capabilities against the JSON API standard](https://www.wearedevelopers.com/videos/33-api-design-getting-started) (from "API Design - Getting Started")
- [Creating API endpoints with GraphQL schemas and backend resolvers](https://www.wearedevelopers.com/videos/311-graphql-apollo-next-js-a-lovely-trio) (from "GraphQL + Apollo + Next.js: A Lovely Trio")
- [Generating frontend APIs with GraphQL and OpenAPI](https://www.wearedevelopers.com/videos/1580-end-to-end-typescript-completing-the-modern-development-stack) (from "End-to-End TypeScript: Completing the Modern Development Stack")
- [Comparing Neo4j and GraphQL conceptual models](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) (from "Putting the Graph In GraphQL With The Neo4j GraphQL Library")

## Related Articles

- [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering)
- [Everything a Developer Needs to Know About MCP with Neo4j](https://www.wearedevelopers.com/magazine/604-everything-a-developer-needs-to-know-about-mcp-with-neo4j)
- [Why You Shouldn’t Build a Microservice Architecture](https://www.wearedevelopers.com/magazine/118-why-you-shouldn-t-build-a-microservice-architecture)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)

## Related Jobs

- [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group**
- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**
- [Staff Software Engineer](https://www.wearedevelopers.com/jobs/ext/1425755-staff-software-engineer) at **GitHub**
- [AI Software Engineer (Germany)](https://www.wearedevelopers.com/jobs/48317-ai-software-engineer-germany) at **Sunhat**
- [Junior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/1532351-junior-frontend-engineer) at **Almedia**
- [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub**