Welcome!

.NET Authors: Pat Romanski, Srinivasan Sundara Rajan, ChandraShekar Dattatreya, Jayaram Krishnaswamy, Jim Kaskade

Related Topics: .NET, SYS-CON MEDIA

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

@ThingsExpo Stories
An entirely new security model is needed for the Internet of Things, or is it? Can we save some old and tested controls for this new and different environment? In his session at @ThingsExpo, New York's at the Javits Center, Davi Ottenheimer, EMC Senior Director of Trust, reviewed hands-on lessons with IoT devices and reveal a new risk balance you might not expect. Davi Ottenheimer, EMC Senior Director of Trust, has more than nineteen years' experience managing global security operations and assessments, including a decade of leading incident response and digital forensics. He is co-author of t...
SYS-CON Events announced today that Gridstore™, the leader in hyper-converged infrastructure purpose-built to optimize Microsoft workloads, will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Gridstore™ is the leader in hyper-converged infrastructure purpose-built for Microsoft workloads and designed to accelerate applications in virtualized environments. Gridstore’s hyper-converged infrastructure is the industry’s first all flash version of HyperConverged Appliances that include both compute and storag...
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at @ThingsExpo, Robin Raymond, Chief Architect at Hookflash, will walk through the shifting landscape of traditional telephone and voice services ...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Architect for the Internet of Things and Intelligent Systems at Red Hat, described how to revolutioniz...
The 3rd International @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. The Internet of Things (IoT) is the most profound change in personal and enterprise IT since the creation of the Worldwide Web more than 20 years ago. All major researchers estimate there will be tens of billions devices - computers, smartphones, tablets, and sensors - connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades.
The Internet of Things will greatly expand the opportunities for data collection and new business models driven off of that data. In her session at @ThingsExpo, Esmeralda Swartz, CMO of MetraTech, discussed how for this to be effective you not only need to have infrastructure and operational models capable of utilizing this new phenomenon, but increasingly service providers will need to convince a skeptical public to participate. Get ready to show them the money!
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) i...
WebRTC defines no default signaling protocol, causing fragmentation between WebRTC silos. SIP and XMPP provide possibilities, but come with considerable complexity and are not designed for use in a web environment. In his session at @ThingsExpo, Matthew Hodgson, technical co-founder of the Matrix.org, discussed how Matrix is a new non-profit Open Source Project that defines both a new HTTP-based standard for VoIP & IM signaling and provides reference implementations.
The definition of IoT is not new, in fact it’s been around for over a decade. What has changed is the public's awareness that the technology we use on a daily basis has caught up on the vision of an always on, always connected world. If you look into the details of what comprises the IoT, you’ll see that it includes everything from cloud computing, Big Data analytics, “Things,” Web communication, applications, network, storage, etc. It is essentially including everything connected online from hardware to software, or as we like to say, it’s an Internet of many different things. The difference ...
DevOps Summit 2015 New York, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. 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 to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential.
The security devil is always in the details of the attack: the ones you've endured, the ones you prepare yourself to fend off, and the ones that, you fear, will catch you completely unaware and defenseless. The Internet of Things (IoT) is nothing if not an endless proliferation of details. It's the vision of a world in which continuous Internet connectivity and addressability is embedded into a growing range of human artifacts, into the natural world, and even into our smartphones, appliances, and physical persons. In the IoT vision, every new "thing" - sensor, actuator, data source, data con...
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
"There is a natural synchronization between the business models, the IoT is there to support ,” explained Brendan O'Brien, Co-founder and Chief Architect of Aria Systems, in this SYS-CON.tv interview at the 15th International Cloud Expo®, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
The Internet of Things promises to transform businesses (and lives), but navigating the business and technical path to success can be difficult to understand. In his session at @ThingsExpo, Sean Lorenz, Technical Product Manager for Xively at LogMeIn, demonstrated how to approach creating broadly successful connected customer solutions using real world business transformation studies including New England BioLabs and more.
There's Big Data, then there's really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at Big Data Expo®, Hannah Smalltree, Director at Treasure Data, discussed how IoT, Big Data and deployments are processing massive data volumes from wearables, utilities and other machines...