<?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>Disposability &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/disposability/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Tue, 29 Sep 2020 15:39:25 +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>Why Deployment Requirements are Important When Making Architectural Choices</title>
		<link>https://noise.getoto.net/2020/09/29/why-deployment-requirements-are-important-when-making-architectural-choices/</link>
		
		<dc:creator><![CDATA[Yusuf Mayet]]></dc:creator>
		<pubDate>Tue, 29 Sep 2020 15:39:25 +0000</pubDate>
				<category><![CDATA[Amazon CloudWatch]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon QuickSight]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[architecture best practices]]></category>
		<category><![CDATA[AWS CodeBuild]]></category>
		<category><![CDATA[AWS CodeDeploy]]></category>
		<category><![CDATA[AWS CodePipeline]]></category>
		<category><![CDATA[deployability]]></category>
		<category><![CDATA[Disposability]]></category>
		<category><![CDATA[observability]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=916b1c5b70af08affb60f921b7d65220</guid>

					<description><![CDATA[Introduction Too often, architects fall into the trap of thinking the architecture of an application is restricted to just the runtime part of the architecture. By doing this we focus on only a single customer (such as the application&#8217;s users and how they interact with the system) and we forget about other important customers like [&#8230;]]]></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 30/63 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-11 14:34:38 by W3 Total Cache
-->