liveBook · Manning

GraphQL mutation

A GraphQL mutation is an operation that requests a change to server-side data or state and may return selected fields resulting from that change.

How 3 Manning books explain it

Quarkus in Action

A GraphQL mutation is a GraphQL operation that can add or modify data and may return data with the update.

How it is used
Uses mutations to add or modify data while returning selected fields from the resulting object.
How deep it goes
Defines operation semantics and demonstrates input, field selection, response echoing, and database verification without covering advanced GraphQL features.
Examples
Demonstrates a register mutation that creates a fleet car, echoes selected fields, and verifies persistence with a cars query.
What you can do after
Apply it via GraphiQL by supplying mutation arguments, selecting response fields, executing the operation, and checking the resulting data.

Read how Quarkus in Action explains GraphQL mutation →

Building Web APIs with ASP.NET Core

A GraphQL mutation is an operation that requests a state-changing action from a GraphQL server and can return selected resulting fields.

How it is used
Uses a state-changing operation to update a board game's name through a GraphQL API.
How deep it goes
Walks through token setup, mutation execution, and database verification, but does not detail server-side mutation implementation.
Examples
Demonstrates renaming Die Macher and assigning a revised name to Axis & Allies.
What you can do after
Operate/configure BananaCakePop to authorize and execute a mutation, then verify the saved change with a query.

Read how Building Web APIs with ASP.NET Core explains GraphQL mutation →

Grokking Software Architecture

A GraphQL operation that requests a change to server-side data or state.

How it is used
Changes server-side data and requires explicit retry protection when a repeated request could cause duplicate effects.
How deep it goes
Explains the duplicate-payment risk and a key-based retry process, without detailing implementation internals.
Examples
Uses a payment mutation for 50.00 and describes how a retry could charge the customer twice.
What you can do after
Apply an idempotency key to a mutation so retries can return the original success instead of repeating the payment.

Read how Grokking Software Architecture explains GraphQL mutation →

Also covered in

Related concepts

Questions about GraphQL mutation

What is GraphQL mutation?

A GraphQL mutation is an operation that requests a change to server-side data or state and may return selected fields resulting from that change.

Which Manning books explain GraphQL mutation?

Quarkus in Action, Building Web APIs with ASP.NET Core and Grokking Software Architecture.

What is the difference between GraphQL mutation and SQL?

A GraphQL mutation is an operation that requests a change to server-side data or state and may return selected fields resulting from that change. SQL is a standardized declarative language for defining, querying, and manipulating data in relational database systems.

What is GraphQL mutation a kind of?

GraphQL mutation is a kind of GraphQL operation. A GraphQL operation is an executable request that specifies a query, mutation, or other interaction with a GraphQL schema.

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.