Allow and separate Infra-structure Services and Repository


Originally, this architecture implements only repositories for infra-structure which is semantically wrong if you think about an "EmailRepository".
We should have a messaging Service, which is nowhere in the application level, but in the infra-structure level.
Therefore we may have the following:
  • Domain.Entities
  • Domain.ValueObjects
  • Domain.Enumerations
  • Domain.Exceptions
  • Infrastructure.Repositories
  • Infrastructure.Services
  • Infrastructure.Providers
  • Application.Workflows
  • Application.Services


hudsonmendes wrote Jun 30, 2011 at 1:29 PM

Expected for v1.1

wrote Sep 9, 2011 at 11:07 PM

wrote Feb 13, 2013 at 6:02 PM