One of the most immediate business benefits that can come out of Web services and SOA is that of reuse. Namely, companies or their developers shouldn't have to reinvent the wheel every time they need to build or integrate a new application.
Service technology -- from SOA to cloud to IT service management -- promises many "-ilities": greater agility, flexibility, and reusability. Joe McKendrick explores the challenges and opportunities with service orientation, and how to capitalize on these emerging computing philosophies.
Joe McKendrick is an author, consultant and speaker specializing in trends and developments shaping the technology industry.
Just to amplify Joe's previous post on BEA's open source strategy, let me offer a Wal-Mart analogy. That may sound strange but bear with me.
Since Web services is based on open, accessible, and (allegedly) universally accepted standards, you'd think there would be more interplay between the Web services and open-source communities. But it hasn't really turned out that way yet.
Bill Gates remains a big believer in the power and potential of Web services. He contends that standards will generate a "more model-based approach to developing applications.
A group calling itself the Integration Consortium predicts that service-oriented architecture development will be the "in" thing for 2005. However, vendors will be duking it out over Enterprise Service Buses.
Loosely Coupled's Phil Wainewright weighs in on Enterprise Service Bus in a recent post: "I doubt many people will be talking about ESB in a year or two," he writes, citing Blue Titan's recent launch of a fairly comprehensive Web services-based messaging infrastructure as a harbinger of things to come. Why introduce a messaging system from anywhere else if an ESB is already in place?
Some more food for thought about the economics of business process outsourcing: A report just out of Datamonitor argues that speech-enabled self-service technology may be a better value proposition than using offshore call center agents for low-level transactions. The report estimates that a company can save 25% to 35% per transaction using speech-enabled self-service solutions versus using a call center in an offshore location.
Speaking of the critical role of the registry in SOA (see my previous post on UDDI, below), Infavio's Jeff Tonkel also beats the drum for registry in his latest blogs. Tonkel observes that there is no single corporate registry tostore information on SOA end points and govern theirrelationships and runtime interactions.
Can Big Blue succeed in BPO? The latest edition of KnowledgeWharton, published by the University of Penn's Wharton School, reports that IBM continues to shift away from platforms to services, with nearly half of its $89 billion revenue from last year coming from services.
UDDI, or the Universal Description, Discovery and Integration protocol, got a bad rap a couple of years back when the dot-coms dot-bombed. UDDI is considered one of the four basic Web services standards (along with XML, SOAP, and WSDL), but was closely associated with e-commerce, intended to serve as the "yellow pages" for linking providers and consumers of Web services.