- Model everything as value objects first eg. even customers if that was part your domain. When you realise they need an identity (lifecycle), then turn them into entities.
https://skillsmatter.com/skillscasts/1981-simple-is-better
http://stackoverflow.com/questions/12584966/where-to-bind-dto-into-domain-model
http://www.wpexplorer.com/wordpress-page-templates-plugin/
https://medium.com/@naveennegi/domain-driven-design-in-elixir-4dc416ac0a36
Ports & Adapters
https://youtu.be/u6oTg5oRH24?t=32m43s
https://www.slideshare.net/profpv/hexagonal-architecture-in-php
http://blog.gauffin.org/2013/01/repository-pattern-done-right/
http://how-it-can-in-nodejs.blogspot.co.uk/2016/04/node-js-rest-api-with-unit-of-work-and.html
With DAO https://www.slideshare.net/Yaboomaster1/save-repository-from-save
Hydrating entities
http://mohdhallal.github.io/blog/2013/10/05/entity-hydration-done-right/
https://lostechies.com/gabrielschenker/2015/04/28/ddd-applied/
http://odetocode.com/blogs/scott/archive/2010/06/13/repositories-and-the-save-method.aspx
BDD is examples you use in conversation to illustrate behaviour - https://www.youtube.com/watch?v=83GbyDpJDI4
Using real numbers and trying to get the same conclusion as the developer and as the client, means the business rules are being accurately translated