• Seven smart statements about SOA
• Who's killing SOA?
• Web services stacks – Windows Communication Foundation (WCF)
• The standards behind Web services
• The 2008 SearchWebServices.com SOA survey
• The convergence of service orientation and business strategy
• SOA: Are we in business yet?
• Avoid vendor driven architecture (VDA)! / Podcast preview of London event
• How difficult is SOA?
• Defining business services: SOA from a corporate perspective
• Efficient XML Interchange tackles data verbosity
• REST and relaxation in SOA
• Starting your SOA project on the right foot
• The SOA marketing paradox and the Wizard of Oz
• The Axis2 Web services toolkit
• Does Microsoft get SOA?
• Using Web services as distributed transactions and the role of XA
• XML to DDL imports, synchronizes database schemata
• SOAP 1.2 Second Edition
• So you think you know SOA?
• Omnipresent SOA
• Using ADO.NET and SDO for SOA data continuity
• Creating rich Web service clients with Flash and Flex
• Introducing our SOA Lifecycle All-in-One Guide
• The concrete abstraction of the business service
• Why SOA isn't going away
• The SOA data integration lifecycle
• WADL: The REST answer to WSDL
• The multiple points of entry in SOA
• The basics of MathML 3.0
• SOA infrastructure patterns and the intermediary approach
• SOA 101 – it's about the architecture, stupid
• XML to the rescue: Data governance in SOA
• JavaFX Script as a Web service client
• SOA quality involves more than testing
• Divorcing SOA and Web services
• SOA at Conjunction Junction
• SOA and Composite Applications
• How EDA and CEP fit in with SOA
• Heterogeneity and SOA
• The Concordia Project and XML security interoperability
• The SOA requirement for data integration
• The universal translator in SOA and EDA – a canonical business model
• Eclipse and SOA infrastructure
• Operating system virtualization and Web services
• XQuery 1.0: A long time coming, now what?
• The governance, quality, management trifecta: Making loose coupling work
• Ruby on Rails – preparing for an enterprise invasion
• The REST of the SOA story
• CAM: A Swiss Army knife for XML structures
• SOA's newest product category, ESB hardware
• Accelerating SOA performance via transport optimization
• Mashing the phone
• Migrating to XSLT 2.0
• SOA a big deal for IBM and HP
• Finding the real barrier to SOA adoption
• Web services and Second Life
• Diving deeper on SOA
• Migrating data from CICS to XML is a major SOA challenge
• JavaOne, an SOA showcase
• XBRL, XML with a mind for business
• SOA performance, easier said than done
• Multi-core processing and its impact on SOA
• What's up with XML 2.0?
• Web 2.0 and SOA
• How Web services can use JavaSpaces
• The third conversation
• The fundamentals of identity federation
• The new breed of software vendor, the SOAsaurus Rex
• SOA and the core competency model
• Data interchange issues for SOA
• Quantity is no measure of maturity
• SOA and the next billion dollar baby
• SOA security: Don't forget identity and access management
• The top five SOA urban legends
• The Eclipse SOA Tools Platform
• The SOA big picture
• SOA-based software change management for mainframes
• Say hello to XPath 2.0
• Integration + governance = SOA?
• Using an ESB to simplify the complexity of SOA
• Pitfalls of SOA RFPs
• Grid computing and Web services
• The ESB, SOA's venerable product offering
• How to architect governance
• Operational Risk and WS-Policy
• What BPM experts know about Business Process that SOA folks don't
• SOA and EDA: Using events to bridge decoupled service boundaries
• SOA projects: Going beyond the ESB with your SOA implementation
• Why we watch Eclipse
• Competitive SOA
• A standard SOA paradox
• Using Microsoft's Visual Studio IDE for Web services
• Podcasting software covers many bases
• The state of worldwide SOA adoption: Is the US behind?
• SCA and SDO for PHP
• Architects: SOA masters or lost in translation?
• The XML behind podcasting
• Pragmatic SOA
• IDEs for Web services – Eclipse
• More