Why limit WCF ServiceContracts to 10-20 OperationContracts?
Posted
by Gary B
on Stack Overflow
See other posts from Stack Overflow
or by Gary B
Published on 2010-03-17T15:32:36Z
Indexed on
2010/03/17
15:41 UTC
Read the original article
Hit count: 268
Filed under:
wcf
I've seen recommendations (Juval Lowy, et al) that a service contract should have "no more than 20 members...twelve is probably the practical limit". Why? It seems that if you wish to provide a service as the interface to a relatively large db (50-100 tables) you're going to go way past that in just CRUD alone. I've worked with plenty of other services that provided hundreds of 'OperationContracts'...is there something peculiar about WCF? Is there something I'm missing here?
© Stack Overflow or respective owner
