Athen
journeyman
Reged: 06/05/07
Posts: 79
Loc: San Francisco, CA
|
|
Do the six burning questions in this article cover it, or have we just scratched the surface of what burns (and matters) about SOA?
Edited by Athen (07/19/07 05:31 PM)
|
Unregistered
|
|
You forgot the biggest question: What is SOA? I recently attended the Serverside Symposium and this questions was asked to the a range of individual inclusive Martin Fowler. One thing that came out clearly was that the term SOA is a marketing term without any concrete meaning by itslef. Ingo http://goldentoolbox.blogspot.com/
|
Athen
journeyman
Reged: 06/05/07
Posts: 79
Loc: San Francisco, CA
|
|
I believe Martin Fowler summed up his thoughts on the topic of SOA two years ago with the phrase "service-oriented ambiguity." At that time he broke down the SOA implementation camps as follows:
- SOA is about exposing software through Web services.
- SOA implies an architecture where applications disappear, replaced by core services that supply business functionality and data.
- SOA is about allowing systems to communicate over a standard structure (at worst this means "CORBA with angle brackets").
- SOA is essentially EAI without the EAI vendors.
Any more (or more current) thoughts about how SOA is misconceived today? What are the most common mistakes when designing a service-oriented architecture?
|
Unregistered
|
|
Technically, I would add transaction managements as another big concern with SOA.
-Manjunath Krishnappa
|
Mohan Kumar
Unregistered
|
|
My take on the SOA is that SOA standalone delivers value only in slideware (ppt presentations) if it is not coupled with good governance, collaboration between Business and IT people, readyness of an organization to change, mechanism of easy consumption of the Services in Business Processes.
Although SOA vendors promote the approach of start small, learn, and scale later as SOA adoption methodology, I have my personal doubts about it. If SOA is not properly designed and its impact on the IT infrastructure and on the organizations as a whole is not thoroughly analysed, we will be creating more and more legacy to manage rather than creating an agile application infrastructure.
It is OK to start small if the future enhancements and improvement processes are in place before taking up an SOA project.
|
Unregistered
|
|
Given all of the ambiguity, I am waiting for SOAP to be renamed Service Oriented Architecture Protocol.
The ambiguity will then be complete.
|
jrockit2004
stranger
Reged: 08/09/07
Posts: 1
|
|
There are too many choices available for implementation and new framework pop up every 6 months. For e.g jboss-ws soon started focussing more on jax-ws. Axis2 is a revamped framework of axis.
Its just like doing it in high school and there is no such perfect way, but claiming it the right approach and adopting what so many people claim to be "right", if it fits the requirement.
The technology / framework is still real fluid.
Edited by jrockit2004 (08/09/07 12:13 PM)
|
Unregistered
|
|
SOA is a good way to architecture a solution but SOA has been the matra for companies like BEA and IBM to sell software which is nothing but re-packaging their existing software. SOA to me should be taught in school as Architecture principles. There has always been a hype in software industry to sell more software and SOA is this new vehicle until somthing else comes up. Just wait for the tide to settle.
|
SteveHB
Unregistered
|
|
I think that as long as the SOA thought leaders continue to pay no real attention to how to deal with COTS (Commercial off the Shelf package) integration into the SOA landscape then SOA will remain the playground of the E-Enabled business start-ups. Google (or of course your preferred engine) "SOA and COTS Integration" and see the ridiculously small amount of real information that is available on how to implement SOA when you have COTS packages that you simply cannot wrap or re-develop under SOA.
I have even seen examples where (LARGE) companies end up developing all of the functionality that they have in a COTS package again in their SOA environment.
|