Predicting the future of SOA

"SOA is a good practice for software design. Although it is not an answer to all problems, SOA isuseful and should be part of most modern software projects. Over time, lack of SOA will becomea competitive disadvantage for most enterprises. Mainstream enterprises should invest today inunderstanding SOA and building SOA design and development skills." "The Best Use of SOA Is for New, Multichannel and Composite Real-Time Applications" "Ironically, Users Who Best Understand Event-Driven Architecture Will Be the Best Users of SOA" "A large part of the integration problem requires implementation of long-running offline businessprocesses. Here, event-driven architecture (EDA), not SOA, is the industry best practice. UnlikeSOA, EDA is the design vision for long-running asynchronous processes (SOA is best applied toreal-time request/reply exchanges). In EDA, a process node posts an event (in SOA, a processnode makes a targeted processing request). In EDA, posting an event reflects results of somepast processing (in SOA, making a processing request directs future processing). In EDA, theposter of the event is disconnected from the processors of the event, if any (in SOA, therequestor of service knows the service and depends on its existence and availability)." "The Main Benefit of SOA Is the Opportunity for Incremental Development, Deployment,Maintenance and Extension of Business Applications" "Through 2007, growing enterprise experience with SOA process and SOA-based applications willeliminate the myths and instill appreciation for the real benefits of SOA in most enterprises.Evolving tools, skills and best practices will make development of SOA-style applications easierthan development of monolithic applications. This change will shift the massive software industrymainstream into the new software-engineering reality: By 2008, SOA will be a prevailing softwareengineeringpractice, ending the 40-year domination of monolithic software architecture (0.7probability). "Prevailing," however, does not translate to "exclusive." Through 2008, mostenterprises will combine elements of SOA, EDA and monolithic architecture in their enterprisesoftware development projects (0.8 probability)." Referência: Yefim V. NATIS, Service-Oriented Architecture Scenario. Gartner Research, 16 April 2003. Disponível em: http://www.g2r.com/resources/114300/114358/114358.pdf