Paul Krill
Editor at Large

CTO Forum: BEA exec hails service-oriented architectures

news
Apr 1, 20034 mins

Web services, messaging play roles

BOSTON– Service-oriented architectures leveraging messaging and Web services are key to meeting complicated system integration needs, a BEA executive stressed during a keynote presentation at the InfoWorld CTO Forum conference here on Tuesday.

BEA’s Adam Bosworth, chief architect and senior vice president of advanced development at the San Jose, Calif.-based company, said enterprises are dealing with hundreds or even thousands of applications that have difficulty communicating with each other. “A very large number of applications have been built, and unfortunately, the people who built them are long gone,” Bosworth said.

Integration, he said, requires three phases: integrating the UI, integrating data, and integrating business processes. “This little problem, succinctly put, is you’re being asked to do three things simultaneously” that cannot be done, said Bosworth.

“We have to change the applications more rapidly, we can bring them down less and less and we have fewer developers to do it. This represents a bit of a challenge,” he added.

Standardization and flexible, service-oriented architectures are needed to address pressing integration issues, according to Bosworth. “The issue is, if you want an architecture that’s going to work, it has to work even when the implementation’s changing,” he said. He cited the Cullinet database as an example of a formerly industry-leading technology that faded away because it did not adapt to changing technology conditions.

He also cited instances of customers having problems using new technologies and moving 2,000 to 3,000 messages per second in their backbones and enterprises universally needing to run multiple OSes. “BEA has made a bet; the bet was that Web services are, if you will, the unlocking key for integration in the face of these realities,” Bosworth said.

BEA, he said, has devised three principles pertaining to application loads: coarse-grained computing is needed to provide for a single trip to a database for each transaction, loose coupling enables interlinked applications to be changed without breaking the architecture, and asynchronous communications provides for delivery.

“There’s a solution for this and it’s called messaging,” Bosworth said, adding that the idea behind Web services was messages could be sent with some degree of latency. “I have been surprised by how slow some companies have been to pick up on asynchrony as a core part of Web services,” said Bosworth.

BEA will invest in the area of message management and message brokering in an upcoming release of its platform, he said.

He cited the recently proposed WS-Addressing specification as containing a core model for asynchronous messaging. Web services provide a model for coarse-grained communications, he said, but the key behind Web services is loose coupling. Additionally, Web services offer at least a standard way of communications between applications.

Messaging, Bosworth said in an interview after his presentation, remains a clear part of BEA’s strategy. “The role there is very simple; it’s reliable delivery,” he said. Bosworth cited ongoing issues with needing a query mechanism for XML data. XSLT currently is being used to query XML but it is not suitable, according to Bosworth. He cited an upcoming version of XML Query as a potential solution.

Bosworth also said:

* SOAP technology “is going to freeze very quickly” after issues with asynchrony and reliable messaging are resolved.

* BPEL4WS (Business Process Execution Language for Web Services) is attempting to provide for descriptions of business processes and business contracts, but BEA is not certain it can handle the contracts task. “If it can do this, great. If not, we’ll have a white paper on it,” Bosworth said. However, Bosworth said BEA would not push the rival WSCI (Web Services Choreography Interface) model unless it is proven that the BPEL4WS model does not work. BEA has participated in development of both specifications.

* Instant messaging is important. “IM gives us a way to push messages and it gives us an architecture of knowing who’s available,” he said.

Paul Krill

Paul Krill is editor at large at InfoWorld. Paul has been covering computer technology as a news and feature reporter for more than 35 years, including 30 years at InfoWorld. He has specialized in coverage of software development tools and technologies since the 1990s, and he continues to lead InfoWorld’s news coverage of software development platforms including Java and .NET and programming languages including JavaScript, TypeScript, PHP, Python, Ruby, Rust, and Go. Long trusted as a reporter who prioritizes accuracy, integrity, and the best interests of readers, Paul is sought out by technology companies and industry organizations who want to reach InfoWorld’s audience of software developers and other information technology professionals. Paul has won a “Best Technology News Coverage” award from IDG.

More from this author