anchor.diff:  * Data access: Curator + Repositories
   * Domain model: Plain Ruby objects (as much as possible)
   * UI: Sinatra + Javascript + Twitter bootstrap
  +* _GOAL: Minimal implementation of full stack by May 18_
   
   === Version 2 - Rails (i.e. ActiveRecord)
   
  
positive.code: 
  * link:https://github.com/patrikfr/dddsample[Written in Java in 2009].
  
  History
  
  * Sep 2008 First public release: 1.0.
  * Jan 2009 Sample application tutorial at the JFokus conference in Stockholm.
  * Mar 2009 Sample application tutorial at the QCon conference in London.
  * Mar 2009 New public release: 1.1.0. See changelog for details.
  * 2010/2011 https://github.com/SzymonPobiega/DDDSample.Net[Ported to .NET in several flavors].
  * May 8 Begin porting to Ruby at https://github.com/paulrayner/ddd_sample_app_ruby
  * May 13, 2013 Presentation of early work on port of sample app to Ruby at DDD Denver. Slides are http://virtual-genius.com/presentations/ddd_with_ruby_20130613.html[available online].
  
  _The .NET port is being used as the primary basis for this Ruby port._
  
negative.code: 
  === Goal
  
  The goal of this sample app is to provide an idiomatic Ruby port of the DDD sample application. It should remain faithful to the intention of the purposes of the original DDD sample application.
  
  === Why a Ruby port?
  
  Because Paul wanted to learn Ruby and see how well it supports DDD. Also, interested in questions like:
  
  * How does the choice of Ruby affect the implementation of the DDD building block patterns? 
  * How well does an opinionated MVC framework like Rails support doing DDD? 
  * What are implications of choosing a document store like MongoDB for aggregate design and eventual consistency? 
  
  === Why a DDD Sample App?
  
  