Blog: Why UDDI Sucks
- 07 October, 2008 14:49
- Comments
Last week I shared my interview with Eugene Ciurana, Leapfrog Enterprises' Director of Systems Infrastructure. One look at his photo will tell you Ciurana is not your typical suit. Ditto his approach to building a service-oriented architecture.
So I guess it should come as no surprise that some of the vendors with whom he associates are not cut from the pinstripe cloth, either. In fact, during the course of reporting his story, I took a briefing with Dave Rosenberg, the CEO at MuleSource, whose Mule ESB plays a key role in Leapfrog's SOA.
As we chatted about the various dimensions of the SOA universe, Rosenberg made a bold assertion. He barked, "UDDI sucks!" I was struck. Universal Description, Discovery, and Integration, the open OASIS standard designed to provide a platform-independent global Web service registry-the key to allowing SOAs the world over share and connect services over the Internet-sucks!
Rather than go off-topic and squander the remainder of our briefing time, I asked Rosenberg if he would mind sharing his reasoning (and by extension, MuleSource's) with CIO's readers in another column. He agreed.
Dave passed the job of articulating MuleSource's position to SOA architect Dan Diephouse, project lead for Mule RESTpack and SOA Governance platform Mule Galaxy. Dan is also creator of the Xfire project, and co-founder of Apache CXF.
MuleSource's position on UDDI follows. But this isn't the end of the story. With MuleSource's permission, I shared this piece with the folks at Microsoft. Microsoft is one of the driving forces behind UDDI, which first debuted in 2000 (it's currently at v.3.x).
Separately, you can read the Microsoft counterpoint.
Meanwhile, here's MuleSource's Dan Diephouse articulating why UDDI sucks. I've made minor grammatical edits, but these are Diephouse's words.
"The registry landscape needs to change. The unholy trinity of SOAP, WSDL and UDDI needs to go. While registry vendors, such as Systinet, have pioneered a number of good ideas in the field, they have failed to meet the needs of enterprise integration projects today, because they are based on these technologies. One should be able to guess this just by seeing the limited adoption, low success rate and high price tags of these solutions. Mass adoption is just not in the cards.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Bookmark this page
- Share this article
- Got more on this story? Email CIO
- Follow CIO on twitter
- Leapfrog Makes a Flying Leap Onto the SOA Pad
- MuleSource--Mule Enterprise Service Bus (ESB)
- Mule RESTpack - Mule Documentation Portal - Mule--Open Source ESB (Enterprise Service Bus) and Integration Platform
- Home - Galaxy - Mule--Open Source ESB (Enterprise Service Bus) and Integration Platform
- Codehaus XFire - Home
- OASIS - Committees - OASIS UDDI Specifications TC
- Blog: Why UDDI Rocks
- Simple Object Access Protocol (SOAP) 1.1
- Web Service Definition Language (WSDL)
- UDDI Version 3.0.2
-
FTC warns makers of background checking apps
-
Time to get Agile
-
QLD govt demands answers after pay glitch
-
Monash Uni reduces IT teams after consolidation project
-
iPad initiative for pupils in WA
-
Managing Private and Hybrid Clouds for Data Storage
Many organisations, driven by the opportunities for significant cost-savings, are considering cloud computing and cloud storage solutions, which take advantage of Web-based technologies to allow scalable, virtualized IT resources to be provided as a service over the network. Not a new technology in itself, cloud computing is a new business model wrapped around existing technologies, such as server virtualization, to make the use of information technology resources more efficient. -
Managing Trust - Data protection and compliance for financial services
If it’s becoming something of a cliché that the financial services industry is one of the world’s most heavily regulated, that’s largely because it’s true. Data retention and archiving, authentication and authorisation, data loss prevention and privacy regulations compete with demands for transparency and accountability, while market imperatives calling for multiple service channels delivered over a broad spread of technologies add to the pressure. Read on. -
Chapter 1: Threats and Challenges to Enterprise VoIP
The convergence of voice and data networks has been evolving and gaining momentum for several years. Organizations that are implementing Voice over IP (VoIP) in an effort to cut communications costs or leverage the competitive advantage of integrated services shouldn’t overlook the security risks that arise as voice and data converge.




















Comments
Post new comment