Lists Home |
Date Index |
Try: It tells you where the focal point of the domain is.
Viewpoints: details are chaotic or organized depending on the proximity
of the viewpoint to domain. A baseball is a point at 100 feet, a sphere
at five feet, a curved surface at 1 inch, a cylinder wrapping a center
at 1/10 inch, a fiber mass at 1/100 and so on. How well you understand
the domain depends on the focal resolution of the viewpoint.
The focal point of SOA is when one decomposes a business into requests
for services by type regardless of implementation. That is why an
object oriented architecture is not an SOA. OOP is a closer viewpoint
and one may not need it for the SOA viewpoint (eg, one can implement an
SOA without objects but I wouldn't want to do that).
Yes, both REST and WS can be used to implement an SOA. We've had that
debate here before. As I recall, it came down to how much hand rolling
one wanted to do to build the product.
From: bryan rasmussen [mailto:firstname.lastname@example.org]
> Or could someone correct me? If I bumped into a service-oriented IT
> in one bank on one side of the street, and an object-oriented IT
> another bank on the other side of the street, how would I tell which
> which (other than by the choice of jargon on the Powerpoint slides)?
an anecdote of minor interest. We had a student in our office that did
his thesis on SOA. got a very good grade, has a nice job now. This guy
was quite smart and technically competent as well, I attempted a few
times to get a description of SOA out of him. I never did get anything
that I recognized as being technical, although whenever he talked
about it he got that abstracted look that I get trying to explain
various technical things to people. But anyway, I DID manage to
confirm from him that both REST and SOAP-based webservices were SOA.
Not sure if that helps narrow it down though ;)