Tim has some comments on MEST. While I said that I am not going to try and describe MEST again until we have a paper written, I think I need to make a clarification (some more details can be found as a comment on Tim‘s post).
As I’ve said previously, MEST is not proposing something that we are not already doing. As Tim says, MEST is already omni-present. We were just trying to define the architectural style called “service-orientation” in terms of architectural elements (data, connectors, components) and then compare it with “resource-orientation” which is represented by REST.
I can’t emphasise enough that the last thing we have been suggesting is that there is only a single WSDL operation defined for every Web Service called ‘ProcessMessage’. Obviously it’s been our fault for not making this crystal clear! Sorry!
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…