<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Retry on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/retry/</link>
    <description>Recent content in Retry on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Nov 2021 11:41:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/retry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Reliable Pipelines with Go: Retry, Circuit Breaker, and Backoff</title>
      <link>https://blog.turboawesome.win/2021/11/building-reliable-pipelines-with-go-retry-circuit-breaker-and-backoff/</link>
      <pubDate>Wed, 17 Nov 2021 11:41:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/11/building-reliable-pipelines-with-go-retry-circuit-breaker-and-backoff/</guid>
      <description>Every service that calls another service will eventually face failures. The patterns that contain those failures — retry with backoff, circuit breakers, bulkheads — are not optional for production Go services. Here&amp;#39;s how to implement them correctly.</description>
    </item>
  </channel>
</rss>
