Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: cfimx who wrote (29222)	3/21/2000 1:07:00 PM
From: rudedog	Respond to of 64865

twister - are you saying that suncom doesn't do well in the "front end" part of this ecommerce buildout. who is doing well there? That's an easy one - the dot-com buildout is almost exclusively MSFT and Linux on the front end. MSFT has a little over 40% by units, Linux just under 40%. And units are OK there since the predominant architecture is 1P or 2P machines... The remainder, less than 20%, is spread among a number of vendors, with a decent presence of SUNW machines. What is the archetecture of an ISP and ASP or other service provider? The simplistic answer is 3-tier but they are not the traditional 3 tiers of the client-server world. The actual "front end" is a load balancing and transaction management layer that distributes requests to multiple web servers and resubmits failed requests transparently to the user. The second layer consists of the web servers themselves, which in a web environment also perform application services in some sense. The third tier consists of data resources - centralized repositories of application data and content. These might be HTML, images, scripts, and CGI/Java/COM executables as well as databases. I am not considering ERP and other existing 3-tier architectures which are now being accessed via web components, although that is an important growth market. Some descriptions of this architecture consider the load balancing component as part of the infrastructure. The back end is then divided into application services and database services. For whatever reason, no one seems to want to consider this a four tier architecture... In any event, SUNW plays well in the back end with a combination of big machines (UE10000 and UE6500) supplying centralized database and other "monolithic" services, and smaller machines providing application support. This architecture is almost arbitrarily scaleable, except for the "monolithic" back end components which have become increasingly the limit on overall size, just as they did for ERP systems.