Re: [service-orientated-architecture] What is SOA?

Sat, 01 Jul 2006 04:37:55 -0700

To build on this

SOA is about architecture, which means its about thinking and planning, REST, SOAP, EDA et al are not architectural styles they are implementation styles.  You can have a consistent SOA that is implemented in any one of those implementation approaches. I blogged about this related to SOA 2.0 (http://service-architecture.blogspot.com/2006/06/soa-20-what-next.html).

SOA has to not be about technology because I think we've pretty much proven that as an approach being focused on technology doesn't work.

Steve


On 30/06/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

I would put REST into a slightly different category from the technologies. REST is an architectural style, not a technology. REST has a lot in common with SOA, but it is resource-oriented rather than service-oriented. Nonetheless, the two architectural styles are compatible. You can expose services as resources. REST applies additional constraints to SOA, which for some applications provide really beneficial advantages (especially scalability).

If you start your design from a SOA perspective, then you have a choice at implementation time as to whether or not you want to expose the service as a resource (via a RESTful interface). In that regard, REST feels more like a technology than an architectural style. From the SOA perspective, I would put REST into the same category as "event driven architecture" (EDA). Both constrain and influence service design.

(If you start your design from a REST perspective, then you have a choice as to whether you want your resource to be a service. It's a different mindset. But this is a SOA discussion list, therefore my analysis comes from the SOA perspective.)

Anne



On 6/30/06, Steve Jones < [EMAIL PROTECTED]> wrote:

Ahhh and here is the number one thing that I think SOA is NOT about....

Technology.

REST, SOAP, WSDL, Pink Pixies, JMS, UML, BPMN, BPEL et al have NOTHING to do with Architecture they are all about the design and implementation.

Part of the Service Oriented Delivery of IT... or SOD IT.

Steve



On 30/06/06, Jim Alateras < [EMAIL PROTECTED] > wrote:


Mark,

Since REST is an architectural style based on resource abstractions
does it fulfill the first criteria.....I guess the resources are exposed
as services through a uniform interface.

What's you take

cheers
</jima>


Mark Baker wrote:
> On 6/29/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>
>>
>> I list two fundamental principles:
>>- service-orientation
>>- loose coupling
>
>
> Sweet! By these measures alone, REST is a better SOA than WS. It's
> probably a toss-up wrt service-orientation, but REST is clearly more
> loosely coupled than WS because it separates the concerns of interface
> and implementation far better... as we've discussed before;
>
> http://groups.yahoo.com/group/service-orientated-architecture/message/3427
>
> Mark.
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>




__._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to