Domain-Driven Design in PHP

Surrogate Identity

Sometimes when using an ORM to map Entities to a persistence store, some constraints are imposed — for example, Doctrine demands an integer field if an IDENTITY generator strategy is used. This can conflict with the Domain Model if it requires another kind of Identity.

The simplest way to handle such a situation is by using a Layer Supertype, where the Identity field created for the persistence store is placed:

namespace Ddd\Common\Domain\Model;abstract class IdentifiableDomainObject{    private $id;    protected function id()    {        return $this->id;    }    protected function setId($anId)    {        $this->id = $anId;    }}namespace Acme\Billing\Domain;use Acme\Common\Domain\IdentifiableDomainObject;class Order extends IdentifiableDomainObject