
Stuart Charlton
(5255) Managing Data in an SOA
Technical long talk 50 min
Wednesday, 2008-06-25, 14:00 - 14:50, Arena 6
Stuart Charlton - Elastra (speaker)
Topics
Abstract
Services Oriented Architecture (SOA) has become a popular approach towards
structuring information systems, and both RESTful and SOAP/WSDL-based Web
Services have come popular technologies for enabling that approach. But too
often, SOA seems to be "the architecture that forgot about data". Data
is the longest-lived portion of most information systems, and is shared,
queried, locked, modified, reused, repurposed, transformed, and interpreted in a
wide variety of ways as it flows between services. But how do we track these
interrelationships? And how should "data services" be designed?
A variety of specifications in the WS-* stack have been created to address the
problem of "data in an SOA": from WS-Addressing and reference
properties, to WS-ResourceFramework, which aims to enable access of both
computational and data resources for "grid" or "cloud"
computing. Meanwhile, the Web's REST Architecture offers a wildly successful
model to identifying and representing data that could also be adapted for a
company's internal information systems, and SQL services continue to support
most reporting and analytic applications.
This session explores these topics for practitioners: how to choose an
architectural style to support data services, the tradeoffs between SQL,
WS-Addressing, WS-ResourceFramework and RESTful data services, and practical
examples of designing data services and data-aware service registries, in both
SOAP and REST.






