Itās really funny to experience your palās rise to stardom š I hope that Jim doesnāt forget his humble origins and friends :-)))
Due to the years weāve been working separately, our rhetoric has slightly diverged. I personally see a service as an architectural abstraction for encapsulating some piece of functionality, no matter how coarse-grained. That functionality can be anything from a business process to an OS process to the encapsulation of an entire organization. I guess Jimās focus on building enterprise applications has directed him to talk more about what makes sense in the business world, hence the āservice encapsulating a business processā discussion, but we are effectively talking about the same thing; of course we areā¦ how couldnāt we, after all those arguments when coming up with MEST, SSDL, SOA-related slides, and writing software together š
I loved the discussion on WSDL and messaging behavior and I was pleased to hear about SSDL again š BTWā¦ during my first year in Microsoft I built a prototype showing off how the messaging behavior of a service could be exposed as a XOML-based contract. I think the CSD folks were working on a product version of the idea already but I donāt know what happened.
As always, MEST had to be mentioned š
In generalā¦ I loved the show. Thatās my very good pal Jim! š
Last week, I wrote about the evolution of the CVOYA Graph. After a lot of…
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…