Imagine I'd create an application which uses several web services, provided

by third parties e.g. a currency converter, an interest rate calculation and

maybe several others.



My question is, doesn't this make my application very vulnerable and

dependent on availability of other bits 'n pieces? What if the server on

which the interest calculation web service resides is unavailable, or times

out - this would mean that my application as a whole would not properly

function anymore.



Now one could say: "If you develop an applic that is that important and

critical you have to make sure that you have a certain amount of guaranteed

uptime for all the web services your app consumes..."



I partly agree there, for isn't the whole idea of web services that your app

can consume anyone's web services, without you knowing where it resides and

without you being bothered whether uptime is guaranteed for all the web

services you'd use... What if the person (or company) gets rid of a specific

web service all together? You'd end up having to write your own in the end

anyway...



I would like to see your thoughts.



Thanks,

Wim

I completely agree.



I couldn't imagine implementing a soloution for a client that invaloved 

various different server being up all the time especially if my connections 

with these organisations was not strong.



I would imagine M$ will be setting up ultra reliable servers to provide 

these web services and will be tied in with hailstorm so it will increase 

the tie in to m$ (which by the way as a mcp i do not think a bad thing) I 

think we will develop web services and submit them for use to a central m$ 

server for reuse amongst the community or in more specific circumstances to 

authorised users. If you look at the present ms passport system you can see 

the basic model for web services.



I would only use these services for certain non-mission critical apps at the 

moment and there must be an alternative. Perhaps services will be mirrored 

on various different servers to negate the chance of down time.



my 2 cents



ben









>From: Wim Hollebrandse <Wim.Hollebrandse@c...>

>Reply-To: "ASP+" <aspx@p...>

>To: "ASP+" <aspx@p...>

>Subject: [aspx] Web Services - is there a downside...?

>Date: Mon, 6 Aug 2001 11:34:20 +0100

>

>Imagine I'd create an application which uses several web services, provided

>by third parties e.g. a currency converter, an interest rate calculation 

>and

>maybe several others.

>

>My question is, doesn't this make my application very vulnerable and

>dependent on availability of other bits 'n pieces? What if the server on

>which the interest calculation web service resides is unavailable, or times

>out - this would mean that my application as a whole would not properly

>function anymore.

>

>Now one could say: "If you develop an applic that is that important and

>critical you have to make sure that you have a certain amount of guaranteed

>uptime for all the web services your app consumes..."

>

>I partly agree there, for isn't the whole idea of web services that your 

>app

>can consume anyone's web services, without you knowing where it resides and

>without you being bothered whether uptime is guaranteed for all the web

>services you'd use... What if the person (or company) gets rid of a 

>specific

>web service all together? You'd end up having to write your own in the end

>anyway...

>

>I would like to see your thoughts.

>

>Thanks,

>Wim

>

>