
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Dan Does Code</title>
      <link>https://www.dandoescode.com/blog</link>
      <description>A blog about .NET and Software Architecture</description>
      <language>en-us</language>
      <managingEditor>me@dandoescode.com (Daniel Mackay)</managingEditor>
      <webMaster>me@dandoescode.com (Daniel Mackay)</webMaster>
      <lastBuildDate>Sat, 03 Oct 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.dandoescode.com/tags/graphql/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.dandoescode.com/blog/vertical-slice-architecture-with-graphql</guid>
    <title>Vertical Slice Architecture with GraphQL</title>
    <link>https://www.dandoescode.com/blog/vertical-slice-architecture-with-graphql</link>
    <description>What happens when you swap the REST API of a real Vertical Slice Architecture template for GraphQL, and try not to touch the domain? I ported the SSW VSA template to HotChocolate 16 to find out. Here&#39;s what GraphQL is, the problems it solves compared to REST, and what it actually looks like in .NET - slices, DataLoaders, typed errors, and a live subscription.</description>
    <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
    <author>me@dandoescode.com (Daniel Mackay)</author>
    <category>dotnet</category><category>graphql</category><category>hotchocolate</category><category>vertical-slice-architecture</category><category>domain-driven-design</category><category>csharp</category>
  </item>

    </channel>
  </rss>
