Featured post
domain driven design - wcf wrapper around ddd project -
i have 2 questions - :
1) have provide wcf wrapper around ddd project. , below design correct ?
mvc -> servicelayer(wcf) -> app -> domain -> infra
or app service act wcf service.
2) know have expose dto's in service layer. so, ever service method's expose in domain services , app services, have create same name method service in service layer , call domain service , app service service layer.
it's hard answer kind of question since depends needs , requirements.
for point of view there not "a best solution" solution fit requirement.
anyway in general doing correct have make sure fit needs: sometime obsessed following best practice risk add many layer done 2 :-)
the thing can can't expose dto way transfer objects (from high point of view compared protocol) doesn’t object exposing. create poco objects instead , expose them in case need "assembler" layer used service layer create poco objects against "domain model". both assembler , mvc layer know poco objects.
i hope makes sense
- Get link
- X
- Other Apps
Comments
Post a Comment