<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BoundedContext on emsenn.net</title>
    <link>https://emsenn.net/tags/boundedcontext/</link>
    <description>Recent content in BoundedContext on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/boundedcontext/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Domain-Driven Design</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/domain-driven-design/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/domain-driven-design/</guid>
      <description>&lt;p&gt;Domain-Driven Design (DDD) is an approach to software development&#xA;that organizes code and teams around a model of the business domain.&#xA;Eric Evans introduced the approach in &lt;em&gt;Domain-Driven Design: Tackling&#xA;Complexity in the Heart of Software&lt;/em&gt; (Addison-Wesley, 2003). Evans&#xA;argued that the primary complexity in most software projects is not&#xA;technical but conceptual &amp;mdash; it lies in the domain the software serves.&#xA;DDD addresses this by making the domain model the central artifact&#xA;around which development is organized.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
