Monthly Archives: February 2003

Reliability and group communications

Werner responds. I don’t think we’re that out of synch, but I maintain that from what I’ve read of the techniques he’s talking about, they are not suited for Internet scale use. And by that, I mean a few orders of magnitude larger than the 10K/100K numbers he quotes. More like 10^8-10^11. I know that… Read More »

Reliability provisions

Werner Vogels comments on my argument against reliable messaging. I’m not sure he read it in its entirety though, as he leads off by saying; I was surprised to read Mark Baker’s statement that he feels there is no need for reliable communication provisions in web-services runtimes. Which isn’t the case, because I said that… Read More »

Discussion on Jorgen’s presentation

Jorgen responds to my comments on a presentation he gave last week. Re my comment that architectural styles are pattern languages, not patterns, I can only point to Roy’s dissertation on this, where he suggests the association between an Alexendar “pattern language” and an “architectural style”, by suggesting indirectly that both are a system of… Read More »

REST and SQL

Jorgen asks Is REST the SQL of the Internet?. There are definitely some similarities between REST’s uniform interface and the SQL language, most importantly that they are both coordination languages, a priori deployed application interfaces that defer component binding (i.e. late binding), which are ideal for deployment on a network between untrusted parties (hence the… Read More »

OASIS does Reliable Messaging

Apparently OASIS has decided to tackle reliable messaging, with help from the usual non-IBM/MS Web services suspects. I think “reliable messaging” is a huge waste of time. It’s akin to saying that the network is unreliable, so let’s just make a reliable network on top (which is different than “reliable data stream” ala TCP). Sorry,… Read More »

We don’t need no steenkin’ schemas

Bob DuCharme gets back to basics about RDF, and in doing so clearly hilights the value of partial understanding. Notice how the integration problem he undertakes scales linearly with the number of documents, rather than proportionally (O(N)) as it would if his code had to have full knowledge of all those schemas. By using RDF’s… Read More »

Bill Gurley on Software-in-a-box

It’s good to see Bill Gurley has restarted his “Above The Crowd” newsletter. His latest is “Software in a box”, where he talks about a topic that I’m quite familiar with; we shipped the first version of our software at Idokorro in a Cobalt Qube for some of the reasons he mentioned; ease of installation,… Read More »

Capeclear presentation about architectural styles

Jorgen points to a presentation he’s giving at an OMG Workshop comparing Service Oriented, Resource Oriented, and Object Oriented architectural styles. This is somewhat similar to my REST Compared presentation, though mine was done at a lower level. I’ll jot down some comments here as I read it. Slide 10, “In other words, architecture styles… Read More »

BEA on integration

Here’s a telling statement for you, from a BEA press release; Recognizing that every integration project requires development, and every development project requires integration This is absolutely wrong; every integration project does not require development. This afternoon I subscribed to (i.e. integrated into my existing aggregate feed) a few more weblogs, and did it without… Read More »

State Really Is Hell

Jorgen Thelin references Bill de h&#211ra’s blog on session state. Unsurprisingly, it appears there’s some serious misconceptions about state going on here. As Ken Arnold said, “State is Hell”, which jives with my experiences. Bill writes; One issue with the REST hypertext model is its view on managing state. REST constrains that state reside on… Read More »