Over the past year, meanwhile, you've upgraded packaged applications, implemented new applications and deployed those developed by your IT staff. Most of those applications, if not all, have a Web services interface or two that facilitate communications with other applications. But these services aren't managed and, in some cases, you might not even know they're ready for access.
You need a repository--one that will help you gain control of rogue services and enable the reuse of services throughout the enterprise. Without a repository for your SOA infrastructure, you cannot catalog or reuse your services. Yes, I'm talking about the UDDI registry. This incarnation of the registry has more bite than a double-shot of hard whiskey. It's geared toward governance, being able to control and manage available services and, ideally, enabling run-time binding that eventually results in business-user-developed, composite applications running on an enterprise SOA.
But reaching this SOA nirvana won't happen in 2006. The major goal of a repository implementation in 2006 will be simply to get a handle on services and manage them from a business viewpoint (what business function does it provide?) and for IT-specific information (what version is it, who can use it?).
The repository also will see wider use of BPM implementations as processes increasingly are defined using service-oriented products from Infravaio, SOA Software, Systinet and others. These vendors will continue to forge relationships with ESP (enterprise solutions platform) vendors like BEA, IBM and Oracle. But Systinet and other service-oriented vendors will get pulled into the enterprise mostly because of their repository products, which, like your SOA, continue to mature and become more useful. More ambitious, composite-application initiatives will emerge in 2007 and beyond. Without the repository, your future SOA won't engender reuse or let services align with business needs.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
Maintaining existing network infrastructures often incurs huge technical debt before newer technologies are adopted over time.
Amid ongoing regional uncertainties, telecom infrastructure in the Middle East has expand to include terrestrial low-latency network infrastructure, which offers resilience and agility in navigating political complexities without relying solely on undersea networks.
