title: Getting started with Domain Driven Design on an ecommerce site
body: <p>having a tough time figuring out how to model the expected product behavior.</p>
  
  <p>Basically, the customer's inventory is managed along products and skus.</p>
  
  <p>A product has many skus, but a single sku accounts for several product attributes.</p>
  
  <p>Let me give an example.</p>
  
  <p>Let's say i'm selling you a shirt.  "Shirt" is the product with some product ID.  If it comes in small, medium, large, then each of those sizes would be associated with a sku #.  </p>
  
  <p>easy enough so far, but if the shirt also comes in multiple colors, let's say red, yellow, and green, then there will be nine skus (red/small, red/medium, red/large, yellow/small, and so on).</p>
  
  <p>Add to that the challenge that the types of attributes can be different for different products.  A shirt might have sizes and colors, a handbag might have different handle styles or patterns, and I won't know ahead of time, these are things that the customer needs to be able to input in an adhoc fashion.</p>
  
  <p>Any ideas on how to approach this from a DDD perspective? I"ve been baking my noodle on it for a few days now.</p>
  
  <p>Thanks.</p>