Where can I find a document or web site that shows a system for
localizing a high-traffic ASP.NET web site. I am looking for something
that describes the database architecture, and design of a flexible
localization system that does not rely soley on the Localization
Toolkit offered by Microsoft and that does not soley rely on the
mechanism built into ASP.NET (since this is not designed for
high-traffic web sites).

I have already determined that Microsoft's does not use the solution
they recommend to others, because it does not work well for high
traffic sites.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/entloctoolkit.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptutorials/html/resources_and_localization_using_the__net_framework_sdk.asp

Would a pointer to a publication(book) be appropriate? or Are you
looking for a free online resource only?

I have already purchased several books on the subject, but they are
not what I am looking for. Either they show you how to use the
built-in .NET API's to serve dynamic web pages (not intented for
high-traffic sites) or they talk about traditional software instead of
web sites. Some of the books I have already purchase are:
1. XML Internationalization and Localization 
2. A Practical Guide to Localization
3. Internationalization and Localization Using Microsoft .Net
4. .NET E-Business Architecture

I would be willing to review and purchase more books, but I would not
be able to tell you if that is what I was looking for until I actually
skimmed through the book.

I prefer an online resource.

Might I ask why you consider a dynamic website unsuitable for high
traffice websites?

May of the most high traffic websites on the internet are dynamic,
including Google, Yahoo, and Microsoft to name but a few.

Also, the caching systems of ASP.NET allow for a pseudo-dynamic cache
- if the information has changed, it will fetch it all out.  However,
if the information is unchanged, it will only perform a check to see
if that has happened and then will present the information to the
clients.

Plus, dynamic websites offer a great advantage: If the content is held
in a database or similar, then you can design the look of the sight
independent from the content.  You can redesign the entire site in a
matter of minutes.

Also, by performing the localisation dynamically you can have the
localised content and the localised designs separate from each other,
and add a new locale in the time it takes to design a new look and
translate the information already in the site.

As a web developer of several years standing, I would not be afraid to
use the extremely powerful .NET tools to localise a dynamic website,
especially considering that microsoft.com uses it throughout most of
their site now, and have demonstrated it is reliable and stable for
large-scale implementations.

Hope these thoughts give you another option to follow in your quest
for a solution.

LazerFX-ga

The site is dynamic. The issue, however, is that not every page needs
to be dynamic. One performance test indicated that a server which can
handle approximately 750 static requests per second, will only handle
480 dynamic requests per second (same page localized statically vs
dynamically using ASP.NET MS Enterprise Localization Toolkit). I would
like to do both. Many pages can be pre-compiled (i.e., generate the
page dynamically via ASP.NET, then save it so it can be served up as a
static page). Other pages can be a combination of pre-compiled content
and dynamic content. That pre-compiled static pages are also easier to
cache in a web farm scenario. I have spoken with the ASP.NET and
Localization Toolkit developers and they said that they would not use
the Toolkit for a site like microsoft.com or yahoo.com for performance
reasons.

ASP.NET caching does not work well with web-farms serving web pages
with content that changes often.

I would like to see how a website like microsoft.com is designed (as
far as localization goes).

The method would probably be something like this:

1. Precompile all pages and portions of pages that can be.
2. Handle a request for a static page, by serving up the precompiled
static page.
3. Handle a request for a dynamic page by using server side includes
to piece together precompiled portions of a page and generating
dynamic portions of the page.

Thanks for the comments.