<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Retry on Coffee-Driven Development</title>
    <link>https://duijzer.com/tags/retry/</link>
    <description>Recent content in Retry on Coffee-Driven Development</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© {currentYear}, Jacob Duijzer. All rights reserved</copyright>
    <lastBuildDate>Thu, 18 Apr 2019 20:10:00 +0200</lastBuildDate>
    <atom:link href="https://duijzer.com/tags/retry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Retry and fallback policies in C# with Polly</title>
      <link>https://duijzer.com/posts/polly-refit/</link>
      <pubDate>Thu, 18 Apr 2019 20:10:00 +0200</pubDate>
      <guid>https://duijzer.com/posts/polly-refit/</guid>
      <description>&lt;p&gt;In this blog I will try to explain how one can create clean and effective policies to retry API calls and have fallbacks when requests are failing. With &lt;a href=&#34;https://github.com/App-vNext/Polly&#34;&gt;Polly&lt;/a&gt; it is possible to create complex and advanced scenarios for error handling with just a few lines of code.&lt;/p&gt;&#xA;&lt;p&gt;This week I was connecting an eCommerce web application to an ERP system with REST APIs. There are multiple endpoints, all authenticated with OAuth. To make sure all calls to the APIs will have a high success rate I had to implement retry mechanisms for different scenarios.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
