<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dotnet on Coffee-Driven Development</title>
    <link>https://duijzer.com/tags/dotnet/</link>
    <description>Recent content in Dotnet on Coffee-Driven Development</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© {currentYear}, Jacob Duijzer. All rights reserved</copyright>
    <lastBuildDate>Thu, 07 Nov 2019 18:00:00 +0200</lastBuildDate>
    <atom:link href="https://duijzer.com/tags/dotnet/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Arrowhead anti-pattern challenge</title>
      <link>https://duijzer.com/posts/arrowhead-antipattern-challenge/</link>
      <pubDate>Thu, 07 Nov 2019 18:00:00 +0200</pubDate>
      <guid>https://duijzer.com/posts/arrowhead-antipattern-challenge/</guid>
      <description>&lt;h5 id=&#34;update-2019-11-08-added-a-bonusbonus-anchor-contribution-from-bob-written-in-prolog&#34;&gt;update (2019-11-08): added a &lt;a href=&#34;https://duijzer.com/posts/arrowhead-antipattern-challenge/#bonus-anchor&#34;&gt;bonus&lt;/a&gt; contribution from Bob, written in prolog&lt;/h5&gt;&#xA;&lt;p&gt;Just recently I had to work on a huge flow-chart to determine farm types based on the animal transports to and from farm locations. I started out with a small proof of concept but didn&amp;rsquo;t like the way it turned out. I did some research and learned I was basically creating a so called arrow head (&lt;a href=&#34;http://wiki.c2.com/?ArrowAntiPattern&#34;&gt;&amp;ldquo;Arrowhead&amp;rdquo; anti-pattern &lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;While it was nothing new, I never knew it was called arrowhead anti-pattern (or arrow anti-pattern).&lt;/p&gt;</description>
    </item>
    <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>
