<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Big Data on Aaron West's technology blog</title><link>https://www.aaronwest.net/tags/big-data/</link><description>Recent content in Big Data on Aaron West's technology blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 13 Apr 2018 14:00:00 -0500</lastBuildDate><atom:link href="https://www.aaronwest.net/tags/big-data/index.xml" rel="self" type="application/rss+xml"/><item><title>What I'm Reading This Week - April 13, 2018</title><link>https://www.aaronwest.net/blog/what-im-reading-this-week-april-13-2018/</link><pubDate>Fri, 13 Apr 2018 14:00:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/what-im-reading-this-week-april-13-2018/</guid><description>&lt;p&gt;I spent a lot of time this week reading about how different engineering teams have scaled their Hadoop infrastructure. I also spent time looking at consistent hashing strategies, how GitHub manages DNS and routing, and how individual personalities affect team culture and performance. Read on for all the details.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://awe.st/2gW1R86"&gt;Transit and Peering: How your requests reach GitHub&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;One of GitHub&amp;rsquo;s infrastructure engineers talks about they use Geographic DNS routing and network &lt;a href="https://en.wikipedia.org/wiki/Peering"&gt;peering&lt;/a&gt; to impact how their traffic is shaped. Through their efforts they were able to direct 60-70% of GitHub traffic through optimal routes.&lt;/p&gt;</description></item></channel></rss>