is equating SOA with web services. Although a lot of folks use web
services to implement services, that's simply an implementation
"So when watching Roy's presentation, replace the term "SOA" with "WS-*", and the discussion will make a lot more sense."
architecture is the collection of the fundamental decisions about a
software product/solution designed to meet the project's quality
attribute requirements. The architecture includes the main components,
their main attributes, and their collaboration (i.e. interactions and
behavior) to meet the quality attributes. Architecture can and usually
should be expressed in several levels of abstraction (depending on the
"Uniform Interface: Resources are identified by only one resource identifier mechanismAccess methods (actions) mean the same for all resources (universal semantics)Manipulation of resources occurs through the exchange of representationsActions and representations are exchanged in self-describing messages Hypertext as the engine of state: Each response contains a partial representation of server-side stateSome representations contain directions on how to transition to the next stateEach steady-state (page) embodies the current application state"
Hypertext as the engine of state:
Subscribe to RSS headline updates from:
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
© Copyright 2005-2013, Arnon Rotem-Gal-Oz
DirectionalRedux theme by John Forsythe and Jon Stovall