When businesses decide to go to the cloud for an enterprise application and open an account with Salesforce.com or some other SaaS (software as a service) provider, they typically don't consider how that SaaS app will integrate with their existing software.
SOA may have seemed the savior of bad software architecture and poor development project planning, but the reality is that it's a complex and difficult venture. Thus, the number of failed SOA projects is about equal to the successful ones. In other words, you have a 50 percent chance of failing, and the odds of failure are even greater if you work within a larger Global 2000 organization or within the government.
I've been getting a lot of e-mails about this...Those seeking general advice around SOA, and how to win. Here's my best shot at that.
Dana Gardner is for WOA, or Web Oriented Architecture, as mentioned in his most recent blog post. You can think of WOA as SOA meets the Web 2.0, but perhaps it's not that simple WOA may indeed lead to SOA, and evolve differently albeit using the same patterns. Let's get into this a bit.
With the advent of mashups, innovative developers all over the enterprise are seeking new ways to leverage the value of corporate information through the use of external Web applications, APIs, or services. Although the thought of this adventure has sent many corporate security specialists running behind their firewalls, mashups are here to stay. Indeed, they have strategic value for many enterprises, so you'd better figure out how to live with them.
SOA has been an enterprisewide rallying cry for the past few years, as companies have sought to unlock Web services' potential to augment the value of existing IT resources. Yet most activity around service-oriented architecture has been limited to discussion, study, planning, and small projects.