<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Event-Driven on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/event-driven/</link>
		<description>Recent content in Event-Driven on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 23 Dec 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/event-driven/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Event-Driven Architecture: When Events Help and When They Hurt</title>
				<link>https://dplabs.tech/blog/event-driven-architecture/</link>
				<pubDate>Mon, 23 Dec 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/event-driven-architecture/</guid>
				<description>&lt;p&gt;Event-driven architecture has become fashionable, which means it&amp;rsquo;s being applied in situations where it doesn&amp;rsquo;t fit. Events are a powerful architectural tool for specific problems. They&amp;rsquo;re a significant operational burden when applied indiscriminately.&lt;/p&gt;&#xA;&lt;p&gt;Understanding when events help and when they hurt requires understanding what problems they actually solve.&lt;/p&gt;&#xA;&lt;h2 id=&#34;events-vs-commands&#34;&gt;Events vs Commands&lt;/h2&gt;&#xA;&lt;p&gt;The distinction matters more than most tutorials acknowledge.&lt;/p&gt;&#xA;&lt;p&gt;A &lt;strong&gt;command&lt;/strong&gt; expresses intent: &amp;ldquo;place this order,&amp;rdquo; &amp;ldquo;cancel this payment,&amp;rdquo; &amp;ldquo;reserve this inventory item.&amp;rdquo; It&amp;rsquo;s addressed to a specific recipient and implies that recipient is responsible for handling it. Commands can be rejected. They have an expected response.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
