When SOA standards attack



Email    print   
July 15, 2008 —  (Page 1 of 2)

What happened to all the talk about SOA standards? You know, the whole WS* thing, and the 100-plus standards that everyone followed? Yes, I said “followed,” as in past tense.

Truth be told, SOA standards have a diminishing value, much like anything that floods the market. There were just too many standards to track, and many of them were redundant and not sincere. The fact of the matter is that interest in standards continues to fall off, and those who placed major bets on standards are starting to feel the stress.

The trouble came about when the creation of SOA standards moved from R&D to marketing. In essence, SOA technology companies found that it was a good way to sell technology. For instance, you create a standard that you drive, then create technology around that standard. After that, point to the fact that you are based on a “standard,” the one you created. It’s kind of silly when you think about it, almost like defining the ideal body type, which just happens to be your own body.

Thus, with standards driven by marketing and leveraged as a way to sell technology, the SOA technology vendors gave birth to over 100 SOA standards within several standards bodies. Typically, not much is behind most of these standards, and usually only one company may drive a standard, with few exceptions.

The problem with this approach is that those who consume SOA technology and want to leverage standards are, in many cases, left holding the bag as both the standard and the technology that support it become irrelevant. Thus, what you thought was a transactional service standard that insures portability turns out to be a standard that defines just one product, not a group of products. Therefore, the standard really brings no value to the table.

Even more popular standards such as BPEL are going through some rough times these days. In some instances, BPEL may be a good fit, but in most instances, SOA projects are opting for other types of service-binding technology (composites, workflow, etc.). Thus, if you invest in BPEL, there could be a day when that standard is replaced by something better and the code is quickly considered legacy. Moreover, with BPEL, as with many standards, the vendors have placed proprietary extensions into the technology to circumvent some of the limitations of the existing standard, and thus by leveraging those proprietary extensions, you (in essence) lock yourself into that vendor, and you might as well not leverage a standard at all.



Related Search Term(s): SOA & SaaS

Pages 1 2 


Share this link: http://sdt.bz/32416
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
SOA Software releases project-planning suite for SOA transition
Portfolio Manager provides a framework for SOA planning, helping developers prioritize services, understand dependencies, and plan architecture and governance processes, the company says. The product is marketed as being essential for creating road maps for transitioning to SOA Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb