Should I combine unrelated interfaces into a single library?
Posted
by mafutrct
on Stack Overflow
See other posts from Stack Overflow
or by mafutrct
Published on 2010-03-19T12:20:03Z
Indexed on
2010/03/19
12:31 UTC
Read the original article
Hit count: 153
architecture
Situation is like this:
There are independent 5 services. Each service consists of a project for interface, implementation and test. Example:
LocalizationService.Interfaces
LocalizationService.Implementation
LocalizationService.Test
There is a WCF service for each of the services:
LocalizationService.WcfContract (including DataContracts)
LocalizationService.WcfHost
The client applications are probably mostly going to use all of the services. Should I combine all service interfaces into a common one?
AllServices.AllInterfaces
In my opinion, this is a bad idea. The services are independent and there is no reason to introduce a dependency. I imagine that especially testing becomes more difficult. However, one may argue that having to include 5 libraries is too much of a hassle.
(I'm not sure how to tag this. Feel free to retag.)
© Stack Overflow or respective owner
