<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mutations on API Course</title>
    <link>https://apicourse.com/tags/mutations/</link>
    <description>Recent content in Mutations on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/mutations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GraphQL Schema Design: Types, Queries, Mutations, and Best Practices</title>
      <link>https://apicourse.com/graphql-schema-design-types-queries-mutations-and-best-practices/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/graphql-schema-design-types-queries-mutations-and-best-practices/</guid>
      <description>&lt;p&gt;GraphQL shifts the design work from endpoint definition to schema design. The schema is the API — every type, field, query, and mutation is declared in the schema, and the schema governs everything the API can do. Designing a GraphQL schema well requires understanding how types compose, how to express mutations that reflect real domain operations, and where GraphQL&amp;rsquo;s conventions differ meaningfully from REST patterns that GraphQL developers often import by habit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
