Re: [xml-dev] What are the "externalities" of deploying a web service?

[Fraser Goffin <goffinf@googlemail.com>]

Of course. My mistake when clicking the Reply button.

Just to reiterate, of course many organisations and private
individuals provide services on the public Internet and in that case
your points about dealing with unexpected demand are perfectly valid
and can be a blessing or a curse depending on the side-effects of that
demand (more orders vs. less order+more costs because of an
unintentioned DoS).

For internal services and/or those made available as part of specific
trading partner relationships, there tends to be a greater level of
goverance to provide some assurance around service level expectations,
which in some cases may include incentives and penalities.

Hope this adds to the debate

Fraser.

2010/1/16 Costello, Roger L. <costello@mitre.org>:
> Hi Fraser,
>
>    Excellent!
>
>    How about sharing this with the rest of the xml-dev community?
>
> /Roger
>
> ________________________________________
> From: Fraser Goffin [goffinf@googlemail.com]
> Sent: Saturday, January 16, 2010 10:42 AM
> To: Costello, Roger L.
> Subject: Re: [xml-dev] What are the "externalities" of deploying a web  service?
>
> For corporate web services (internal or external facing) this would
> really be part of the run-time governance model. That is, there isn't
> carte-blanche access to services, there is controlled access which has
> associated SLA's. The run-time governamce is there to ensure both that
> SLA thresholds are not exceeded (and to proactively report when they
> are approached) and to ensure that 'rogue' access to services is
> either prevented or gives rise to alerts. Clearly in many business
> contexts, performance, avialabilaity, resilience, scalability (n fact
> all of the non functionals) can't be left to the vagueries service
> popularity.
>
> Fraser.
>
> 2010/1/16 Costello, Roger L. <costello@mitre.org>:
>> Hi Folks,
>>
>> Consider these two examples:
>>
>> 1. When you drive, you pay for only gasoline and maintenance. You don't pay for the noise and pollutants that your car emits.  You also don't pay for the added congestion and delays that you impose on other drivers.
>>
>> 2. When society is educated, it costs less to produce signs, ballots, tax forms, and other information tools. Literacy enables a democracy to function effectively, and higher education may stimulate scientific discoveries that improve the welfare of society. When you acquire an education, however, you do not get a check in the amount of savings your education will create for society.
>>
>> The first example shows costs that you incur but are borne by others not directly involved.
>>
>> The second example shows benefits that you incur but are accrued by others not directly involved.
>>
>> Externalities are the costs or benefits of a market activity borne or accrued by someone who is not a direct party to the market transaction.
>>
>> What are the externalities of deploying a web service?
>>
>> Here's one: Suppose you deploy a web site and it is massively successful - lots of people visit your web site. You assume the costs of hiring land, labor, and capitol. But you don't bear the costs associated with the increased congestion and delays you impose on other users of the Internet.
>>
>> Increased congestion and delays are externalities of deploying a web service. What are the other externalities?
>>
>> Who pays for the externalities? For instance, who pays for the additional routers and DNS servers?
>>
>> /Roger
>>
>>
>> P.S. The two examples and the definition of "externalities" come from the book: "Economics" by Boyes and Melvin.
>>
>>
>>
>> _______________________________________________________________________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>> subscribe: xml-dev-subscribe@lists.xml.org
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>>