Manas and Clemens discuss deriving business agility from SOA and BPM, how SOA and BPM enable agility, and pitfalls/recommendations for organizational culture, business and technical architectures.
Hajo Normann on modeling human interaction, improving BPM models, orchestrating composed services, central task management, business-IT alignment, non-deterministic processes, and choreography.
Bill Burke shows how to use REST to create interfaces to middleware services – messaging, transactions, workflow, security – in order to have RESTful enterprise SOA implementations.
Cesare Pautasso proves that BPM can be used to compose and implement REST web services, showing the relationship between business processes and stateful resources accessed through a RESTful API.
Russ Miles and Toby Hobson outline many factors to be considered when adopting a cloud solution, creating a wider view of the cloud from the development and business perspective.
Next Generation of Business-Driven SOA: The Convergence of Performance-Driven Business and Service-Orientation
John DesJardins believes that the new SOA will measure their businesses alignment with IT in order to asses the impact of services or of changes or new initiatives, up-time, response time, etc.
Anne Thomas Manes talks about SOA's reincarnation. Old SOA had to die because it was focused on technology and products, while the new one will be focused on architecture, principles and practices.
Paul Downey covers the risks of premature standardisation, partial implementations and open extensions, cloud computing lock-in, and formal activities vs lightweight open processes like open source.
Ian Robinson on issues to be addressed when starting a new SOA project by identifying business capabilities using user stories, describing services and contracts, and setting up teams for delivery.
Kirk will present the advantages of a RESTful architecture to develop integrated systems in the financial services arena; leveraging infrastructure, skills, and systems already in place.
Our application runs over 10,000 sustained transactions per second with a rich model. The key? Modeling state transitions explicitly.
Jim Webber explains the core concepts of message-oriented and resource-oriented web services, expresses his thorough dislike of WSDL, and shows an example of a RESTful workflow.