Sam Gentile, has written a *must read* post about why .Net developers don't grok scalable distributed systems. He cites lack of literature,among other things.

I don't totally agree with him, i usually choose to scale my applications horizontally. Either have subsystems living on different machines (preferably with their own data), or equally configured machines that are load balanced (can be easily replicated and when more horsepower is needed,you just need to add some iron to cope with the higher load). From what i've seen, this is easily acomplished but the database seems to be (invariantly) the bottleneck. If you don't acommodate this from the start [replication,data partitioning,etc], you are doomed sooner or later. (from my experience the later seems to happen when the database server vertically scalable is not feasible anymore (or no budget to do it :-))].  Adrian Bateman seems to share the same opinion and describes it much better then me. :-)

But there is something i would really love to see. A blueprint of the architecture him and Robert have been writing for the last few months.

I would really like to understand .Net Enterprise Services, and their advantages but i've failed to do it so far, i guess as sam says no sufficient literature. :-)

Maybe Sam will write a book about it? send me the amazon link, and i will surely pre-order it today. :-)

Perhaps an english version of Clemens book is in order? or Ingo rammer's next book will cover this gap?

Meanwhile TheServerSide.Net is compiling a top 50 list, on Who's Who in the Enterprise .NET World?