<?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 egig.github.io</title><link>https://egig.github.io/blog/grpc/</link><description>Recent content in Grpc on egig.github.io</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 07 Feb 2020 10:00:00 +0000</lastBuildDate><atom:link href="https://egig.github.io/blog/grpc/index.xml" rel="self" type="application/rss+xml"/><item><title>Versioning gRPC Services Example in Go</title><link>https://egig.github.io/versioning-grpc-services-example-in-go/</link><pubDate>Fri, 07 Feb 2020 10:00:00 +0000</pubDate><guid>https://egig.github.io/versioning-grpc-services-example-in-go/</guid><description>&lt;p&gt;Sure we need the versioning for our microservices, its also apply for grpc services.&#10;I current working on service that used by another several service.&#10;My service periodically evolved and updated so I think its good practice to give it&#10;version, keep the code base tracked for update and deprecation.&lt;/p&gt;&#10;&lt;p&gt;In REST API we usually use path or &lt;code&gt;Accept&lt;/code&gt; header to identify versioning.&#10;For gRPC, I didn&amp;rsquo;t know I can apply versioning until I get in this page:&#10;&lt;a href="https://docs.microsoft.com/en-us/aspnet/core/grpc/versioning?view=aspnetcore-3.1%5D"&gt;Versioning gRPC services&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>