<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Matt Duncan</title>
    <description/>
    <link>https://speakerdeck.com/mrduncan</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/mrduncan.rss"/>
    <lastBuildDate>2013-09-05 10:00:17 -0400</lastBuildDate>
    <item>
      <title>Zero Downtime Deploys with Rails</title>
      <description>http://mattduncan.org/talks/zero-downtime-deploys/

Every deploy introduces the risk of downtime because of changes which are not backwards compatible. At Yammer, we deploy our Rails codebase to hundreds of servers many times a week. In this talk, I’ll discuss many of the strategies we use to mitigate downtime during deploys. This includes how we handle database changes as well as background workers and external services.</description>
      <media:content url="https://files.speakerdeck.com/presentations/604ea8f0f860013020bd4288c23f2aed/preview_slide_0.jpg?1932681" type="image/jpeg" medium="image"/>
      <content:encoded>http://mattduncan.org/talks/zero-downtime-deploys/

Every deploy introduces the risk of downtime because of changes which are not backwards compatible. At Yammer, we deploy our Rails codebase to hundreds of servers many times a week. In this talk, I’ll discuss many of the strategies we use to mitigate downtime during deploys. This includes how we handle database changes as well as background workers and external services.</content:encoded>
      <pubDate>Thu, 01 Nov 2012 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/mrduncan/zero-downtime-deploys-with-rails</link>
      <guid>https://speakerdeck.com/mrduncan/zero-downtime-deploys-with-rails</guid>
    </item>
  </channel>
</rss>
