.net - Interface programming -
background
a developer on team has implemented application reviewing. has used interfaces everywhere. app has typical service layer, data layer , poco objects passed website down db.
assumption
ioc used (through unity) inject runtime concrete service , data class. pocos have nothing , set methods on public properties.
question
i understand why interface used @ service , data layer why use interfaces on poco objects? overkill?
do poco interfaces serve purpose? if yes, may not overkill. however, if not used, violate yagni principle.
however, on more general note, i'm beginning think properties on interfaces design smells, violate law of demeter.
i posted some thoughts on better abstractions.
Comments
Post a Comment