<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Performance  on Matt Aimonetti</title>
		<link>https://matt.aimonetti.net/categories/performance-/</link>
		<description>Recent content in Performance  on Matt Aimonetti</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 23 Jun 2013 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://matt.aimonetti.net/categories/performance-/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>using go vs ruby for web apis</title>
				<link>https://matt.aimonetti.net/posts/2013-06-using-go-vs-ruby-for-web-apis/</link>
				<pubDate>Sun, 23 Jun 2013 00:00:00 +0000</pubDate>
				<guid>https://matt.aimonetti.net/posts/2013-06-using-go-vs-ruby-for-web-apis/</guid>
				<description>&lt;p&gt;A few days ago, I was wondering if using &lt;a href=&#34;https://golang.org/&#34;&gt;Go&lt;/a&gt; would be worth it when developing new web APIs.&#xA;I obviously knew that Go would be faster than Ruby, but I wasn&amp;rsquo;t sure&#xA;how much faster. I also wondering about the amount of work required to&#xA;write get a full API implemented.&lt;/p&gt;&#xA;&lt;p&gt;I therefore wrote the same web API in Ruby (using Rails) and in Go (at&#xA;first using Revel and then rewriting it without a framework since Go&amp;rsquo;s&#xA;std lib have everything one might need).&#xA;The API spec was simple:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
