W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2002

Re: Web Services 2.0?

From: Igor Gorbunov <gorbunov@pacbell.net>
Date: Mon, 03 Jun 2002 19:58:58 -0400
To: www-ws-arch@w3.org
Message-id: <KCEBLPJMAEJKHLAHKAGHKEKDCCAA.gorbunov@pacbell.net>

Farelets Examples
(where regular Web Services fall short, but Farelets can deliver):

1. Reliability
Businesses are unlikely to dedicate mission critical activities to remote
Web Service because of Internet's inherent lack of reliability.

EXAMPLE 1: scheduler ("CRON"-like) Web Service. A main concern in this case
is reliability. As soon as this issue is addressed, scheduler could become a
very valuable Web Service application.


2. Performance
In many cases performance limitations prevent customers from using otherwise
effective Web Service.

EXAMPLE 2: Sorting, graph traversing, other computational tasks or
algorithms do not make good Web Services until their performance is
dramatically improved. The root of performance limitations in this case is
Web Services remoteness. It is also true for compound- and broker-type Web
Services.


3. There are situations where remote Web Service is trusted but the
communication channel is not.

EXAMPLE 3: flight tracking Web Service or online shopping Web Service, which
sends sensitive data over the Internet.


4. Heavily loaded Web Services can be ineffective. Addressing clustering,
load balancing and other scalability issues may require either extensive
programming or employing some kind of sophisticated tools and frameworks
even for simpler Web Services.

EXAMPLE 4: currency converter on your home machine, which suddenly becomes
very popular.

For graphical illustrations and more details, please visit:
<a href="http://www.entente-llc.com/farelets/Farelets.htm#n7">Farelets
docs</a>

Thank you,
Igor Gorbunov
Received on Monday, 3 June 2002 19:55:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT