In case you need to catch up, Anne Thomas Manes of Burton Group declared that "SOA met its demise on January 1, 2009, when it was wiped out by the catastrophic impact of the economic recession!".
In her posting, she states –
Service-orientation is a prerequisite for rapid integration of data and business processes; it enables situational development models, such as mashups; and it’s the foundational architecture for SaaS and cloud computing. (Imagine shifting aspects of your application portfolio to the cloud without enabling integration between on-premise and off-premise applications.) Although the word "SOA" is dead, the requirement for service-oriented architecture is stronger than ever
I am happy to see that there’s renewed energy to try and find something new among some of my industry colleagues whom I respect. I’m not against finding a new name for this thing that we have been until-recently-referring-to-as-SOA but I still am looking for a reason why. Dave Linthicum claimed he predicted it would become less important, asked “Could the death of SOA bring it back to life?” , and purported that Anne Manes had simply signed and dated the certificate of death for it. Miko Matsumura and I had some fun with the whole thing, and the Yahoo!Groups service-orientated-architecture forum had a field day with it.
Jack Vaughan of SearchSOA.com recently posted an interesting case study of a SOA at National City Bank that succeeded, yet eventually failed because the credit crisis came along and a government-forced merger with PNC Financial Services Group took its toll. In Jack’s posting he asks
If one SOA succeeds is SOA still dead? What if it succeeds and fails?
One could stretch and say that that this is an example of being wiped out by the catastrophic impact of the economic recession. However I don’t think Anne had this case in mind when she wrote this. I’m sure there were a lot of casualties of that merger, and I don’t think the demise of the project had anything to do with whether it was SOA.
Joe McKendrick brought it up again in his 09 predictions saying that SOA will be de-emphasized by cloud computing. Nick Gall of Gartner Group used this as a way of promoting his pet peeve WOA with Long Live the Web, and as a bit of tongue-in-cheek retort, Steve Jones of CapGemini quickly proclaimed REST is dead long live the Web
I have been thinking hard over the past year or more to come up with new models for how service-orientation, grid computing, cloud computing, and SAAS all come together in a coherent architecture, but I have always thought we would just call it SOA.
So here’s my problem with all this noise …. I’m still looking for where’s the death!?? I’m not against joining the new bandwagon, but I’m still looking for a good reason to declare an acronym dead while still declaring everything that it stands for to be critical for future success.
Not a one has bothered to substantiate any of the claims that are made about SOA being unsuccessful. The consensus is that all the elements of SOA such as service-orientation, governance, alignment with the business, etc are still critical to live on, and be joined with things like cloud computing and SAAS yet the term itself needs to die because IT has to stop selling that term to the business. In favor of what? Another term? I’m all ears. In fact I would like to issue a challenge to the industry of those are in the thick of it to suggest a new term.
Just to let folks be aware that SOA, the architecture-formerly-known-as-SOA, and the architecture-until-recently-known-as-SOA is alive-and-well, I gathered up some success stories that show tangible ROI from recent SOA projects across the industry, which include some Oracle customers. If IT needs some ammunition to help sell SOA to the business, there's some right here -
I came across this set of case studies from the OMG SOA Consortium web site - which highlights SOA success stories across Insurance, Transportation, Government, Financial Services, and Healthcare.
Here are a few more from Oracle customers I culled from various sources –
Apollo Group, one of the leading providers of higher education for working adults, used SOA to automate determining the eligibility of their 120,000 student population for additional funds. The eligibility verification process was driven by many complex rules and required integration with heterogeneous systems such as PeopleSoft Campus Solution, Oracle e-Business Suite Financials and homegrown student record application. The rules that govern a student's eligibility for additional funds were volatile and needed to be quickly and easily modifiable by business users. Once a student is determined to be eligible for additional loan funds by the Oracle Rules Engine, multiple areas of PeopleSoft have to be populated to complete the Additional Funds process. The business logic in the PeopleSoft system had been highly customized so PeopleSoft Component Interfaces were utilized to gain reuse of all Apollo custom business logic. By reusing Component Interfaces, Apollo Group prevented the need to duplicate any business logic in the BPEL processes
The project took 4 months from start to finish with only 3 months to architect and develop the solution. The process was comprised of 12 BPEL sub processes containing over 450 BPEL activities. It interfaced with three different ERP systems to retrieve student information and inserted data into 12 PeopleSoft Components using Component Interfaces. Said Mark Forier, IT Director of Applications at Apollo Group.
Success of this project demonstrated the capabilities of IT and the Oracle Fusion Middleware stack to upper management and the business. We achieved a 600% ROI on this project with a four month time frame on a $300,000 investment. Essentially, a significant and immediate return.
Tucson Electric Power Company Unifies Business Processes with Oracle(r) Service-Oriented Architecture Suite
Tucson Electric Power Company expects to implement and integrate new applications 36 percent faster and reduce time spent on supporting and maintaining the system by 50 percent. They expect to implement and integrate new applications 36 percent faster and reduce time spent on supporting and maintaining the system by 50 percent.
Tucson Electric Power Company provides energy services in a regulated market and is focused on controlling costs while expanding IT services to increase business efficiency. The utility's IT infrastructure includes hundreds of specialized application interfaces and lacked a unified process for implementing new applications to deliver new services. To reduce IT complexity and administration requirements - and accelerate new application implementations - Tucson Electric Power Company selected Oracle SOA Suite to create a single enterprise-wide integration environment.
They are integrating their STORMS Work Management application with the Oracle E-Business Suite, which allows them to streamline work requests sent from STORMS to Oracle Projects and to track project costs more efficiently. The STORMS application enables the organization to rapidly assign field crews to restore electricity service and make repairs caused by storm damage.
Oracle SOA Suite (which enables underlying support for their service orientation) helps eliminate customized application integration requirements, establishing a framework of reusable components that allow Tucson Electric Power Company to simplify integration between additional work management applications and other back office systems - eliminating the requirement for custom, "hard wired" interfaces.
Capitol Corridor Joint Powers Authority Selects Oracle to Support Automated Ticket Validation Services Initiative
Capitol Corridor Joint Powers Authority (CCJPA), which manages an Amtrak intercity passenger train service in eight Northern California counties is using SOA as the foundation for its Automated Ticket Validation Services initiative.
Committed to continually improving customer service and security, CCJPA plans to launch California's first real-time ticket sales and validation system on its trains. The system, which is scheduled to go live in 2009, will allow CCJPA conductors to use hand held scanners to validate and sell tickets to customers on the train. This will also improve security by being able to track when passengers board and exit the train. The scanners will utilize Web and business process execution language (BPEL) based services to link CCJPA and Amtrak's IT systems.
Last but not least, is one of my favorites, Green ROI - It is widely believed that green revolution is the answer to the current downturn. How can SOA help you go green? Verizon Wireless did it using SOA, reducing their hardware footprint by 95% and measuring their ROI by reduction of tonnage of hardware in the datacenter. I blogged about this earlier in the year.
In summary, I’m not against joining the new bandwagon, but I’m still looking for a good reason to declare an acronym dead while still declaring everything that it stands for to be critical for future success. Help me out here.
Dave
