To make your SOA a success, you must control these services. Many of your application projects in the next year will be geared toward governance of your organization's myriad business services--which look suspiciously like Web services (probably because beneath the covers, most are).
Many are watching SOA with suspicion. After all, we've heard that this type of architecture would save the world before--why would SOA succeed where others, such as CORBA (Common Object Request Broker Architecture), have failed? It's all about the "B" for business. The movers and shakers of the SOA world know that it's the bottom of the ninth, there are two outs, and the count is full in this architectural game. Because SOA focuses much attention on business process, with a language that is moving to accommodate the business analyst as well as the IT architect, there's a lot more synergy between the business and IT, and a lot more common ground.
That's something we haven't seen before--a single language that makes sense to tech and non-tech alike. Having learned from the failures of CORBA and RMI, SOA is better positioned to save the game than the technology that came before it.
Conventional integration technologies are evolving and are quickly being replaced with ESB software. ESBs provide integration plus the capabilities of legacy EAI products, and features and functions that integrate both legacy and contemporary services, such as Web services. And ESBs are gaining momentum in the enterprise. In fact, more than half of all large organizations will have an ESB running by year-end 2006, according to Gartner.
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
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.
