The axioms of web architecture and an invitation for big vendors to understand them.
That is to say, they don't get it. This started out as a simple rant and turned into a decent sized essay on basic shared-nothing architecture and scaling down.
Bill de hÓra knocks one out of the park: "I think sometimes that the problem people have with REST is that it's so well-defined; it's not witchcraft, it's not a cargo cult. You can't argue with it on a relativistic basis or apply clever rhetoric or continuously redefine what it means. An architectural style isn't 'good' or 'bad' - you have to decide if it's the right fit for your problem space and if not, you have to come up with a more appropriate one."
An all around great post from Bill de hÓra. Wow.
Okay, I've read about five of these articles purporting to explain Git's internal conceptual framework. This was the first that really made things click in any significant way.
Roy Fielding on the difference between architecture, architecural styles, patterns, implementations, and applications.
Rut-roh. The RDBMS crowd is none too happy about the recent MapReduce talk. This article suggests they've solved all these problems a long time ago and that MapReduce is basically retarded. This discussion will get interesting over the next few weeks.
This is a scary description of a small chunk of my tech career: "In a previous life, I helped develop ESBs. I’ve written about them and I’ve promoted them. But somewhere along the way, I lost the religion."
"There is an important tradeoff between the computational power of a language and the ability to determine what a program in that language is doing."
Linux, Apache, PHP, and memcached are the big winners. Nice to lighttpd represent.
"It was as if its architects were given a perfectly good hammer and gleefully replied, 'neat! With this hammer, we can build a tool that can pound in nails.'" -- that is THE SINGLE FUNNIEST SENTENCE ever assembled in the history of english language!
How long has this been floating around? Roy Fielding on building the web... (via Aristotle Pagaltzis on rest-discuss)
This is too funny: "... provides you with the verbiage you need to explain SOA to non-technical people and 'sell' its long-term strategic benefits."
"Each resource demarcates a subset of an application's state, and becomes a handle by which other applications can interact with that state."
Excellent description of where Enterprise Architects should be moving and why...
Nice python-list thread with Paul Rubin challenging my ibm-poop-heads article and Andrew Dalke (and quite a few others) champions it. This discussion is worth more than the original article!
What the Internet Is and How to Stop Mistaking It for Something Else.
This is too cool.