<?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>polly on Alastair&#39;s Blog</title>
    <link>https://alastaircrabtree.com/tags/polly/</link>
    <description>Recent content in polly on Alastair&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 29 Dec 2016 09:27:59 +0000</lastBuildDate>
    <atom:link href="https://alastaircrabtree.com/tags/polly/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Implementing the retry pattern in c sharp using Polly</title>
      <link>https://alastaircrabtree.com/posts/implementing-the-retry-pattern-using-polly/</link>
      <pubDate>Thu, 29 Dec 2016 09:27:59 +0000</pubDate>
      <guid>https://alastaircrabtree.com/posts/implementing-the-retry-pattern-using-polly/</guid>
      <description>This post is the third and final installment on the retry pattern following on from implementing a simple retry pattern in c# and the retry pattern for async tasks.
In the last two posts we created a retry helper class to allow us to add retry logic to applications without cluttering important application logic with retry code. Now we will solve the same problem using a popular OSS library.
Polly is an open source framework for that &amp;ldquo;allows developers to express transient exception and fault handling policies such as Retry, Retry Forever, Wait and Retry, or Circuit Breaker in a fluent manner&amp;rdquo;.</description>
    </item>
    <item>
      <title>Implementing a simple retry pattern in c#</title>
      <link>https://alastaircrabtree.com/posts/implementing-a-simple-retry-pattern-in-c/</link>
      <pubDate>Thu, 01 Dec 2016 00:53:35 +0000</pubDate>
      <guid>https://alastaircrabtree.com/posts/implementing-a-simple-retry-pattern-in-c/</guid>
      <description>Everything is unstable. You cannot assume that every external service call will succeed on first attempt - the load balancer might be removing a failing host, the database might be being patched, the Ops person might have tripped on the network cable and quickly plugged it back in hoping the boss didn&amp;rsquo;t notice. If you make an outbound call you probably need an easy way to retry a couple of times before giving up and raising an exception.</description>
    </item>
  </channel>
</rss>
