<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Domain-Driven-Design on F. Latini - IT Engineer</title><link>https://latini.dev/tags/domain-driven-design/</link><description>Recent content in Domain-Driven-Design on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 11 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/domain-driven-design/index.xml" rel="self" type="application/rss+xml"/><item><title>DDDD - Domain Driven Design for Dummies</title><link>https://latini.dev/posts/dddd-domain-driven-design-for-dummies/</link><pubDate>Mon, 11 May 2026 09:00:00 +0000</pubDate><guid>https://latini.dev/posts/dddd-domain-driven-design-for-dummies/</guid><description>&lt;p&gt;&lt;strong&gt;DDDD&lt;/strong&gt; - Domain Driven Design for Dummies. One extra D, because by the time you finish Eric Evans&amp;rsquo; &lt;a href="https://www.dddcommunity.org/book/evans_2003/"&gt;original 560-page book&lt;/a&gt;, you&amp;rsquo;ll feel like a dummy regardless. This is the shorter version, the one I wish I&amp;rsquo;d read before trying to apply DDD on a real project for the first time.&lt;/p&gt;
&lt;h2 id="what-ddd-actually-is"&gt;
 What DDD actually is
 &lt;a class="heading-link" href="#what-ddd-actually-is"&gt;
 &lt;i class="fa fa-link" aria-hidden="true"&gt;&lt;/i&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Strip away the jargon and DDD is about one stubborn idea: &lt;strong&gt;the structure of your code should reflect the structure of the business it serves.&lt;/strong&gt; Not the database. Not the framework&amp;rsquo;s defaults. The business.&lt;/p&gt;</description></item></channel></rss>