What is a practical way to model lookup tables in Domain Driven Design (DDD)?

Question

I\'m just learning DDD (Eric Evans book is open in front of me) and I\'ve come across a problem that I can\'t find an answer for. What do you do in DDD when you\'re just trying

Answer 1

You're reading the wrong book if you want to learn how to do DDD without over complicating it. :-)

The simplest solution you're proposing is fine if it meets your needs. Encapsulating address data in business objects can be as simple or as complicated as your application demands. For example, the State object has a one-to-many relationship with County so Employee really just needs to reference a County if you chose to model it that way. I would only introduce that sort of complexity if required.

Additionally, I don't think there's much to be gained by defining interfaces for your repositories unless there's a real possibility that you might have multiple repositories for your objects.