<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clean Architecture on</title><link>https://eunus.dev/tags/clean-architecture/</link><description>Recent content in Clean Architecture on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Sun, 09 Nov 2025 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/clean-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>How DDD Helps Simplify Business Logic and Speed Up Development</title><link>https://eunus.dev/blog/how-ddd-helps-simplify-business-logic-and-speed-up-development/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/how-ddd-helps-simplify-business-logic-and-speed-up-development/</guid><description>Imagine walking into an office to request some data.
In one building, there is no manager. You enter, search files, validate rules, double-check policies, and repeat work that others already did.
Without DDD With the help of domain manager In another building, there is a manager. You simply ask. The manager knows the rules, validates everything once, and hands you trusted information.
Why DDD Was Introduced # Before Domain-Driven Design, many systems looked like an office with no manager.</description></item></channel></rss>