--- In [email protected], JP Morgenthal <[EMAIL PROTECTED]> wrote:
> To speak of things like "facade services" confuses SODA with > general SOA in my opinion. This is just helper code to make a > software system work, it has nothing to do with actually providing > the service you wish to provide. Doesn't this assume 1) a facade service adds no value; 2) that basic services cannot be combined to create new, higher-level services; 3) that such a notion is applicable only to application development and not to other areas such as business architecture? Let's examine a set of travel business services. One might have hotel, air, car rental, and event (shows, theme parks, zoos, etc.) services available for individual use. Bundles that combine two or more of those for a reduced fee could be represented as facade services. Perhaps this is a definition issue and it is the term "facade" that gives pause. Would another descriptive name like "intermediary" or "aggregate" or "functionality added" or "value added" fit better? -Rob
