<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: domain-driven-design</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/domain-driven-design.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-08-16T13:35:14+00:00</updated><author><name>Simon Willison</name></author><entry><title>Domain-Driven Design in an Evolving Architecture</title><link href="https://simonwillison.net/2008/Aug/16/infoq/#atom-tag" rel="alternate"/><published>2008-08-16T13:35:14+00:00</published><updated>2008-08-16T13:35:14+00:00</updated><id>https://simonwillison.net/2008/Aug/16/infoq/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.infoq.com/articles/ddd-evolving-architecture"&gt;Domain-Driven Design in an Evolving Architecture&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
How the team at guardian.co.uk used Domain-Driven Design in their recent two year rebuild. The core of DDD is having end users involved with domain modeling, which results in a shared domain language that should be understood by everyone involved.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domain-driven-design"&gt;domain-driven-design&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/guardian"&gt;guardian&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/modeling"&gt;modeling&lt;/a&gt;&lt;/p&gt;



</summary><category term="domain-driven-design"/><category term="guardian"/><category term="modeling"/></entry></feed>