<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Microservices on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/microservices/</link>
		<description>Recent content in Microservices 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/microservices/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>The Modular Monolith: An Architecture Pattern That Deserves More Attention</title>
				<link>https://dplabs.tech/blog/modular-monolith-architecture/</link>
				<pubDate>Mon, 14 Oct 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/modular-monolith-architecture/</guid>
				<description>&lt;p&gt;The software industry has a microservices fixation. Over the last decade, &amp;ldquo;monolith&amp;rdquo; became almost a pejorative, and teams moved to distributed architectures before they had the scale, team size, or operational maturity to justify them.&lt;/p&gt;&#xA;&lt;p&gt;The result has been widespread over-engineering: systems that are harder to understand, harder to debug, harder to change, and more expensive to operate — not because distributed systems are inherently bad, but because the problems they solve weren&amp;rsquo;t actually present.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
