RE: [service-orientated-architecture] Zapthink on SOA/REST

[Harm Smit]

Title: Message

-1. Anne, I don't know which "traditions" you are referring to for a discipline that is only a few years old. Yes, I know we disagree on this point: to you, CORBA and DCOM are also SOA -- to me, SOA is no older than Web Services. But maybe this is precisely why we are diverging here: could it be that your position is inspired by the heritage of the distributed object paradigm? As the draft OASIS SOA Reference Model puts it in its section "How is SOA different?": "To use an object, it must first be instantiated, while one interacts with a service where it exists". IOW, in SOA there is no notion of instantiation.   Furthermore, it seems to me that quite some confusion stems from not distinguishing between abstract services and the actual implementations thereof, through the corresponding service providers.   Taking your stock quote example, let's assume there is just one universal abstract stock quote service. But that doesn't mean there is just one universal stock quote service provider, and one may have very good reasons to prefer one service provider over another, e.g., because they don't cover the same range of stock symbols.   Similarly, when invoking the services of a smart lightbulb, I'd need to know whether it's the lightbulb in the kitchen or the one in the bathroom. But both lightbulbs would implement the same abstract service, even if they were from different vendors.   HTH, Harm.     -----Original Message----- From: service-orientated-architecture@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Anne Thomas Manes Sent: vendredi 14 juillet 2006 20:06 To: service-orientated-architecture@yahoogroups.com Subject: Re: [service-orientated-architecture] Zapthink on SOA/REST +1. In a traditional service-oriented approach, a service implements a function that can be performed on multiple instances of a resource. You do not have a different service for each resource. .e.g, you have a stockQuote service -- you input a stock symbol and it returns the stock quote for that stock symbol. You don't define a separate service for each stock symbol. The latter would be a resource oriented approach -- and it makes much more sense to use a uniform interface( i.e., REST) when using a resource-oriented approach. Anne On 7/14/06, Stefan Tilkov <[EMAIL PROTECTED] > wrote: On Jul 14, 2006, at 9:52 AM, Harm Smit wrote: > The latter is rubbish. It should read: lightbulb10.turnOn() > Each lightbulb is an independent, autonomous service provider. That's the first time I've seen someone make that claim for SOA-style services. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/ __._,_.___ SPONSORED LINKS Computer software Computer aided design software Computer job Soa Service-oriented architecture 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. __,_._,___