Those of you familiar with SOA (service-oriented architecture) know that a registry/repository is the best way to expose and govern internally provisioned services. But, says Miko, a registry/repository can also be used to take externally procured cloud services and make them accessible via standard protocols across an organization, leveraging them beyond point solutions while maintaining control. Conversely, IT can use a registry/repository to expose its own native services to the cloud for B-to-B integration or even for a revenue-generating project or two.
CentraSite ActiveSOA, Software AG's new registry/repository, is the heart of the company's recent webMethods 8 release (IBM, Oracle, HP, SOA Software, and others offer their own as well). Miko claims that registry/repositories based on XML databases (like his and HP Systinet) are the most conducive to cloud-SOA synergy. In a sweet piece of irony, the Tamino XML database upon which the new ActiveSOA registry/repository is based derives from the first commercially available DBMS, ADABAS, developed in 1970 by Software AG.
So once again, a solution from the mainframe past vaults into the present like a "crashed UFO" (a favorite Miko phrase). If SOA never got off the ground in your organization, then a registry/repository may not help you. But if you're already on an SOA track, then some extra dev time to expose and govern cloud services may put you on the cutting edge of the biggest trend in IT -- and prevent you from being tagged as an obstacle to progress.