Title
The future of SOA: what worked, what didn't, and where is it going from here?
Abstract
The past few years Service Oriented Architecture (SOA) has risen from being a concept promoted by few to become one of the most important architecture styles enterprises are trying to adopt. Though many of the bases upon which SOA is founded are not new, its link to achieving business results makes it very appealing. However, as with any new and promising concept, a great deal of hype is associated with SOA, which could spell trouble for both its promoters and those committed to its adoption. Today there are no shortage of claims from both believers and doubters of its benefits. There are many challenges facing its early adopters as well as missing capabilities needed to support all business needs. The next few years are critical to the success of SOA. To silence its doubters and live up to its high expectations, SOA must evolve and extend to incorporate features from other emerging paradigms, techniques, and architectures. This panel will address the challenges facing enterprises in their attempts to adopt SOA and realize its full benefits, and will shed some light on the future of SOA. The panelists will be asked to address the following questions: 1) Is SOA a revolution which requires a paradigm shift (similar to OO for example)? Or is it an evolution? And what are the challenges? 2) What aspects of current SOAs work well? What evidence do we have? Do we have specific quantified cases showing the business benefits for an enterprise as a result of adopting SOA? 3) What didn't work? (For example, high overhead, performance, methodology, etc.) 4) What does the future hold for SOA? And what are the priorities? (For example, should SOA adopt a light-weight approach similar to Web 2.0, or focus on building Composite Services? How would SOA address 'user needs' Should future SOA enhancements focus on incorporating Event Driven Architecture? Or on providing Hardware as a Service (HaaS)? 5) How do we support larger transaction action based services that can be composed of many smaller autonomous services?..
Year
DOI
Venue
2007
10.1145/1297846.1297975
OOPSLA Companion
Keywords
Field
DocType
promising concept,complexity,years service oriented architecture,high overhead,web 2.0,business benefit,future hold,business result,business need,soa,future soa enhancement,event driven architecture,high expectation,service oriented architecture,web 2 0,paradigm shift
Event-driven architecture,Architecture,Programming language,Paradigm shift,Computer science,Knowledge management,Web 2.0,OASIS SOA Reference Model,Database transaction,Service-oriented architecture,Process management,Early adopter
Conference
Citations 
PageRank 
References 
6
0.63
1
Authors
6
Name
Order
Citations
PageRank
Mamdouh H. Ibrhaim160.63
Kerrie Holley2242.54
Nicolai M. Josuttis361.31
Brenda Michelson460.63
Dave Thomas5193.75
John deVadoss660.63