<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>retries and backoff &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/retries-and-backoff/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Wed, 02 Aug 2023 13:12:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>Let’s Architect! Resiliency in architectures</title>
		<link>https://noise.getoto.net/2023/08/02/lets-architect-resiliency-in-architectures/</link>
		
		<dc:creator><![CDATA[Luca Mezzalira]]></dc:creator>
		<pubDate>Wed, 02 Aug 2023 13:12:51 +0000</pubDate>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[AWS Well-Architected]]></category>
		<category><![CDATA[AWS Well-Architected Framework]]></category>
		<category><![CDATA[jitter]]></category>
		<category><![CDATA[Let's Architect]]></category>
		<category><![CDATA[resilience]]></category>
		<category><![CDATA[Resilience Hub]]></category>
		<category><![CDATA[retries and backoff]]></category>
		<category><![CDATA[Thought Leadership]]></category>
		<category><![CDATA[timeouts]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=f2ac1146a239847b1a72ad3bf9edb319</guid>

					<description><![CDATA[What is “resiliency”, and why does it matter? When we discussed this topic in an early 2022 edition of Let’s Architect!, we referenced the AWS Well-Architected Framework, which defines resilience as having “the capability to recover when stressed by load, accidental or intentional attacks, and failure of any part in the workload’s components.” Businesses rely […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 26/67 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-07 02:50:20 by W3 Total Cache
-->