Comments on: Domain-Driven Design with Zend Framework

By: Federico

Federico — Thu, 11 Feb 2010 10:42:26 +0000

Here's an example:

class User {
    private $id; 
    private $name;
    private $password;

    public function setId($id)
    public function getId()
    public function setName($name)
    public function getName()
    public function setPassword($password)
    public function getPassword()
}

class UserRepository {
    public function find($id) 
}

class UserService {
    public function authenticate(User $user)
}

By: Juan

Juan — Thu, 11 Feb 2010 03:34:01 +0000

Others said business logic should be in the domain and only those logic that are not fit to any entity or value objects should be placed in the service.

By: Federico

Federico — Wed, 10 Feb 2010 15:35:14 +0000

Well, its purpose is to hold methods that implement business logic. They do not provide methods to access data.

By: Juan

Juan — Tue, 09 Feb 2010 05:29:24 +0000

Thanks federic. So what are the purpose of service classes then?

By: Federico

Federico — Mon, 08 Feb 2010 10:20:11 +0000

Repositories are not part of the Service Layer, they are part of the Domain Layer. The Repository provides a higher level of data manipulation, and acts as a link between the Domain and Persistence Layers (Entity – Repository – DAO).

Service classes are not part of the Domain or Persistence Layers and therefore do not provide methods to access data, such as finders. Finders are usually found in the Repository.

By: Juan

Juan — Sat, 06 Feb 2010 00:41:11 +0000

Hi,

I’m confused about domain and service, can someone provide a sample code for domain and service in action?

Thanks

By: Olagato’s blog

Olagato’s blog — Tue, 03 Nov 2009 10:28:51 +0000

[...] Por otra parte los mappers heredarán de Zend_Mapper. A esta nueva orientación se le denomina Domain Driven Design (DDD). Estoy siguiendo el tema con este libro y la verdad es que todo tiene muy buena pinta, aunque [...]

By: My Web Development Bookmarks

My Web Development Bookmarks — Thu, 22 Oct 2009 04:23:29 +0000

[...] Read this article: Domain-Driven Design with Zend Framework « Federico Cargnelutti [...]

By: Roman

Roman — Thu, 15 Oct 2009 07:24:32 +0000

Federico,

As far as I know, only Aggregate Root is recomended to have a Repository. I’m really stuck with such implementation details. DDD concepts are obviosly interesting, but I’ve lots of misunderstandings relative to implementation :\

By: Federico

Federico — Mon, 18 May 2009 16:37:19 +0000

Gotcha. I guess that, if you are working with DAOs, there are different ways of doing it. You already mentioned 2 of them I think. You could also have a repository that represents the relationship between both entities, for example, UserProfileRepository. And then use UserProfileDAO to query the database, join the User and Profile tables and return the data to the repository so it can populate the User and Profile objects.

I don’t know if this is allowed in DDD, but I haven’t develop a Repository that manages this complexity for me yet.