Re: [service-orientated-architecture] Re: Coarse grained interfaces?

[Amit Gupta \(FSI\)]

How about following example:-   Adding a Purchase Order with Fine Grained Interface :-     - Open a Connection with DB with specified username/passwd     - Insert PO header     - For each PO Line Item         + Insert PO Line Item     - Close the connection with DB   Adding the same Purchase Order with Coarse Grained Interface:-     - Insert PO       Here the configuration of "Insert PO" step has instructions on     DB URL, username/passwd, transaction mode etc. and also     how incoming PO has to be mapped to multiple tables in the     target DB.. Note that all this "configuration" when moved out of     process definition, helps focussing on the "actual business     process" in the process definition.   Thanks, Amit Gupta Fiorano Software Inc ----- Original Message ----- From: jeffrschneider To: service-orientated-architecture@yahoogroups.com Sent: Thursday, January 19, 2006 12:49 AM Subject: [service-orientated-architecture] Re: Coarse grained interfaces? > > 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  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.