At least there are no objects that we can see. Objects may be used in an implementation of a service but there are no objects in the architecture (either remote or local). In a post that seems to miss this point, Sean Landis talks about “SOAs – Separating Hype from Reality”. Here’s a quote from his post…
“Web Services breaks one of the key doctrines identified in the classic “Note on Distributed Computing”: Local vs. remote objects. The argument made by Waldo, Wolrath, et. al., is that there is a fundamental difference between local and remote objects and any distributed system that attempts to hide that difference is fundamentally flawed.”
As I said, there are NO OBJECTS and hence there is no need to hide the difference between remote and local.
I agree with his comments on Grid computing though 🙂
(link via Stefan’s blog).
There’s a unique energy that comes with starting something new — a blend of excitement,…
As I continued work on BrainExpanded and its MCP service, I came to realize that…
Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…
After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…
Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…
As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…