face it without XML SOA wouldn't exist, and quite frankly XML sucks anyway -- ever look at all the documents that need to exist and be generated?

the XML community is on crack -- and the technology is out of control.

why is the JRE backward compatible, but with MS you need every .NET framework to make sure everything is "interoperable"?

why should folks use an inferior model like MS .NET?

good article, dumb headline. Fire your editor.

First off I think it is interesting that you are smoking a technology that the very magazine you are writing for depends on. A bit amusing to me actually.

Second, although your article doesn't cause me major objection around web services. I do object to the continued misunderstanding of what SOA is trying to accomplish both in the vendor world as well as the business world. Everyone equates Web services as a 1-1 mapping to SOA, while most implementations end up this way it isn't the intent of the panacea as you stated in your article.

The intent of SOA is to start thinking of your business process and how all your systems are supporting those process whether they are distributed or not. A service doesn't necessarily mean that it is remote from the application or even a webservice. I can imagine within a batch process you have an NDM service that will provide a part of your business process.

The true intent and the best way to look at SOA is that it is an IT methodology shift from a silos of departments working on everything that every other department is working on to a specialized view of fulfilling an over all business function or infrastructure function which is needed from a holistic business architecture.

Now of course your point is about the clients you have worked with, which is why your article is skewed in the first right probably since you don't seem to have any meat on what SOA seems to accomplish from your standpoint.

I don't see SOA as an end all solution but it does help to establish a new way of thinking for business and IT which in the long-term will help to feed a more efficient organization if done right.

Thank you for your time in reading this feedback.

- Dan

As with all "new" technologies, the good is over-hyped and the bad is conveniently underestimated. Derek you mentioned reliability problems, but did not elaborate. The act of creating functionality by linking together independant services will give business what they need: increase business flexibility, but with nasty side effects of unpredictability (thus hard to plan and support), much higher reliability risk (a giant AND condition of every service you request), and the urge for every business to convert many batch processes to dynamic processes. All of this will cause more complexity, higher infrastructure costs, and lower overall reliability. All because we continue to push all our execution through limited, expensive compute resources. The web has taught us the economics of deploying software to end users (scale out), yet we still execute our core business like we did decades ago (scale up), causing a choke point. Virtualize the application and the server so every service gets "it's own machine, it's own instance of the application" This would eliminate compute constraints...

On the second thought, you're right again. Not only SOA sucks. There are many things that Sun Microsystems has not bothered to fix for years.
Example: int java.sql.ResultSetMetaData.getColumnType(int)

Software engineering is not an exact science yet.

I respectfully disagree as noted on my latest blog post.

You're right: Each made by Microsoft including 'DLL Hell' and many other is a phenomenal load of crap. Switch to Linux and forget MSFT.

Well, we all know that SOA is still an infant, it cries a lot and does poo-poo all over the place, nevertheless it does show some potential. If you treat it as if it were an adult, you are very naive and in deep trouble.

The whole industry is behind this because for the first time in history, Microsoft has agreed to sort of cooperate with it's competitors in creating a framework for the future. They have actually agreed to compete without reserving for themselves the role of rule-maker, referee and lead player. They are *only* the 800lb gorilla in the playground. The only way this would work is if the technology itself is immature and over-hyped.

The funniest part of the article is the claim that WS is the only way of accessing non-Microsoft systems. WOW! Unix has supported all the distributed computing paradigms that have been invented by mankind in the last 30 years and these are myriad. There main weakness was that none of them were accepted by Microsoft. What SOA offers is exactly the opposite: the only way to include Microsoft systems in distributed computing scenarios and this is the main reason for our unreasoning support.