Geek Answers Handbook

How to use the principle of single responsibility in large wcf services?

At the moment we use about 7 services. It's pretty big there.

Does anyone have experience with the principle of shared responsibility and WCF services? Does this mean that you will have many small contracts? If so, how do you deal with this in your application?

+5
source share
3 answers

I think you are confusing one responsibility with interface segregation.

From the point of view of the client / service interface, you should keep your contracts harsh and medium. Below is an example of this.

SRP , . , . , , , . . , SOA - , , .

: , , -. . , , , : , -, -. . / 3, , , WCF. .

, .

+7

hanselminutes:

- .

.,

+1

You can apply a facade template for a web service that interacts with a client, and in the implementation code you can apply a separate responsibility to make it serviceable.

+1
source

More articles:


All Articles