<?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>Layered-Architecture on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/layered-architecture/</link><description>Recent content in Layered-Architecture on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Sun, 01 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/layered-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 4 – Isolating the Domain</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-04/</link><pubDate>Sun, 01 Jun 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-04/</guid><description>&lt;p>&lt;em>Discussion led by &lt;strong>Ayush Gupta&lt;/strong>&lt;/em>&lt;/p>
&lt;hr>
&lt;p>I will start off with quoting this line from the chapter which I think really resonates with the idea of design principles we are discussing:&lt;/p>
&lt;blockquote>
&lt;p>&amp;ldquo;When domain logic is embedded in other layers, it becomes hard to see, test, and evolve.&amp;rdquo;&lt;/p>
&lt;/blockquote>
&lt;p>One bit I really liked was the distinction between Application and Domain layers. The app layer doesn&amp;rsquo;t &lt;em>do&lt;/em> business logic; it &lt;em>orchestrates&lt;/em> it. That alone can clean up so much of the mess I&amp;rsquo;ve seen in bloated service classes.&lt;/p></description></item></channel></rss>