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! š
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…