c# - Interfaces and Coupling -
from design , loose coupling standpoint. idea have interface each class in project might part of composition model?
i have project i'm doing this, i'm getting rather lot of interfaces, in attempt keep things relatively loosely coupled.
without knowing specifics of design, that's how interface segregation principle (pdf) supposed work.
you should provide interface every class may need swap out implementation (i wouldn't create interface each dto, example).
Comments
Post a Comment