Automate your infrastructure to build, deploy, manage, and secure applications in modern cloud, hybrid, and on-premises environments.
Posted by Dan Foody
I recently had a discussion with one of the key industry analysts covering the SOA governance space. He said that the need for UDDI is going away – to be clear, registries and repositories are very important, but the UDDI technical standard is no longer a key driver.
UDDI had promised to be the universal standard for communicating with registries, and there were no real competing standards. So, what’s led UDDI to be on its deathbed? A few things, I think:
This is a long time coming but welcome news for anyone that’s ever had the “pleasure” of using UDDI. On the other hand, if you’re a UDDI vendor, take a big breath and remember the 5 stages you’ll go through: Denial, anger, bargaining, depression, and acceptance.
No doubt this does leave a gap – we have no widely adopted standard for integrating with or federating registries and (more importantly) repositories. Hopefully all the registry/repository vendors will get together and fill the gap soon – preferably with something that’s simple and useful. The status quo (with or without UDDI) where every SOA infrastructure product must custom-integrate with every registry/repository product just can’t be sustained.
Rest in peace UDDI. Just do it quickly, please.
View all posts from dan foody on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You have the right to request deletion of your Personal Information at any time.
You can also ask us not to pass your Personal Information to third parties here: Do Not Sell My Info
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.
Copyright © 2021 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.