<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GRPC on API Course</title>
    <link>https://apicourse.com/tags/grpc/</link>
    <description>Recent content in GRPC 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/grpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>REST vs GraphQL vs gRPC: Choosing the Right API Protocol</title>
      <link>https://apicourse.com/rest-vs-graphql-vs-grpc-choosing-the-right-api-protocol/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/rest-vs-graphql-vs-grpc-choosing-the-right-api-protocol/</guid>
      <description>&lt;p&gt;Every API starts with a choice that will shape every decision that follows: what protocol are you building on? REST, GraphQL, and gRPC are the three dominant options in modern API development, and none of them is universally correct. Each reflects a different set of assumptions about who is calling the API, how often, and what they need back.&lt;/p&gt;&#xA;&lt;p&gt;Understanding the tradeoffs is not optional knowledge for serious API developers. It is the foundation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
