This presentation attempts to clear up some of the misunderstandings surrounding SOA considering the fact that many implementations are labeled as “SOA” but are not. It 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).
http://www.infoq.com/presentations/SOA-Solution-Evaluation-Criteria

Jason Hogg makes a quick overview of security and application design followed by a more in-depth look at web services security, explaining the need for threat modeling through security design patterns. Hogg explains a number of design patterns related to processes, services and SOA security, detailing on how they can be applied to service-oriented systems.
http://www.infoq.com/presentations/Understanding-SOA-Security-Patterns

In this interview from QCon San Francisco 2009, Don Box discusses the history of SOAP, XML, XML Schema, RELAX NG, SOAP and WSDL, REPL, opinions on REST, REST at Microsoft, coexistence of REST and WS-*, the M programming language, M and DSLs, M versus XML/XML Schema, Data as XML, and future plans for M and data modeling at Microsoft.

http://www.infoq.com/interviews/box-soap-xml-rest-m

However, as application complexity increases, the coupling of services becomes an impediment in adapting applications to meet the ever-changing goals of the business. Event Driven Architecture (EDA) is a method of designing and implementing systems where events are exchanged between highly decoupled components and services. EDA does not replace SOA, instead it compliments the request/response nature of SOA with a highly scalable event model for building and coordinating asynchronous transactions. This presentation explain event driven architecture, describe the different types of events, demonstrate how events can be related and orchestrated, …

Greg the Architect obtains instructions from his CIO to scope and deliver an SOA solution for their company. See what happens.

Based on real-life cases from the financial industry, Michael Poulin shows how to use 7 service oriented principles, Composability, Autonomy, Contracts, Abstraction, Loose Coupling, Reusability, and Discoverability, to handle service behavior in the execution context and UI changes, and how to prepare for unexpected changes.
http://www.infoq.com/presentations/Real-life-SOA-Michael-Poulin

The JBoss SOA Platform was released in February 2008 and has quickly become a significant open source SOA infrastructure. In this presentation we shall look at the architecture of the SOA Platform, what principles it is based upon, where is it going and how it can help deliver on the SOA vision.

Paul Fremantle presents three case studies of organizations, small and large, which decided to implement SOA. He details on design, architecture, technologies used, lessons learned, and potential disadvantages of the solutions chosen.
http://www.infoq.com/presentations/3-SOA-Case-Studies-Paul-Fremantle

The presentation is still beneficial and addresses a few interesting issues that are challenging like flexibility, reporting and management of SOA.

Related blog post with slides

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.
http://www.infoq.com/presentations/soa-web-services=practice