|
Hi SamAtt.
You know, your posting is fun to read. Nice. Still, the reason "Software System Architecture" or anything with the architecture name on it, has become a dirty word is because there is no understanding between an abstraction and a concrete thing. What you picture is known as Intellectual Violence, an architectural antipattern. In my case, if I want to talk about data, I say data. If I want to talk about information, I say information. They are not the same thing. SO, if I say resource, it means it is not data nor service. A resource can be a document, data, a service, a process, a whole system, anything. So, as you can see, that is no mental circle, I really mean anything. If you think a resource is just data exposed as a service, then you are missing thousands of other resource implementations. Why call it resource and not data, service or system? Because resource is an abstraction, that allows me to work it without knowing what the final implementation would be. Cheers! |