<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hot-Chocolate on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hot-chocolate/</link>
    <description>Recent content in Hot-Chocolate on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hot-chocolate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted GraphQL Server Libraries: Apollo Server vs Yoga vs Mercurius vs Strawberry</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-graphql-server-libraries-apollo-yoga-mercurius-strawberry-hotchocolate/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-graphql-server-libraries-apollo-yoga-mercurius-strawberry-hotchocolate/</guid>
      <description>&lt;p&gt;When building a GraphQL API, you need a server library that handles query parsing, validation, execution, and response formatting. While platforms like Hasura and PostGraphile auto-generate GraphQL APIs from existing databases, server libraries give you full control over your schema design, resolver logic, and middleware composition. Choosing the right one for your language ecosystem can dramatically impact development velocity and production performance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
