Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
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.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, 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 or appropriate markings.