GraphQL
GraphQL is a query language and execution specification for APIs that lets clients request and manipulate data through a schema.
Building Web APIs with ASP.NET Core
GraphQL is a data query and manipulation language for APIs that lets clients specify the data fields they require.
- How it is used
- Uses GraphQL to retrieve client-selected API data through one endpoint as an alternative to REST’s fixed responses and multiple round trips.
- How deep it goes
- Explains field selection, runtime processing, and caching, performance, and complexity trade-offs without detailing the runtime’s internals.
- Examples
- Uses a board-game query that filters names, sorts and limits results, and selects game and related-entity fields.
- What you can do after
- Apply it via BananaCakePop to test a GraphQL query for precisely selected board-game data.
Read how Building Web APIs with ASP.NET Core explains GraphQL →
Digital Twins in Action
GraphQL is a query language and runtime for APIs that lets clients specify the fields and shape of the response they require.
- How it is used
- Uses GraphQL to expose and integrate related digital twin data for clients, dashboards, and agents.
- How deep it goes
- Explains query shape and schemas, then implements an API that orchestrates external services and connects a dashboard.
- Examples
- Queries second-floor temperatures and builds a city weather forecast API backed by geocoding and Open-Meteo.
- What you can do after
- Builds a GraphQL API using Python, Graphene, and Flask to coordinate external data sources.
Fast by Default
GraphQL is a query language and execution system for APIs that lets clients request structured data through a typed schema.
- How it is used
- Reduces API round trips and response waste when clients need related data with varying field requirements.
- How deep it goes
- Explains client-shaped queries, REST contrasts, payload effects, and trade-offs, but does not detail schema or execution internals.
- Examples
- Uses GitHub pull-request data, a user profile with posts, and PayPal checkout latency to illustrate request costs.
- What you can do after
- Evaluate GraphQL against REST and gRPC for client diversity, round trips, payloads, caching, and operational fit.
Grokking Software Architecture
GraphQL is an API query language and execution system that lets clients request structured data through a typed schema.
- How it is used
- Exposes a public API contract when clients need flexible, targeted data retrieval.
- How deep it goes
- Explains targeted queries, round trips, tradeoffs, and mutation retry safety, but not server implementation.
- Examples
- Shows a shopper requesting a chip’s name and soda’s price, plus a warehouse scanner retrieving product, stock, and location data.
- What you can do after
- Evaluate GraphQL against REST by weighing round trips, client flexibility, caching, implementation complexity, and retry safety.
Quarkus in Action
GraphQL is a query language and runtime for APIs that lets clients request precisely the data they need.
- How it is used
- Reduces overfetching, underfetching, requests, and network traffic when clients need precise API responses.
- How deep it goes
- Defines schemas and demonstrates a code-first Quarkus service, while deferring persistent storage and broader production concerns.
- Examples
- Uses a Quarkus car inventory with Java models, an in-memory database stub, a cars query, and register and remove mutations.
- What you can do after
- Build a code-first GraphQL API in Quarkus using SmallRye GraphQL annotations and Java-backed data.
Contract Testing in Action
GraphQL is a query language and runtime for APIs that lets clients request structured data through a typed schema.
- How it is used
- Supports flexible API consumption and contract testing between consumers and a GraphQL layer.
- How deep it goes
- Explains response shaping, SDL, resolvers, and Apollo integration, but defers broader frontend and backend integration details.
- Examples
- Uses a movie landing page, Movie SDL type, movie resolver, Apollo application, and single-query versus multi-request comparison.
- What you can do after
- Apply GraphQL through Apollo tools and evaluate consumer data needs, invalid queries, output changes, and response status behavior.
The Art of Code
A query language and runtime for APIs that lets clients specify the fields they need.
- How it is used
- Reduces API bandwidth by letting clients request only the fields required by each page.
- How deep it goes
- Explains selective field retrieval as a design technique but stops short of query syntax or runtime implementation.
- Examples
- Uses a customer profile payload and contrasts full search data with report fields such as name and order count.
- What you can do after
- Apply GraphQL to request narrower API responses and reduce unnecessary data transfer.
Django in Action
GraphQL is a query language and API runtime in which clients specify the data and operations they want through a schema-defined query.
- How it is used
- Provides a schema-driven alternative to REST for flexible client queries through one API endpoint.
- How deep it goes
- Explains the endpoint, schemas, ORM mapping, and query classes, but stops short of detailed implementation or query syntax.
- Examples
- Uses Graphene schemas, query classes, GraphQLView registration, and selectively requested object fields as concrete artifacts.
- What you can do after
- Evaluate GraphQL architecture and identify how a Django API exposes schemas, operations, and client-selected responses.
Also covered in
- Pro ASP.NET Core 7, Tenth Edition
- API Design Patterns
- GitHub Actions in Action: Continuous integration and delivery for DevOps
- Build Financial Software with Generative AI (From Scratch)
What to know first
- RESTREST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
- JSONJSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- HTTPHTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
- protobufProtocol Buffers is a language- and platform-neutral system for defining structured data schemas and serializing messages in a compact binary format, with support for generated code.
Related concepts
- RESTalternative to · REST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
- JSONuses · JSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- rest apicontrasts with · A REST API is an application programming interface that exposes resources through representations and provides interactions according to the constraints of the REST architectural style.
- HTTPuses · HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
- api callalternative to · An API call is a programmatic request or invocation sent through an application programming interface to retrieve data or invoke an exposed operation.
Questions about GraphQL
What is GraphQL?
GraphQL is a query language and execution specification for APIs that lets clients request and manipulate data through a schema.
Which Manning books explain GraphQL?
Building Web APIs with ASP.NET Core, Digital Twins in Action, Fast by Default, Grokking Software Architecture, Quarkus in Action, Contract Testing in Action, The Art of Code and Django in Action.
What should I know before learning GraphQL?
Manning books that teach GraphQL usually introduce REST, JSON, HTTP and protobuf first.
What is the difference between GraphQL and REST?
GraphQL is a query language and execution specification for APIs that lets clients request and manipulate data through a schema. REST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.







