Welcome!

Microsoft Cloud Authors: Kevin Benedict, Pat Romanski, Liz McMillan, Lori MacVittie, Elizabeth White

Related Topics: Microsoft Cloud, SYS-CON MEDIA

Microsoft Cloud: Article

i-Technology Viewpoint: "SOA Sucks"

"I don't think that all of our problems will be solved if we move in this direction as an industry."

From time to time, I find myself lassoing a sacred cow in this Editorial space, dragging it over to the slaughterhouse of rhetoric, and ultimately barbecuing its falsehood over the stainless-steel, six-burner, propane-powered grill of real-world experience. To wit, the current industry obsession with SOA as a panacea for every information system ill from performance to security is, in my humble opinion, a phenomenal load of crap.

Now, please don't misunderstand me. I am not saying that there isn't a myriad of benefits to be derived from exposing systems' functionality for access by other automated systems simply by passing XML across industry-standard networking protocols such as HTTP and TCP. Web services are great! If you have to interoperate with non-Microsoft systems, they may be your only option. If you are building a system today and you suspect that some other system might want to tap into its functionality at some point in the future (hint: you can almost always safely assume that this will happen at some point), then you are wise to architect in a way that will lend itself to exposure via Web services.

What I do not buy into is the idea that all systems should be seen either as services that expose their functionality only via unidirectional XML messaging or as clients of such systems. Specifically, I don't think that all of our problems will be solved if we move in this direction as an industry, nor do I think that such an approach is without colossal problems of its own.

What problems have I seen at clients that have tried this? To begin with, the move to asynchronous system operations requires a massive change in thinking on the part of most developers. Having a separate Architect role on a team can offset a lot of this difficulty by allowing just one individual to orchestrate how a set of discrete, asynchronous services can be aggregated into various useful systems.

Versioning and reliability are two problems that are more tactical, and in some ways harder to resolve. If one considers the move from COM to .NET, for example, one of the major problems that .NET was intended to solve was the so-called "DLL Hell" versioning conflicts that were common in the days of COM. Many of these problems return with a vengeance when one begins to rely heavily upon external Web services, because a change in a Web service that is beneficial to one system may be quite detrimental to another system using that same Web service. Unlike .NET code that is run in process, there are no out-of-the-box standards and tools to help with the versioning of .NET Web services.

Finally, of course, are the eternal problems with all new technologies - unclear return on investment and quickly changing standards. These are the difficult questions that SOA must answer if it is to remain relevant in the computing environment of the early 21st century and beyond! As always, I welcome your feedback via e-mail to [email protected].

More Stories By Derek Ferguson

Derek Ferguson, founding editor and editor-in-chief of .Net Developer's Journal, is a noted technology expert and former Microsoft MVP.

Comments (10) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
jabailo 05/15/09 05:56:07 PM EDT

Wait...so you're criticsim of SOA is primarily that entrenched IT thinking and current locked mindsets can't comprehend it!

Simple answer: fire the laggards!

SOA is the right answer in so many ways.

However, the technology press doesn't get it because it's not proprietary, it doesn't have a single owner, you can't download it, you can't get a free t-shirt about it.

SOA is about good old fashion smart programming using the latest tools and technologies and eschewing all the Tinker-Toy "application servers" that have been foisted on us as the cure-all and yet sit there wasting server space.

I can build SOA with sendmail servers running on Debian messaging smtp.

I can build SOA with EJBs sending each other Jason strings.

I can use ticker files and the c# FileWatcher to notify automated execution of web services.

I can build a scheduling table on a database that organizes a set of tasks at destinations worldwide.

All of these things are SOA! And if you don't get it...you're SOL!

david 01/18/08 08:40:31 AM EST

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.

david 01/18/08 08:36:12 AM EST

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?

David deMilo 10/06/05 11:21:22 PM EDT

good article, dumb headline. Fire your editor.

Dan 10/06/05 02:30:34 PM EDT

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

Justin Fite 10/04/05 11:39:53 PM EDT

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...

George 09/30/05 06:20:12 PM EDT

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.

luke 09/28/05 02:46:29 PM EDT

I respectfully disagree as noted on my latest blog post.

George 09/27/05 05:54:18 AM EDT

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.

archie 09/27/05 03:38:40 AM EDT

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.

IoT & Smart Cities Stories
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
The current age of digital transformation means that IT organizations must adapt their toolset to cover all digital experiences, beyond just the end users’. Today’s businesses can no longer focus solely on the digital interactions they manage with employees or customers; they must now contend with non-traditional factors. Whether it's the power of brand to make or break a company, the need to monitor across all locations 24/7, or the ability to proactively resolve issues, companies must adapt to...
DXWorldEXPO LLC announced today that ICC-USA, a computer systems integrator and server manufacturing company focused on developing products and product appliances, will exhibit at the 22nd International CloudEXPO | DXWorldEXPO. DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City. ICC is a computer systems integrator and server manufacturing company focused on developing products and product appliances to meet a wide range of ...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
@DevOpsSummit at Cloud Expo, taking place November 12-13 in New York City, NY, is co-located with 22nd international CloudEXPO | first international DXWorldEXPO and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time t...
Founded in 2000, Chetu Inc. is a global provider of customized software development solutions and IT staff augmentation services for software technology providers. By providing clients with unparalleled niche technology expertise and industry experience, Chetu has become the premiere long-term, back-end software development partner for start-ups, SMBs, and Fortune 500 companies. Chetu is headquartered in Plantation, Florida, with thirteen offices throughout the U.S. and abroad.
DXWorldEXPO | CloudEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
Disruption, Innovation, Artificial Intelligence and Machine Learning, Leadership and Management hear these words all day every day... lofty goals but how do we make it real? Add to that, that simply put, people don't like change. But what if we could implement and utilize these enterprise tools in a fast and "Non-Disruptive" way, enabling us to glean insights about our business, identify and reduce exposure, risk and liability, and secure business continuity?