<?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>architecture Archives - Petamind</title>
	<atom:link href="https://petaminds.com/tag/architecture/feed/" rel="self" type="application/rss+xml" />
	<link>https://petaminds.com/tag/architecture/</link>
	<description>A.I, Data and Software Engineering</description>
	<lastBuildDate>Wed, 05 Jun 2024 22:27:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://petaminds.com/wp-content/uploads/2019/09/ic_launcher.png</url>
	<title>architecture Archives - Petamind</title>
	<link>https://petaminds.com/tag/architecture/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>MVVM vs MVI &#8211; Architecture for Mobile Development</title>
		<link>https://petaminds.com/mvvm-vs-mvi-architecture-for-mobile-development/</link>
					<comments>https://petaminds.com/mvvm-vs-mvi-architecture-for-mobile-development/#respond</comments>
		
		<dc:creator><![CDATA[Tung Nguyen]]></dc:creator>
		<pubDate>Fri, 05 Apr 2024 22:22:00 +0000</pubDate>
				<category><![CDATA[front-end]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[Kotlin]]></category>
		<category><![CDATA[MVI]]></category>
		<category><![CDATA[MVVM]]></category>
		<guid isPermaLink="false">https://petaminds.com/?p=5191</guid>

					<description><![CDATA[<p>The Model-View-ViewModel (MVVM) and Model-View-Intent (MVI) are architectural patterns used in software development, particularly for structuring the code of user interface (UI) applications. Both patterns aim to separate concerns and manage the flow of data between the UI and the underlying data models, but they do so in different ways. Let&#8217;s explore both patterns with [&#8230;]</p>
<p>The post <a href="https://petaminds.com/mvvm-vs-mvi-architecture-for-mobile-development/">MVVM vs MVI &#8211; Architecture for Mobile Development</a> appeared first on <a href="https://petaminds.com">Petamind</a>.</p>
]]></description>
		
					<wfw:commentRss>https://petaminds.com/mvvm-vs-mvi-architecture-for-mobile-development/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PETAMIND IS NOW LIVING ON AWS</title>
		<link>https://petaminds.com/petamind-is-now-living-on-aws/</link>
					<comments>https://petaminds.com/petamind-is-now-living-on-aws/#respond</comments>
		
		<dc:creator><![CDATA[Tung Nguyen]]></dc:creator>
		<pubDate>Sat, 02 Oct 2021 19:12:28 +0000</pubDate>
				<category><![CDATA[back-end]]></category>
		<category><![CDATA[front-end]]></category>
		<category><![CDATA[full-stack]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[mirgration]]></category>
		<guid isPermaLink="false">http://13.238.174.212/?p=3170</guid>

					<description><![CDATA[<p>After 3 years residing on Google Cloud, we decided to move to AWS. GC is generally OK, however, there is some issue related to the architecture of the previous one that may hinder the future scalability! As such, we decided to re-architecture the site and its workload for the future. There may be some issues [&#8230;]</p>
<p>The post <a href="https://petaminds.com/petamind-is-now-living-on-aws/">PETAMIND IS NOW LIVING ON AWS</a> appeared first on <a href="https://petaminds.com">Petamind</a>.</p>
]]></description>
		
					<wfw:commentRss>https://petaminds.com/petamind-is-now-living-on-aws/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
