Wow, the shit’s really hitting the fan this time, isn’t it? Go go stop energy!

The latest entrant is a surprise (to me at least); Simon Fell, author of PocketSOAP.

Though Simon and I may not like the stack for different reasons, any way you look at it, WS-* seems to be on its last legs.

Onwards and upwards to true loosely coupled, document exchanged based distributed services! You know, the World Wide Web.

If you’ve heard me discuss Internet scale systems, you’ve certainly heard me talk about the necessity of interface constraints for those systems. What hit home with me today was that this term is probably unfamiliar to a lot of folks, so it could be of value to attempt to relate it to other things that they might be more familiar with.

What other names does “interface constraint” go by? “Component model” is one you might recognize. The value of component models like Java Beans derives entirely from the generality of the common interface they define. In the case of Beans, that interface isn’t complete (it’s more akin to a CRUD interface) but it remains useful.

Hmm, I wonder what a complete distributed component framework might look like? 8-)