design patterns - controller/service/repository style, should service wrap repository for other service -
my project followed controller/service/repository style, usercontroller -> userservice -> userrepository , shopcontroller -> shopservice -> shoprepository. want fetch user shopservice, should call userservice or call userrepository directly shopservice.
as per understanding repository should accessed service layers.
expose known interfaces via service layer. changes repository (like underlying orm change or db change) go unknown consumer client.
so answer question - call userservice.
Comments
Post a Comment