Please everyone, repeat after me… there are NO OBJECTS in service-orientation

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).

Recent Posts

My Coding Agent Needed Its Own GitHub Identity

In my last post, I wrote that "the typing of code was parallelized and delegated.…

1 month ago

Rebuilding My AI Team in Twelve Days — And Why

In February, I wrote about the small team I'd stood up instead of hiring humans:…

1 month ago

How I Built My Own Team of AI Developers

Assembling a dream team without a single hire I've been making great progress on CVOYA's…

3 months ago

Reflecting on 2025: Building CVOYA’s Future with AI Coding Agents

As 2025 is now behind us, I wanted to share a few reflections from my…

5 months ago

DIY smart home accessory – It all started with a question to ChatGPT

Few months ago, we bought a sculpture from a local art fair for our Palm…

5 months ago

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

7 months ago