<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/infrastructure/</link>
    <description>Recent content in Infrastructure on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 16 Oct 2016 15:51:46 -0700</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Golang is great for network services</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2016/why-golang-great-for-network-services/</link>
      <pubDate>Sun, 16 Oct 2016 15:51:46 -0700</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2016/why-golang-great-for-network-services/</guid>
      <description>I&amp;rsquo;ve been using Go professionally for over a year now. While I&amp;rsquo;m not a fan of every decision made by the language, I will admit that Go gets a lot of things right for one segment of the industry - network daemons and similar systems software. Google&amp;rsquo;s ethos are engineering solid and reliable services at scale; various design decisions make Go well suited for this.&#xA;Go favors composition at multiple levels.</description>
    </item>
  </channel>
</rss>
