Ø Saying that SOA is not bound to a technology makes no sense
Ahhh. Terminology.
SOA, the conceptual model, is not bound to a technology. Java, C#, COBOL, HTTP, DECnet, CORBA, and other technologies can all be used to express an SOA design.
SOA, *an implementation*, is very much bound to a technology (it’s code, after all). This is the case where the particular middleware and architectural tools used for the implementation can affect how you express an SOA design, including potential constraints and aids. Not all tools do all things well; some will be better at some aspects than others.
But specific technology only enters the picture when you talk about an implementation.
The ideas and style (the ‘flavor’ if you will) of SOA designs can very well be technology agnostic, it’s only as you sink down towards a concrete implementation that all the real world details start to color the design.
This is why many people at first may say CICS/COBOL systems are not SOA, but as you peel back the superficialities and devil-in-the-details caveats, the broader designs can become more obvious.
Not to say all ‘old’ apps are SOA, hell I’ve seen Java code that was about as far from OO as you could imagine (which is a neat trick considering the language jams it in your face at every level starting at day 1). Just that SOA, the architectural concept, is a new term for something that’s been in practice for a very long time. It’s just more commonly recognized nowadays, and there’s more and better tooling to facilitate it.
- Howard
"Your training is nothing! The will is everything! The will to act."
__._,_.___
| Computer software program | Computer software spy | Computer job |
| Database software | Discount computer software |
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.
__,_._,___
