With the India Times report on a huge technology induced crash with police searching lakes and canals for possible suicides by bankers and traders, it's natural to reflect on the cyclical boom-or-bust nature of technology trends.
SOA should be no exception. Where is SOA on Gartner's Hype Cycle? Phil Wainewright sees SOA at rock bottom. Tim Bray is already eulogizing SOA and talking about the emergence of something he calls Web Style. Loek Bakker says that SOA has been hijacked in a recent blog posting. Todd Biske calls SOA Battered and Bruised.
Interestingly enough, amidst all of the doom and gloom are some efforts to "reinvent SOA". Obviously it's in the best interest of some companies to reinvent SOA in their own image. Of course one of the great and terrible aspects of SOA is that it operates at an architectural level of abstraction. This allows for a lot of maneuvarability with respect to definitions.
Oracle, for example is already working on what they call SOA 2.0, an idea which they touted at the recent JavaOne conference in San Francisco. "SOA 2.0 is the term that we're using to talk about the combination of service-oriented architecture and event-driven architecture," said Steve Harris, vice president of Oracle Fusion middleware. This term was also picked up by Yefim Natis, distinguished analyst at Gartner who said that the difference between "SOA 2.0" and good old fashioned SOA is the inclusion of "Event-Driven Architecture".
Some of the tension can be found at the interface between lower level SOA concerns such as transactional SOA systems and systems focused on ERP and the more coarsely grained "agile" business service layer on top. Do we need a new name for SOA in this flexible new incarnation? Implementation strategies also represent the types of schisms that exist in many implementations. Document style or RPC style? REST or SOAP? AJAX or Smart Client? ESB or WS Fabric? Data centric or Process centric? EAI or Mashup? Centralized governance or distributed? Taxonomy or Folksonomy (tagging)? Schemas or Microformats? It's a long distance between COBOL based mainframe transactional applications and green screen scraping and social software, blogs and wikis.
Some of the naysayers are no doubt experiencing implementation pain. It turns out that while SOA pilots are easy and incremental, serious enterprise scale SOA requires planning, governance, organizational change, cultural change and real budgets.
SOA in total is also experiencing some degree of schism. While the blogorati and thought leadership are bemoaning the fate of SOA, industry watchers like Joe McKendrick suggest SOA may be on the Gartner slope of enlightenment. Real World SOA case studies are emerging. Organizations are realizing the connection between SOA maturity, SOA governance and business value.
The most significant data point is in the recent study by Merrill Lynch analyst Kash Rangan. The study found that of 76 CIO level executives surveyed, almost half expected IT spending to rise in 2006. Among these CIOs, Nearly all of them -- 87% -- said they believed developing a service-oriented architecture (SOA) to be the "next big thing" in enterprise software. So a very hopeful sign can be found simply by "following the money".
SOA should be no exception. Where is SOA on Gartner's Hype Cycle? Phil Wainewright sees SOA at rock bottom. Tim Bray is already eulogizing SOA and talking about the emergence of something he calls Web Style. Loek Bakker says that SOA has been hijacked in a recent blog posting. Todd Biske calls SOA Battered and Bruised.
Interestingly enough, amidst all of the doom and gloom are some efforts to "reinvent SOA". Obviously it's in the best interest of some companies to reinvent SOA in their own image. Of course one of the great and terrible aspects of SOA is that it operates at an architectural level of abstraction. This allows for a lot of maneuvarability with respect to definitions.
Oracle, for example is already working on what they call SOA 2.0, an idea which they touted at the recent JavaOne conference in San Francisco. "SOA 2.0 is the term that we're using to talk about the combination of service-oriented architecture and event-driven architecture," said Steve Harris, vice president of Oracle Fusion middleware. This term was also picked up by Yefim Natis, distinguished analyst at Gartner who said that the difference between "SOA 2.0" and good old fashioned SOA is the inclusion of "Event-Driven Architecture".
Some of the tension can be found at the interface between lower level SOA concerns such as transactional SOA systems and systems focused on ERP and the more coarsely grained "agile" business service layer on top. Do we need a new name for SOA in this flexible new incarnation? Implementation strategies also represent the types of schisms that exist in many implementations. Document style or RPC style? REST or SOAP? AJAX or Smart Client? ESB or WS Fabric? Data centric or Process centric? EAI or Mashup? Centralized governance or distributed? Taxonomy or Folksonomy (tagging)? Schemas or Microformats? It's a long distance between COBOL based mainframe transactional applications and green screen scraping and social software, blogs and wikis.
Some of the naysayers are no doubt experiencing implementation pain. It turns out that while SOA pilots are easy and incremental, serious enterprise scale SOA requires planning, governance, organizational change, cultural change and real budgets.
SOA in total is also experiencing some degree of schism. While the blogorati and thought leadership are bemoaning the fate of SOA, industry watchers like Joe McKendrick suggest SOA may be on the Gartner slope of enlightenment. Real World SOA case studies are emerging. Organizations are realizing the connection between SOA maturity, SOA governance and business value.
The most significant data point is in the recent study by Merrill Lynch analyst Kash Rangan. The study found that of 76 CIO level executives surveyed, almost half expected IT spending to rise in 2006. Among these CIOs, Nearly all of them -- 87% -- said they believed developing a service-oriented architecture (SOA) to be the "next big thing" in enterprise software. So a very hopeful sign can be found simply by "following the money".
