Eric Jan Malotaux presents a way of implementing SOA in small iterative steps, each step delivering value to stakeholders, higher than the costs involved, using feedback from previous steps to adjust the requirements and design accordingly.
Brian Nicks presents a study case of a healthcare company which inherited many disparate technologies from Java on WebLogic to .Net to RPG on iSeries to CICS on zSeries to COBOL on OpenVMS, deciding that the integration solution was to implement a SOA initiative. The presentation contains the challenges, the successes and the lessons learned throughout the process.
Paul Mooney attempts to clear up some of the misunderstandings surrounding SOA considering the fact that many implementations are labeled as “SOA” but are not. He does that by describing an SOA journey from establishing a route (characteristics, goals, benefits), planning it (service inventory), making it (service design) and arriving at the destination (measuring success, governance).
Anne Thomas Manes, who pronounced SOA dead a year ago, talks about the reincarnation of SOA. She believes the old SOA had to die because it was too much focused on technology and products, while the new one, absolutely necessary for the new cloud computing era, will be focused on architecture, principles and practices.
Ian Robinson on what organizational and social issues should be addressed when starting a new SOA project by identifying business capabilities using user stories, describing services and their contracts, and how to set up teams for delivery.
This presentation discusses specific SOA properties that might result in major problems and concrete ways to solve such problems including appropriate decoupling, appropriate processes for dealing with life-cycles and heterogeneous repositories, and pragmatic solutions for interoperability, reliability, and security.
Video of SOA Foundations course captured at webMethods SOA Master Class in San Francisco. Speaker Miko Matsumura covers foundational definitions and patterns for SOA.