I originally planned to gradually share this draft paper with you all one section at a time, but I'm too impatient for that.
Below is the full draft - its in two formats: PDF and DOCX. Have a look and let us know what you think.
I originally planned to gradually share this draft paper with you all one section at a time, but I'm
Lots to catch up on. ASP.NET 3.5/AJAX/MVC It's out! ScottGu details the ASP.NET 3.5 Extensions CTP
I really don't see what most of what you cover in the paper has to do with Internet scale computing. AFAICT, it's primarily about "management", which is, by definition, enterprise scale because you can only manage your own stuff.
Mark - I'm not sure I understand your concern. The capabilities we covered in the paper are necessary for scaling out services, assuming you are responsible for hosting your own services in your own datacenters.
Scalability is merely a characteristic of architecture - it is not architecture in and of itself.
I remember when there were less than 5 hits on Google for this term.   A quick inquiry last
Ok, think about it this way. Your document provides guidance to somebody on an intranet who wants to expose their own services to other parties over the Internet. What it doesn't do, is provide guidance about *how* those services should be exposed. The former is intranet-scale computing, the latter Internet-scale.
Both are needed of course, but let's not confuse them.
I think we are in agreement on this Mark. The doc is less of a "how to" than a "what is needed". The original goal of the doc was to get people thinking about the operational capabilities necessary for enabling Internet scale services. It was never intended to be a "how to". We originally intended this to be a multi-paper series with a "how to" paper being teed up next (this is even mentioned towards the end of the paper). Since I'm in a new job now its doubtful that I'll get a chance to write the "how to" paper.
I'm not sure I understand your point about intranet vs. Internet with regard to management and operations. A service will always require some level of hosting and management, regardless of its expected deployment scale.