A lot of analysts I respect have been pushing the concept of Web-oriented architecture, or WOA, of late. For those unfamiliar with the term, Dion Hinchcliffe has covered it extensively and Dana Gardner has been singing its praises. To be honest, it looked like a term in search of a foundation to this observer. We’ve already got RIA and composite applications and mashups and Web 2.0 and SaaS and SOA, but I figured I should ask a few architects what they think of the concept to see if it’s got traction in those circles.
Granted, I only polled half a dozen people (though I’ll note here that they are half a dozen really smart people). The response I got from all of them is that WOA strikes them as redundant and nothing particularly new, an empty suit if you will. One wrote, “It reminds me a lot of the attempt by someone to gain some name recognition with the ‘SOA 2.0’ concept (which one vendor did try to use and then dropped after it was rejected by the SOA community).” Another responded, “It’s the same old thing, relabeled with an even MORE unwieldy name.”
Yet another noted, “This is just composite Web apps.”
Not a single one of them voiced a problem with the notion that Web-based development is an excellent place to concentrate your resources. In fact, some of the architects stated they are eagerly pursuing these sorts of development strategies.
That said, no one showed any love for the “WOA” acronym. “God forbid this take hold because it could complicate something the industry has been trying to simplify,” said one of the architects. He listed numerous reason why WOA, as a term, could do more harm than good:
- Users should have exactly one enterprise architecture, many don’t and they don’t need the confusion of “which architecture should I use?”
- WOA doesn’t really have an underlying architecture, it’s more a set of best practices around REST, RIA and composite apps.
- If users perceive WOA to be outside the principles of SOA, it could prove an excellent vehicle for building Web-based stovepipes.
- WOA toes and sometimes crosses the line of being technology driven. “We plan on using Google Apps, but Google Apps needs to fit into our structure, not the other way around.”
That last point about the potential technology driven nature of WOA was a point of contention for another architect. “One of the big problems we’ve had to fight is people who act as if SOA is tied to middleware or specific standards like SOAP or to a specific data format like XML. Nothing could be farther from the truth. Just because you’ve got some new technology to use doesn’t mean you go back to shoddy engineering. Everyone should know better than to let a specific hot technology drive the bus. It will cool off and you still need to be in business.”
Strikeiron CEO Dave Linthicum has also blogged about the upside of WOA. He pitched WOA as a potential gateway to SOA.
What is changing quickly is that enterprises are finding that the path of least resistance is in essence to build their SOAs on the Web, using Web resources, including content, internet delivered APIs, and Web services. Once there is success with WOA you’ll see the same patterns emerging behind the firewall, or SOA.
The polled architects viewed that as a perfectly legitimate approach, but one noted, “It’s still SOA. I just don’t see where WOA adds anything. Terms like this tend to make people in the field angry. In this case, it’s an attempt to sell them something they’ve already bought. I don’t know anyone who doesn’t want to use REST or build composite apps using Web tools.”
Time will tell whether WOA gains traction, but these architects expressed an unequivocal desire to have no more than one something-oriented architecture in their lives.
It’s amazing what happens you put a few thousand SOA users together. Suddenly you start to get a clearer picture of what service orientation can achieve at both the business and IT levels. That was probably the biggest takeaway for this attendee at IBM’s Impact 2008 conference last week: a lot of users are well down the road with this stuff. They’ve thought about it, put it into action and it’s responsible for a significant amount of mission critical business.
Here’s a smattering of comments made by SOA users at the show:
John Roach, director of architecture and governance at Wal-Mart, focused on using SOA to help manage store stock levels and customer demand. “If SOA doesn’t trace back to you finding the right thing when you walk into our store at the time you need it, then it isn’t material for us,” he said.
Kumar Murugan, application development manager at pharmaceutical manufacturer and marketer Novo Nordisk, talked about centralized policy management and stressed the need to view all SOA projects as part of a continuous process improvement cycle. He also highlighted the importance of having a rigorous QA process.
“You need to do a system discovery for any new service,” he said. “You need to understand how reuse affects your existing services.”
Manny Montejano, CTO at Cars.com, called governance “the key thing we need to resolve to be successful” as his company deals with explosive growth.
“It’s important to say no sometimes,” he said. “You have to let people know that some things are going to be more trouble than they’re worth.”
Anne McDiarmid, CIO for Australian fabric and crafts retailer Spotlight, made a case against trying to solve every problem with a software purchase.
“I’ve got middleware hanging out of my middleware,” she said. “I don’t need more middleware.”
A whirlwind of corporate acquisitions in foreign countries has created an integration challenge for SEB, a Swedish banking and insurance company. Enterprise architect Anders Jader targeted data as a key element in bringing together this international banking conglomerate.
“We are now in a phase where we need to transform everything into one data model and then be able to use that data as a service,” he said.
Tony John, domain lead architect at Allstate Insurance, echoed the importance of data in all things service-oriented, stating “we need more data analysts and data architects.” He noted that the bulk of a $30 million mainframe-to-SAP project “was spent on understanding the data.”
John also made the case that technologists have to understand the business they work for, not just how their niche of IT functions.
“No matter what machine or network it goes through, it’s still a group of people doing some business activity,” he said.
Things Kate Pierson surely never thought she’d say during a concert when the B-52s were taking off 30 years ago: “Happy birthday WebSphere!”
Now, THAT is what I call a mashup.
Artists who debut high on the Billboard charts plugging your products is also what happens when a company pulls off a big show, which is what IBM has done at Impact 2008. It’s easy to be cynical about these sorts of events. In fact, I’m paid to be cynical about pretty much everything. It’s a job requirement. Yet it’s impossible not to notice all the users in attendance and presenting in the sessions. Anyone who doubts whether SOA is happening at the corporate level only needs to spend an afternoon here and it will quickly prove that SOA is not only happening, but it’s happening in a big way.
After four days I’m starting to wonder if there’s a company that isn’t pursuing service-orientation. One interesting observation from a senior IT exec with whom I had lunch the other day was that a lot of his developers and IT ops people probably don’t even know the company is heading down the SOA path because the higher ups don’t use the term. The company just happened to build a loosely coupled, modular order-to-cash process. Only the folks with an enterprise architectural view tossed around the SOA acronym. Everyone else was working on an order-to-cash overhaul.
By the way, this is how SOA dies — not with obsolescence, but with ubiquity.
The event has also generated a ton of coverage. Dana Gardner has a great recap of the first day highlights in his BriefingsDirect blog. In it he’s got a killer quote from WebSphere GM Tom Rosamilia:
“You can do BPM without SOA, but I wouldn’t recommend it,” says Rosamilia.
I’ll note here that SearchSOA.com did a special report on this very topic two years ago. Business process management has always been a good idea, but without service orientation it’s largely unimplementable. How you compose those processes and manage them is critical.
In his OnStrategies Perspectives blog, Tony Baer recaps his conversation with IBM software head honcho Steve Mills about whether SOA is getting boring and then talks about the parallels between SOA and enterprise databases.
There’s yet another parallel between SOA and the evolution of databases. Twenty years ago, there were debates over whether SQL databases could handle the load and deliver the performance of legacy databases or file systems. The answer was throwing Moore’s law at the problem. Today, there are similar questions regarding SOA, because if Web services standards are used, that means a lot of fat, resource-hungry XML messages whizzing around. Mills’ answer is that there’s a glut of underutilized processing capacity out there and a crying need for virtualization to make that iron available for XML.
A lot of software-oriented folks tend to miss out on how much of a role hardware has to play in SOA. We’re talking about architecture here, not software. Hardware, networks, databases, storage — each one comprises a major component of the enterprise architecture. IBM’s talking about monster transaction volumes this week, the sort of thing you’d associate with TPF. So don’t be surprised if you’re in an app dev meeting in the future and you’re sitting next to the corporate mainframe guru and a data architect. Comfortably living within the artificial barriers created within IT shops is probably a luxury you won’t enjoy much longer. Those imaginary cubicle walls are coming down.
James Taylor has been a one-man Impact blogging machine this week over at Smart (enough) Systems. One entry covered a customer panel comprising Michelin, The Hartford, Health Care Services Corporation and the U.N.
Randy [Wallace from Michelin] discussed how far they had come from having a very small percentage of IT spend aligned with key business goals (6%) to one that is much more so (81%). For instance, in the past business units in different regions picked i2 and Manugistics at the same time and both were implemented resulting in separate systems. A stronger governance process and overall architecture are now established, driven by business ambitions and regularly updated. Far fewer and more focused projects as a result. Senior executive user satisfaction has risen steadily.
Here’s where I note Michelin sells tires. We’re not talking about a financial services company that stands to make a killing if it can combine information in new and dynamic ways or some Web business. These folks have a supply chain, logistics and customer care to manage and they’re finding value in SOA. This is why I really start to wonder who isn’t doing this stuff. It’s working in the tire business. The tire business!
Floyd Marinescu has a great summary of IBM’s “Smart SOA” vision up at InfoQ. In it, he lists five SOA best practices that IBM showed off a few times during the event.
- Linking business and IT from the beginning. Set the business vision first and see how IT can support it.
- Develop an architecture with a vision for the future. Not just one that will satisfy one process or one LOB, but something that can work over time.
- Skills and culture, governance.
- Scalabilty and process integrity – how do you plan for the spikes?
- Maintain end-to-end operational visibility
That’s a solid list. I’ll add one of my own, make the QA folks a central player in all of this. I don’t think I’ve spoken with one person over the past year who claimed to have a working SOA who didn’t tell me that service-oriented QA was essential. You’ve got to know what to test, what architectural principles need to be followed and whether your service can be expected to meet its service-level agreements. From everything I hear, it’s one thing to say that, but no mean feat to do it.
As such, it won’t surprise me overly much if at Impact 2009, IBM is pounding away on the theme of quality SOA.
And speaking of new themes, there was a presentation on “Green SOA” that I admittedly didn’t make, but there is a summary of the presentation up at Greenmonk Associates blog. The nut of the case made by RedMonk‘s James Governor for “Green SOA” is:
My argument at the event is basically that if SOA is a means to better alignment between IT and the business, then we should also drive sustainability into the mix. Componentising services gives you freedom to leave, for example, potentially allowing you to swap a provider out for a greener, or more importantly from a bottom line perspective, more energy efficient service.
Now that is what I call a forward-thinking take on the whole consumer-provider relationship. At the end of the day, that’s what SOA is: an arrangement between producers and consumers. People classically think about it in IT terms. IBM is pitching it in pure business terms, but the model can be extended beyond that. Choice is perhaps the greatest product of a truly decoupled world and, as Governor points out, profit isn’t the only choice on the menu.
At its Impact 2008 event, IBM today launched a REST-based development environment called WebSphere sMash, based on its open source Project Zero. sMash supports both the PHP and Groovy scripting languages, the latter was chosen in order to “attract the Java developers,” according to Jason McGee, IBM distinguished engineer and chief architect for WebSphere sMash.
It creates a serverside runtime for RESTful services. The browser-based development tools allow for REST-based components to be exposed via Ajax with the Dojo toolkit. McGee said the goal of the project had been to create a simple, intuitive component model for developers looking to create RESTful services. There is a developer guide, which goes into the nitty-gritty on runtime management, RSS/ATOM support, REST API documention, configuring data access and dozens of other topics.
Some good news for those looking to do more with REST development is that sMash won’t be a standalone REST offering inside the Big Blue product ocean.
“We look at REST enablement as a core capability across the IBM portfolio,” said Kareem Yusuf, director of product development for WebSphere sMash. WebSphere CTO Jerry Cuomo made the same vow, promising that REST support will be driven across IBM’s platforms, particularly on the SOA front.
“We’re systematically going through our product line and REST-enabling everything from MQ to CICS, DB2, WebSphere Application Server and on and on. This liberates these products and the content they represent to the Web,” Cuomo said. “With all that content dangling out on the Web, programmers can now agilely write new applications by interacting with those programs.”
Using sMASH coders can mashup content and then deploy it as a Web application, he explained. Mashups developed with the Project Zero technology also lend themselves to being hosted in a Software as a Service (SaaS) mode, Cuomo said.
“So Zero as a service is the next thing on the horizon,” he added.
The scripting language support should lower the barriers to entry for developers looking to try sMash.
“It’s not a new language people have to learn,” McGee said.
A limited community version will be available through the Project Zero website and the full version, with support, will be available on a license model.
For a developer level take, check out the TSS.com discussion of the sMash release.
Joining sMash in the Web 2.0 offering mix is a new product called IBM Mashup Center, designed for non-technical line of business users. It combines Lotus Mashups technology on the front end with the InfoSphere MashupHub on the back end. Larry Bowden, vice president of portals and Web interaction hubs at Lotus, said the product is designed to put mashup technology in the hands of knowledge workers, enabling them to pull information out of enterprise applications (like ERP and CRM) and combine that with market data and other 3rd party applications.
“The differentiator is we know where all that information is at,” Bowden said, noting that mashup development has become a hotbed for venture capital investment.
A visual wizard tool will allow users to create RESTful services and widgets without having to know specific programming languages.
The overwhelming theme coming from IBM on the opening day of its Impact 2008 event is that SOA isn’t about the technology. It sounds a bit odd to hear that message coming from a company with more SOA-related software and hardware products than anyone can count, but Big Blue deserves some message purity points for noting that SOA isn’t per se a technology initiative … even if it is more than willing to sell you a mother lode of technology in the pursuance of SOA.
Yet it also has some new technology to show off in front of the 6,000 attendees at the Las Vegas conference, which produced a standing room only crowd this morning at the MGM Grand Garden Arena. One of the highlights is a new business process management (BPM) suite. According to Tom Rosmilia, vice president for WebSphere software, the suite will be available during the second quarter of 2008. It will feature modeling, monitoring, process accelerators and asset repository capabilities.
The product itself comes from IBM’s January purchase of AptSoft Inc. and it will be called IBM WebSphere Business Events. True to its name, there’s lots of event-driven architecture under the covers. That fits into the second generation SOA vision pitched by senior pice president and group executive for IBM Software Group Steve Mills. Beyond event-driven services he stressed high performance transaction systems, low latency, integrity and scalability as the most in-demand functionality for an SOA growing in size and responsibility.
As with most of his comments during the day, Mills made sure not to offer any magic bullets. In particular, he noted that an ESB alone won’t net you a working SOA.
“The very nature of this is bringing multiple things together to make an environment work,” he said. That sort of business process unity marks IBM’s current efforts. Mills noted that goal comes on the heels of an endemic condition where IT shops “have effectively fragmented the ownership of information technology across the company.”
Rosamilia urged users to “take an iterative approach. Build it up over time and make it little bit better with each pass because you won’t get it right the first time.”
Tomorrow the company plans the commercial launch of its REST-based Project Zero initiative.
Last August I noted that Microsoft regularly finds itself buried under an avalanche of news coming from its Java-based competition. It’s impossible to compete with that kind of volume and that fact alone has caused the SOA market to gravitate toward Java and away from .NET.
Well, something similar is happening this year with open source vs. proprietary vendor in 2008, but, in what should be considered a bit of a stunner, it’s the open source folks who are creating the news deluge. It started innocently enough when Mulesource and WSO2 both released REST-based SOA registries. Then Red Hat released a modularized SOA platform in February. Now WSO2 and Mulesource are back with another major round of announcements. Based on its December Spring Integration release, you can expect SpringSource to become an increasingly visible player in the SOA market. Sun Microsystems will surely have some service-oriented dogs and ponies to show off at next month’s JavaOne conference and Eclipse, which has already debuted the Swordfish SOA runtime this year, will have a whole slate of SOA-enabled tools in its June Ganymede release.
The open source players are pounding away at the news cycle, throwing a steady stream of innovation into the mix. Obviously traditional app dev titans still dominate the market in terms of dollars and customers, but it’s about time somebody noted that we’ve got a movement on our hands. If you’re looking to build loosely coupled services, there are a host of open source vendors to choose from and that ecosystem is growing at an aggressive rate.
Change, particularly in an established market, doesn’t come in one big seismic event. It takes years of consistent pressure to remake this kind of landscape, but to be sure, we are in a period of volcanic activity for the open source market.
Defining your terms makes a world of difference when a project manager is modeling a business process, says Debra Berard, program manager for business excellence, Lean/Six Sigma at Seagate Technology LLC.
The bugaboo that also haunts data integration projects — you say “bill,” I say “invoice” — is something project managers need to solve in business process modeling for application development.
A recent example Berard offered was the design of Seagate’s failure analysis common tracking system (FACTS) application, which is used to find the root cause of failures in product design or manufacturing so they can quickly be corrected.
In a competitive business like disk drive manufacture the quicker a failure can be remedied, the quicker a new product gets to market.
To develop the FACTS application required WebEx meetings and conference calls with stakeholders from all the Seagate facilities involved including manufacturing sites in Thailand, China, Malaysia, and Singapore, as well as design centers in Oklahoma City, Minneapolis, and Singapore.
During these meetings, the project manager captured the processes that existed in the various locations using a business process modeling and analysis tool, the newly released Metastorm ProVision 6.1 enterprise modeling product.
The first thing the analyis revealed was the while Seagate’s goal was to have one failure analysis process, there were approximately 25 to 30 different processes in the company.
But after further review, that wasn’t as bad as it first looked.
“Come to find out, we did have a lot of processes,” Berard said. “but what was revealed was that they were really doing the same process, but calling the activities different names.”
So the issue was resolved in the conference calls by getting all the stakeholders around the world to agree to call the failure analysis activites by the same set of names, she said.
Once that was done a common model for FACTS was created, which then became the requirements document for the $5 million application development project.
Now, everybody involved in failure analysis at Seagate uses the same terminology as well as the same Web-based FACTS application.
Two interconnected debates are raging in the blogsphere over how service-oriented architecture (SOA) may be running into resistence in 2008.
One debate covered this week in a SearchSOA article is about whether SOA is reaching it’s goal of linking IT and business people, or is just becoming an IT-only initiative that is stalling out in most companies.
The other related debate concerns whether the R-word a.k.a “the current economic downturn” will hurt SOA adoption.
These questions were raised when Gordon Van Huizen, vice president of SOA at Progress Software Corp., called this week discussing how his company is putting all its SOA products under the umbrella of the Progress SOA Portfolio.
The portfolio offers a broader SOA marketing message by covering all the Progress products for:
· Enterprise service bus (ESB)
· Business process management (BPM)
· Complex Event Processing (CEP)
· SOA management
· Data interoperability
· Mainframe integration
From a sales and marketing perspective this seems like a good approach. But Van Huizen was asked about the larger marketing challenge posed by current economic conditions.
Does Progress have a strategy for coping with hard times?
“We have this built-in strategy at Progress that is relatively unique,” Van Huizen said.
He noted that his company’s Open Edge development platform is sold through an ISV channel that has been in place for a long time. The 1,500 ISVs target “very specific, narrowly defined segments of vertical industries.”
By throwing the net so wide, the ISVs reach customers in a variety of industries, not all of which are hurting in this economy, he explained.
“So if there’s a slow down in financial services we don’t feel it so much in that product line,” Van Huizen said. This is also true of the SOA products, he added.
“Our orientation to the market was initally around financial services and telco, perhaps because of the messaging orientation of Sonic MQ,” he said. “But with the SOA management product, with Actional, there’s been opportunities to branch well beyond that.”
The Progress SOA Management product is penetrating into healthcare and higher education, two areas generally considered recession proof, he noted.
“As one part of the market goes down others remain somewhat boyant,” Van Huizen said. “So if there’s an offsetting strategy I believe we have one. Of course, if everything tanks, we’re all in trouble for awhile, and that’s just the way it goes.”
As for the other related debate about how to keep SOA from stalling out even in companies that have the budget to do it, Van Huizen suggested two strategies.
The first one is to reach across from IT to business people by explaining SOA not in terms of technology with acronyms, but through business case studies that show the dollars and sense success of the approach.
The second is to begin SOA projects at a tactical level, even as simple as application integration, sometimes called EAI 2.0. This allows IT to show the business managers and executives the advantages of SOA without asking them to shell out big bucks for a massive implementation.
These two approaches are also echoed in a recent blog by analyst Joe McKendrick, who quotes fellow analyst Tony Baer’s view that this will be a year of lower expectations for SOA.
“Recessions tend to discourage the kind of long-term thinking that grand enterprise architectural exercises are supposed to support,” Baer said. “In that sense, SOA has been caught up in the middle – roughly six years after the current incarnation of the concept emerged with Web services, there remains considerable debate as to whether it makes sense to take a project or architectural approach.”
However, McKendrick makes the interesting point: “It’s worth noting that the case for SOA, in tandem with Web services, was forged during the worst IT spending slump in a generation – the 2000-2002 time period. Companies and IT professionals were attracted to the SOA/Web services concepts because they offered the attractive advantage of building or exposing existing applications at minimal cost and disruption.”
This podcast with Mulesource CEO Dave Rosenberg covers the role of the enterprise service bus (ESB) inside an SOA. Rosenberg notes that an ESB shouldn’t be thought of as a singular piece of software sitting in the middle of every application, tossing aside the hub-and-spoke model from the EAI world that often gets grafted onto SOA. He stresses that SOA “is not about integration,” but rather a sensible infrastructure that can handle modular development and changing business needs.
Other topics covered in this interview include:
- How users are more likely to have an “enterprise service network” with multiple ESBs rather than a single or master ESB
- The role of open source in SOA development
- Why neither the Java EE nor .NET meets are well-suited to service orientation
- The roadmap for the Mulesource, particularly in the management area
- What constitutes “SOA infrastructure”
- Data issues, including getting data out of 3rd party SaaS applications
Oracle has standardized on a JavaServer Faces (JSF)-based RenderKit, which allows the developer who has learned JSF to assemble disparate components into a Web 2.0-style mashup.
Enterprise customers are looking for ways to avoid getting caught up in such complexities, so the philosophy behind the tools Oracle has in beta is to automate the rendering technologies, so developers only need to work with components and pages, he said. This approach also is designed to insulate developers from the on-going changes in underlying technologies for RIA, he said.
“As technologies change, we can change our framework but they don’t have to change their pages,” Farrell said.
He describes the Oracle RIA tools as “very WYSIWYG.” The developer designates that a page will be Ajax with Flash from Adobe Systems Inc., Farrell said, and that is all the coder needs to know about those technologies.
Farrell said the Oracle RIA tools are in an advanced beta stage prior to the official release. Interested developers can find out more information and even download them from the Oracle Technology Network.