<?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 BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/grpc/</link>
    <description>Recent content in Grpc on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 Nov 2024 09:13:40 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/grpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>gRPC fundamentals with Go</title>
      <link>https://www.bradcypert.com/grpc-fundamentals-with-go/</link>
      <pubDate>Sat, 13 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/grpc-fundamentals-with-go/</guid>
      <description>&lt;p&gt;gRPC (Remote Procedure Call) is a powerful tool for building robust and scalable communication between server applications.  It offers several advantages over traditional REST APIs, including type safety, performance optimizations, and a cleaner development experience.  In this blog post, we&#39;ll explore how to leverage gRPC with Go to establish communication between servers. We&#39;ll build a simple coffee shop example where a coffee shop client communicates with a server to manage orders.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
