WCF Services - Best Practices for grouping Classes
We're planning our architecture and considering how to group our Classes
into WCF Services.
We could create one Service per Class or tight collection of Classes. For
instance, one Service for everything to do with User Data. That would lead
to quite a lot of relatively small Services.
Alternatively, we could create groupings of Classes into a Service. For
instance, one service to include Classes for all data entities (User,
Order, Customer etc etc).
Or something in between.
I may have a misconception about how these should be related or be looking
in the wrong places, but I can't find any guidance.
Is having many Services a bad idea? Do they each have a significant
overhead? If we did group them and later wanted to change the groupings,
would that be an issue?
No comments:
Post a Comment