<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Distributed-Systems on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/distributed-systems/</link>
		<description>Recent content in Distributed-Systems on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 06 Jan 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Monolith vs Microservices: Starting With the Right Question</title>
				<link>https://dplabs.tech/blog/monolith-vs-microservices/</link>
				<pubDate>Mon, 06 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/monolith-vs-microservices/</guid>
				<description>&lt;p&gt;The monolith vs microservices debate has produced more heat than light over the past decade. Both sides have oversimplified. &amp;ldquo;Monoliths don&amp;rsquo;t scale&amp;rdquo; is demonstrably false — StackOverflow ran a monolith for years serving massive traffic. &amp;ldquo;Microservices are only for large teams&amp;rdquo; ignores the many small teams that have shipped them successfully.&lt;/p&gt;&#xA;&lt;p&gt;The real question is not which architecture is better in the abstract. It&amp;rsquo;s which architecture fits your current constraints: your team size, your organizational structure, your operational maturity, and your actual scaling requirements.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Distributed Systems: The Problems You Get for Free</title>
				<link>https://dplabs.tech/blog/distributed-systems-problems/</link>
				<pubDate>Mon, 28 Oct 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/distributed-systems-problems/</guid>
				<description>&lt;p&gt;Every system that communicates over a network is a distributed system, and distributed systems fail in ways that single-process applications don&amp;rsquo;t. This is not opinion — it&amp;rsquo;s physics. Networks drop packets. Clocks drift. Services restart. Disks fail. These things happen regardless of how carefully you write your application code.&lt;/p&gt;&#xA;&lt;p&gt;The teams that get distributed systems right don&amp;rsquo;t eliminate these failures. They design so that their systems remain correct despite them.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
