Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

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.

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.