<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design Patterns on Bryan Avery</title><link>https://bryanavery.co.uk/categories/design-patterns/</link><description>Recent content in Design Patterns on Bryan Avery</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>© 2026 Bryan Avery.</copyright><lastBuildDate>Tue, 06 May 2025 10:39:42 +0000</lastBuildDate><atom:link href="https://bryanavery.co.uk/categories/design-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Advanced Fault Tolerance in .NET 8 Using Microsoft’s Resilience Framework</title><link>https://bryanavery.co.uk/advanced-fault-tolerance-in-net-8-using-microsofts-resilience-framework/</link><pubDate>Tue, 06 May 2025 10:39:42 +0000</pubDate><guid>https://bryanavery.co.uk/advanced-fault-tolerance-in-net-8-using-microsofts-resilience-framework/</guid><description>&lt;p&gt;In my original &lt;a href="https://github.com/BryanAvery/PollyHttpClientFactory"&gt;Polly article&lt;/a&gt;, I introduced Polly as a robust resilience framework for handling transient faults and service failures. At the time, Polly was entirely community-driven and required manual configuration within each application. Fast forward five years, and Microsoft has officially embraced the concepts introduced by Polly, incorporating them directly into the .NET framework with a suite of first-party resilience libraries.&lt;/p&gt;</description></item><item><title>Fault tolerance using Polly</title><link>https://bryanavery.co.uk/fault-tolerance-using-polly/</link><pubDate>Mon, 09 Nov 2020 08:18:53 +0000</pubDate><guid>https://bryanavery.co.uk/fault-tolerance-using-polly/</guid><description>&lt;h2&gt;What is a Resilience Framework?&lt;/h2&gt;&#10;&lt;p&gt;Polly is classed as a resilience framework. A resilience framework is a set of libraries that help an application to recover from transient or more extended failures in services or infrastructure upon which it depends. When recovery is not possible, the resilience framework will facilitate graceful degradation of your application.&lt;/p&gt;</description></item><item><title>Claim-Check Pattern</title><link>https://bryanavery.co.uk/claim-check-pattern/</link><pubDate>Thu, 30 Jan 2020 15:59:25 +0000</pubDate><guid>https://bryanavery.co.uk/claim-check-pattern/</guid><description>&lt;p&gt;I’ve been using an Event Bus for some time now in the designs of a system, for reason of performance and scalability. There is also an issue with the message size. But it would be best if you were using the Event Bus as a messaging system, not a data transport mechanism.&lt;/p&gt;</description></item><item><title>Multi-Tenancy</title><link>https://bryanavery.co.uk/multi-tenancy/</link><pubDate>Wed, 20 Feb 2019 15:24:00 +0000</pubDate><guid>https://bryanavery.co.uk/multi-tenancy/</guid><description>&lt;h3 id="what-is-multi-tenancy-"&gt;What Is Multi-Tenancy?&lt;/h3&gt;&#10;&lt;p&gt;“&lt;em&gt;Software&lt;/em&gt; &lt;strong&gt;&lt;em&gt;Multitenancy&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;refers to a software&lt;/em&gt; &lt;strong&gt;&lt;em&gt;architecture&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;in which a&lt;/em&gt; &lt;strong&gt;&lt;em&gt;single instance&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;of a software runs on a server and serves &lt;strong&gt;&lt;em&gt;multiple tenants&lt;/em&gt;&lt;/strong&gt;. A tenant is a group of users who share common access with specific privileges to the software instance. With a multitenant architecture, a software application is designed to provide every tenant a &lt;strong&gt;&lt;em&gt;dedicated share of the instance including its data&lt;/em&gt;&lt;/strong&gt;, configuration, user management, tenant individual functionality and non-functional properties. Multitenancy contrasts with multi-instance architectures, where separate software instances operate on behalf of different tenants&lt;/em&gt;” (&lt;a href="https://en.wikipedia.org/wiki/Multitenancy"&gt;Wikipedia&lt;/a&gt;)&lt;/p&gt;</description></item><item><title>How to handle Events between Applications</title><link>https://bryanavery.co.uk/how-to-handle-events-between-applications/</link><pubDate>Fri, 24 Aug 2018 06:16:25 +0000</pubDate><guid>https://bryanavery.co.uk/how-to-handle-events-between-applications/</guid><description>&lt;h2&gt;The problem?&lt;/h2&gt;&#10;&lt;p&gt;How can application A, handle events sent by an application B, and how to implements those events in B? Knowing that B has no idea of the existence of A.&lt;br/&gt;&#10;&lt;span id="more-1014"&gt;&lt;/span&gt;&lt;/p&gt;&#10;&lt;h2&gt;The MemoryMapped way&lt;/h2&gt;&#10;&lt;p&gt;The following example shows how it would work, with the restriction that both applications are using the same memory space. In real code, the &lt;code&gt;producer()&lt;/code&gt; method would be in a different application from the &lt;code&gt;consumer()&lt;/code&gt; method, but this serves to illustrate an implementation:&lt;/p&gt;</description></item><item><title>Design Patterns</title><link>https://bryanavery.co.uk/design-patterns/</link><pubDate>Fri, 19 Jan 2018 07:55:42 +0000</pubDate><guid>https://bryanavery.co.uk/design-patterns/</guid><description>&lt;p&gt;Sometimes, a solution is so beautiful, and you wish you had the right problem to apply it to. But unfortunately, issues come first. As impressive as your new screwdriver may be (imagine a handle made of gold, with your initials engraved, of course, if the problem at hand is to knock in a nail, it makes for only a less than perfect solution.&lt;/p&gt;</description></item><item><title>Creating Good APIs</title><link>https://bryanavery.co.uk/creating-good-apis/</link><pubDate>Fri, 19 Jan 2018 07:52:44 +0000</pubDate><guid>https://bryanavery.co.uk/creating-good-apis/</guid><description>&lt;p&gt;I’m sure you’ve used a third-party API at some point in your dev career – for example, to create new contacts in your CRM, to send emails through a newsletter service, or to do anything else with a third-party service virtually.&lt;/p&gt;</description></item></channel></rss>