<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ddd on Pasi Dev</title><link>https://dev.pasi.pl/tags/ddd/</link><description>Recent content in Ddd on Pasi Dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 11 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://dev.pasi.pl/tags/ddd/index.xml" rel="self" type="application/rss+xml"/><item><title>Hexagonal Architecture Abuse: When Organization Becomes Obfuscation</title><link>https://dev.pasi.pl/hexagonal-architecture-abuse-when-organization-becomes-obfuscation/</link><pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate><guid>https://dev.pasi.pl/hexagonal-architecture-abuse-when-organization-becomes-obfuscation/</guid><description>&lt;p&gt;Hexagonal architecture (also known as Ports and Adapters) is a powerful way to design software that is independent of frameworks, databases, or UI layers. Its main goal is to isolate the &lt;strong&gt;core business logic&lt;/strong&gt; from the outside world by enforcing clear boundaries. However, in many projects, this pattern is over-engineered to the point where the supposed simplicity turns into a maze of indirection, deeply nested folders, and needless abstractions.&lt;/p&gt;
&lt;h2 id="the-problem-overstructuring-a-simple-concept"&gt;The Problem: Overstructuring a Simple Concept&lt;/h2&gt;
&lt;p&gt;Many developers (including me) start with the intent of using hexagonal architecture but quickly spiral into the following:&lt;/p&gt;</description></item></channel></rss>