Title: Re: [service-orientated-architecture] Re: SOA Infrastructure
I believe that there is a considerable difference between SOA and SODA.  As you said, SODA is service-oriented design of applications.  SOA Infrastructure is not an application, it a set of tooling that provides governance, security and management (reliability, version management, monitoring, etc) for the service-oriented applications.  

Take UDDI for example.  It is clearly not a business application so doesn't fit into the SODA concept, but does fill an important role in SOA, hence SOA Infrastructure.  There are many such examples.

Essentially the way I think of, and describe, SOA Infrastructure is:

SOA Infrastructure provides tools and run-time services to abstract developers from the complexities of enterprise security and management policy enforcement and implementation.

>From a practical perspective, SOA Infrastructure allows application developers and architects to focus on building the business logic and interfaces for their applications, and leave issues of performance and reliability management, version management, and security to their enterprise SOA Infrastructure.

Ian

--
Ian Goldsmith - VP, Product Marketing
SOA management, security, and governance.
www.soa.com
--
Ian Goldsmith - VP, Product Marketing
Phone: +1 310 612 5649
Web services management, security, and governance.
www.soa.com



> From: JP Morgenthal <[EMAIL PROTECTED]>
> Organization: Avorcor, Inc.
> Reply-To: <[email protected]>
> Date: Sat, 11 Mar 2006 08:43:27 -0500
> To: <[email protected]>
> Subject: RE: [service-orientated-architecture] Re: SOA Infrastructure
>
> Sorry, but I have to weigh in on the title of this thread.  Here's a blog
> entry I just posted at:
> http://www.avorcor.com/morgenthal/index.php?entry=entry060311-084440
>
> SOA and SODA
> Saturday, March 11, 2006, 08:43 AM
> When the term SODA first started being bandied about I was less than
> enthusiastic about the terminology. SODA stands for Service-Oriented Design
> of Applications. However, there's been a lot of recent discussion of a topic
> termed "SOA Infrastructure", which has forced me to re-examine the SODA term
> and start to use it to help explain and differentiate between general SOA
> and a technological SOA.
>
> First of all, I do not believe there is anything called "SOA
> Infrastructure." As I explain SOA to my clients, SOA is a way of designing a
> system. A system is an abstract entity, like a lighting system, electrical
> system, and heating and cooling system. In this case the system we're
> designing is a business system. There's no infrastructure involved, just
> artifacts, components and the relationships between these two.
>
> An SOA can be used to design an Enterprise, a software system, even a
> telephone system. There's no limitation or inherent attribute that says that
> a service has to be described as a software component. To do so only limits
> the value of this architectural pattern and sets it up to be easily
> dismissed by non-technological personnel.
>
> When you get into discussions of SOA infrastructure, in my mind, you're in
> the SODA world. You're specifically talking about an implementation approach
> to a system designed using SOA. Things like registries and enterprise
> service buses are components of a software-only system. They have nothing to
> do with a banking system I designed using SOA that identifies each of the
> specific types of services the bank offers as a service.
>
> For example, I can design a bank system with a checking service, loan
> service, loan decisioning service, investment service, corporate banking
> service, etc. In each case, these services represent more than some Web
> service interface to the e-commerce offerings within each of these areas of
> the bank. They represent the service itself inclusive of the organization
> requirements, documents, processes, workflows, etc.
>
> So, stop abusing the term SOA and use the correct term for SOA relative to a
> software system, which is SODA.
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mukund
> Balasubramanian
> Sent: Friday, March 10, 2006 6:33 PM
> To: [email protected]
> Subject: Re: [service-orientated-architecture] Re: SOA Infrastructure
>
> Jerry:
>
> This is indeed a pretty good description and I agree with most of it.
>
> I don't agree with making as strict a relation as that of a type and
> instance. I think it is more appropriate to leave it at the level of
> defining architecture as the answer to the question "what are the parts and
> how do they behave" and design is the answer to the question "how are the
> parts actually going to be built".
>
> Mukund Balasubramanian
> CTO/Infravio Inc.
>
>
>
>
>
> -----Original Message-----
> From: Jerry Zhu <[EMAIL PROTECTED]>
> To: [email protected]
> <[email protected]>
> Sent: Fri Mar 10 08:29:28 2006
> Subject: Re: [service-orientated-architecture] Re: SOA Infrastructure
>
> Alex,
>
> Many here agree that architecture and design are two
> different things and architecture goes before design.
> Some may think that architecture is just a step in the
> design.  I disagree.  
>
> One way to differentiate the two is that architecture
> is the form or identity or a type. Design is an
> instance of that type and is a model that describes
> how the parts are implemented, what materials are used
> etc.  A car is an identity as opposed to a boat and a
> generic description of a car is the architecture.  A
> car can be designed into a wood car, a plastic car and
> metal car etc.  So there are infinite designs with
> respect to the same architecture.  Software
> architecture is technology dependent such as object
> oriented or service oriented etc. but it is platform
> independent.   The same architecture can be designed
> using different platforms such as J2EE or .Net etc.  
>
> Architecture has something to do with basic beliefs
> that are either accepted or rejected. Design is about
> how basic beliefs about some thing come into reality.
>
> Jerry
>
> --- Alexander Johannesen
> <[EMAIL PROTECTED]> wrote:
>
>> On 3/10/06, Jerry Zhu <[EMAIL PROTECTED]> wrote:
>>>
>>>  Architecture is not designed but defined.
>>>
>>
>> I think you'll find that architecture is used as a
>> word describing how
>> something is designed, again, pointing back to
>> design being something an
>> architect does.
>>
>> But anyways, if you look up the definitions for
>> architecture, there are as
>> many definitions as there are people trying to
>> define it. There is no one
>> answer to this, and I assert that the word itself
>> should be erased from
>> serious computer language. :)
>>
>>
>> Alex
>> --
>> "Ultimately, all things are known because you want
>> to believe you know."
>>                                                     
>>     - Frank Herbert
>> __ http://shelter.nu/
>> __________________________________________________
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>
>
>
>
> SPONSORED LINKS
> Computer software
> <http://groups.yahoo.com/gads?t=ms&k=Computer+software&w1=Computer+software&
> w2=Computer+aided+design+software&w3=Computer+job&w4=Soa&w5=Service-oriented
> +architecture&c=5&s=121&.sig=fpXcvMH1T7dIWKArM_WfrQ>   Computer aided
> design software
> <http://groups.yahoo.com/gads?t=ms&k=Computer+aided+design+software&w1=Compu
> ter+software&w2=Computer+aided+design+software&w3=Computer+job&w4=Soa&w5=Ser
> vice-oriented+architecture&c=5&s=121&.sig=aLmDc98q-ezguJlYUiw3Rw>
> Computer job
> <http://groups.yahoo.com/gads?t=ms&k=Computer+job&w1=Computer+software&w2=Co
> mputer+aided+design+software&w3=Computer+job&w4=Soa&w5=Service-oriented+arch
> itecture&c=5&s=121&.sig=S4rCT77z3xUeesYhvuqZ3g>   
> Soa
> <http://groups.yahoo.com/gads?t=ms&k=Soa&w1=Computer+software&w2=Computer+ai
> ded+design+software&w3=Computer+job&w4=Soa&w5=Service-oriented+architecture&
> c=5&s=121&.sig=XVYKxWnIx0EdfkBS6DaTLQ>   Service-oriented
> architecture
> <http://groups.yahoo.com/gads?t=ms&k=Service-oriented+architecture&w1=Comput
> er+software&w2=Computer+aided+design+software&w3=Computer+job&w4=Soa&w5=Serv
> ice-oriented+architecture&c=5&s=121&.sig=i-_f4IMs4JCXEMjxqUGGtA>   
>
>   _____  
>
> YAHOO! GROUPS LINKS
>
>
>
> *  Visit your group "service-orientated-architecture
> <http://groups.yahoo.com/group/service-orientated-architecture> " on the
> web.
>   
>
> *  To unsubscribe from this group, send an email to:
>  [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]
> Unsubscribe>
>   
>
> *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/> .
>
>
>
>   _____  
>
>
>
>
>
>
>  
> Yahoo! Groups Links
>
>
>
>  
>
>
>
>
>
>
>
>
>  
> Yahoo! Groups Links
>
> <*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/service-orientated-architecture/
>
> <*> To unsubscribe from this group, send an email to:
>     [EMAIL PROTECTED]
>
> <*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>  
>
>
>
>


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


YAHOO! GROUPS LINKS




Reply via email to