Let's use order entry as an example.

A chatty interface (fine grained) provides the following methods/operations:
- createOrder
- addItem
- processOrder

And a fatty interface (coarse grained) provides the following method/operation:
- submitOrder

The chatty scenario is reminiscent of distributed object technologies, where the client performs remote operations on the service-based Order object. Multiple message exchanges are required to submit the order (one to create the order, one for each item in the order, and one to process the order).

The fatty scenario requires the client to manage and maintain it own copy/version of the Order object, and it requires only one message exchange to submit the order.

Anne

On 1/18/06, jeffrschneider <[EMAIL PROTECTED]> wrote:

> > I'd still like to understand what folks mean by "coarse grained
> > interface".  I see many people *saying* they're doing them, but
when I
> > look around at what's deployed, all I see are what I would
personally
> > call "fine grained interfaces".  To me, "coarse grained"
= "general".
> >
> > Mark.
> > --

Mark - you should have fun with this one... :-)

'Coarse Grain' = the level of granularity necessary to reduce the
chatty-ness of an interaction. (Fatty over chatty). Typically, a
coarse grain call is one that identifies a Verb + a Noun and in one
call passes the adjectives and the predicates that are need to fulfill
an 'action'.











Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/







SPONSORED LINKS
Service-oriented architecture Computer monitoring software Free computer monitoring software


YAHOO! GROUPS LINKS




Reply via email to