|
|
Benjamin Carlyle
|
Benjamin has been involved with the REST community through his blog and other forums since 2004. He is credited with inspiring the popular Restlet framework for Java, he coined the term “REST Triangle”, and has deep understanding of both the theory and practice of REST-style architecture.
As an architect working in the Rail industry he is experienced in bringing together REST architecture, systems architecture, systems integration, and a variety of other topics at an enterprise scale. Benjamin has recently been working with the likes of Thomas Erl on documenting the convergence between SOA and REST.
Click Here to View Speaker Profile
|
"Modeling REST Service Capabilities"
REST services are services in the classical SOA sense. These services benefit both from applying REST constraints and from applying SOA principles. The conceptual definition of a service inventory is not directly addressed by REST constraints, and is largely governed by service-orientation principles. However, the contracts in a REST-style service inventory are strongly influenced by REST constraints.
Chief amongst these is the requirement for a uniform interface consisting of "standardized" methods and media types. Translating to SOA parlance, this amounts to the combination of a method centralization pattern plus the Schema Centralization pattern. A fine-grained identifier concept is also introduced with a view to allowing a service to expose an arbitrary number of "resources". These produce a uniform contract at a fine-grained level without requiring the service as a whole to expose the same total contract as other services within the service inventory.
In this talk we will demonstrate how a service contract developed to current best-practice SOA can be translated into a REST service definition by splitting each capability into a centralized method, a choice of centralized media types, and most importantly a service-specific resource identifier. We will further challenge the notion that REST services are either simpler or lower-level than classical services by examining the idea that this as essentially a layering exercise: Low-level service-specific capabilities are expressed as a high-level uniform REST interface.
October 22, 2009 - 10:15
Room: Diamond 2
Click Here to View Speaker Profile
"Governing REST-Style SOA"
REST-style SOA is SOA that complies with the REST constraints. The traditional governance role in SOA includes ownership of the set of contract design standards for a given service inventory. In a REST-style SOA this role is emphasized and enhanced by the combination of schema centralization, method centralization, and uniform contract centralization patterns.
These patterns mean that the set of media types (schema and encoding) and the set of methods (protocol, including header and response codes) used in the inventory are centrally controlled. In addition to this, only the centrally controlled media types and methods are permitted to be used in the architecture. The combination of method and media type form a conceptually-complete uniform interface that clients (service consumers) can depend upon without acquiring service-specific dependencies at design time.
Finally, the oversight roles and composition of Web standards bodies are compared to the role of enterprise architecture teams. The extra power centralization of media types and method give to the enterprise team is emphasized with the need recognized to give project teams additional representation in the process. The additional roles of maintaining a normalized service inventory and reviewing service capabilities and their expression through combination of standard method and service-specific resource identifier are also discussed.
October 23, 2009 - 15:30
Room: Mees
Click Here to View Speaker Profile
To locate the date and time for when these sessions are scheduled, visit the Conference Agenda page.
|
Platinum
Gold
Silver
Founding Partners
Media Partners
|
