<?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>Bounded-Context on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/bounded-context/</link><description>Recent content in Bounded-Context on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Sun, 17 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/bounded-context/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 14 &amp; 15 – Maintaining Model Integrity / Distillation</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-14/</link><pubDate>Sun, 17 Aug 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-14/</guid><description>&lt;p>Apologies for not posting the Week 14 thread last week. We had a mix-up with scheduling and a couple of us were catching up on reading. Given that the two chapters flow nicely into each other, it worked out okay to talk about them together.&lt;/p>
&lt;h2 id="chapter-14--maintaining-model-integrity">Chapter 14 – Maintaining Model Integrity&lt;/h2>
&lt;p>This chapter was more tactical than philosophical, which made for a slightly different reading pace. It dives into the patterns for preserving the integrity of large systems by managing how different models interact. I found the distinction between &lt;strong>Shared Kernel&lt;/strong> and &lt;strong>Customer/Supplier&lt;/strong> particularly useful — one speaks to tight alignment, the other to necessary detachment. The &lt;strong>&amp;ldquo;Conformist&amp;rdquo;&lt;/strong> pattern also stood out, not because it&amp;rsquo;s ideal, but because it acknowledges the reality of working with upstream teams that you have no leverage over.&lt;/p></description></item></channel></rss>