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).
Last year, I released the "Graph Model" library for .NET as an open source project. It…
Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…
In my last post, I wrote that "the typing of code was parallelized and delegated.…
In February, I wrote about the small team I'd stood up instead of hiring humans:…
Assembling a dream team without a single hire I've been making great progress on CVOYA's…
As 2025 is now behind us, I wanted to share a few reflections from my…