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 : Dell Technologies Inc. -- Ignore unavailable to you. Want to Upgrade?

To: Lizzie Tudor who wrote (85019)	12/12/1998 1:28:00 PM
From: rudedog	Read Replies (1) \| Respond to of 176388

Michelle - Apratim has a good point about internet support architectures if we think about e-commerce, which will probably drive a lot of volume in this space. Tandem has been selling a lot of machines into this space in the last 6 months, as has Sun - there are currently reasons to have a big scalable single machine or a tightly linked cluster for this part of the work. It is relatively easy to take general web service and disperse it - but SAP also did this by using a queueing server on the front end of an application farm a la R3 architecture. But there is also a central datastore which maintains persistent state in an R3 system, and the bigger that box is, the better the whole system performs. Current e-commerce architectures seem to be evolving to that same model.

To: Lizzie Tudor who wrote (85019)	12/13/1998 11:31:00 AM
From: BGR	Read Replies (2) \| Respond to of 176388

Michelle, I understand the model and why it needs smaller servers, but the reason for choosing the model doesn't look very wise to me. Allow me to speak from my six years of experience as a UNIX/VMS/NT and database designer, developer, administrator and project coordinator. Assuming a single server and storage configuration, order segmenting into components can very easily and transparently be done using database triggers (perhaps on updateable database views) in real time. Ad hoc calculations may then proceed for each division w/o problems. Alternatively, in a distributed environement where it is imperative for time zone, language and/or efficiency's sake that each department maintains it's own server and storage, multiway symmetric database replication may be used for synchronization. IOW, let the server and the storage do your work for you - don't reinvent the wheel. The advantages are two fold, first, consolidation may be simplified using database views thus reducing development cost and next, either redundant IT groups are eliminated or practises of diverse IT groups are standardized, making SOPs for maintainence, backup and recovery plans less complex and easier to follow. So you have the benefits and avoid the headaches. Of course you need the right heavy-duty feature-rich tools for the job. Those do exist. -Apratim. PS: I was reading your other post about mom-and-pop stores and their choice of h/w and s/w for e-commerce. Let me ask you this, if you were to start a new small business tomorrow, would you: 1. Try to hook up and configure a network of answering machines or sign up for similar service from your local telephone company? 2. Try to manage your accounts and that of your employees using MS Excel macros or sign up for the American Express Small Business Corporate Card? 3. Try to manage your e-commerce server yourself by buying an NT box, managing the HTTP as well as the database server and coding CGI programs or simply rent out similar space and services if available? Hoping for a consistent choice, -Apratim.