<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Software-Architecture on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/software-architecture/</link>
		<description>Recent content in Software-Architecture on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Fri, 14 Aug 2026 20:57:00 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/software-architecture/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Process vs Thread: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/process-vs-thread-explained/</link>
				<pubDate>Fri, 14 Aug 2026 20:57:00 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/process-vs-thread-explained/</guid>
				<description>&lt;p&gt;A web server becomes slow, so someone suggests adding more threads. Another person proposes splitting the work into separate processes. Both ideas sound like ways to “run more things at once,” yet they change the system in very different ways.&lt;/p&gt;&#xA;&lt;p&gt;The difference is not simply that processes are heavy and threads are light. That shortcut hides the decision that matters most:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;A process gives running code its own resource boundary. A thread gives code another path of execution inside an existing boundary.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>What Is Software Architecture? A Beginner&#39;s Guide</title>
				<link>https://www.compilemymind.com/posts/software-architecture-beginners-guide/</link>
				<pubDate>Thu, 13 Aug 2026 20:00:00 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/software-architecture-beginners-guide/</guid>
				<description>&lt;p&gt;The first time many developers hear &lt;em&gt;software architecture&lt;/em&gt;, they imagine an enormous diagram: dozens of boxes, arrows in every direction, and perhaps a cloud in the corner for good measure.&lt;/p&gt;&#xA;&lt;p&gt;That picture is not completely wrong. It is just where architecture becomes visible, not where it begins.&lt;/p&gt;&#xA;&lt;p&gt;Architecture begins much earlier, with decisions such as these:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Should the ordering code be allowed to update inventory data directly?&lt;/li&gt;&#xA;&lt;li&gt;What happens to checkout when the payment provider is unavailable?&lt;/li&gt;&#xA;&lt;li&gt;Can one part of the application be changed without redeploying everything?&lt;/li&gt;&#xA;&lt;li&gt;Which problems are important today, and which ones are still imaginary?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;These decisions create the shape of a system. At first, that shape can feel invisible. Later, when the product grows, it determines whether a change takes an afternoon or an entire quarter.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
