[nycphp-talk] Scaling LAMP Architecture
Anirudh Zala
zala007 at hotmail.com
Sat Oct 12 00:53:50 EDT 2002
Hans Z.
:)
Your r right, it's not imp. which tools u use, but it's imp. how effectively
u use it.
And as i told there can be several solution for this, and may be someone
will have better solution than i have..Gotcha
Anyway this was nice topic to discuss..thanks all for giving suggestions
Anirudh Zala
>From: Hans Zaunere <zaunere at yahoo.com>
>Reply-To: talk at nyphp.org
>To: NYPHP Talk <talk at nyphp.org>
>Subject: Re: [nycphp-talk] Scaling LAMP Architecture
>Date: Fri, 11 Oct 2002 12:26:44 -0400
>Received: from mc5-f17.law1.hotmail.com ([65.54.252.24]) by
>mc5-s8.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 11 Oct
>2002 10:02:33 -0700
>Received: from parsec.nyphp.org ([66.250.54.138]) by
>mc5-f17.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 11 Oct
>2002 09:37:27 -0700
>Received: from nyphp.org (parsec.nyphp.org [66.250.54.138])by
>parsec.nyphp.org (8.12.3/8.12.3) with ESMTP id g9BGQiWM058205;Fri, 11 Oct
>2002 12:26:44 -0400 (EDT)(envelope-from listmaster at nyphp.org)
>Message-Id: <200210111626.g9BGQiWM058205 at parsec.nyphp.org>
>X-Paralist-Archived:
><http://nyphp.org/list/paralist_archive.php?L_mid=1387>
>X-List-Software: Paralist 0.6
>List-ID: <nyphptalk.nyphp.org>
>List-Owner: <mailto:listmaster at nyphp.org>
>List-Archive: <http://nyphp.org/list/paralist_archive.php?L_lid=1>
>List-Subscribe: <http://nyphp.org/list/>
>List-Unsubscribe: <http://nyphp.org/list/>
>Organization: New York PHP
>X-Mailer: Paramail 0.5
>Return-Path: listmaster at nyphp.org
>X-OriginalArrivalTime: 11 Oct 2002 16:37:27.0968 (UTC)
>FILETIME=[7C76F200:01C27144]
>
>Hi Anirudh,
>
>
>--- Anirudh Zala <zala007 at hotmail.com> wrote:
> >
> > In SDDS, Data and Files are kept on several machines rather than same
> > server or 2 servers (i mean many companies use db server and
> > scripting/file server as separate to get better output and faster
> > execution). This tech is also known as Client-Agent-Server tech.
> > here u can say there is 1 main server where all data is kept and at
> > second level there comes Agents machines/servers interacts btwn main
> > server and client. All client servers has replica of main servers DB
> > but in diff parts not as whole db so like 4 servers with 25% and
> > almost all clients queries are first directed to this Agents only and
> > replied/executed by these 4 servers and if needed they are redirected
> > to main server and finally records btwn main server and agent servers
> > are updated.
> >
> > This is similar like concept of cache servers in Oracle and Java but
> > this is bit new and different. The main diff is all Agent servers
> > acts like as they are main servers so at client end u never know
> > where your request is being redirected or which server your data is
> > coming from?
>
>This is a very effective way to handle large quantities of traffic, and
>is needed with any DB/language/server/OS. While Oracle supports a lot
>of this as a shrink-wrapped package, there are limitations, and of
>course price. I've seen very effective implementations using
>replication/MySQL/round-robin, and with a cost of only the hardware. I
>think most sites would be hard-pressed to saturate even two Pentium-4
>MySQL servers with proper DB design. And scalability? Buy another
>server and add an A record to your DNS.
>
> > This is like a concept of having chain store where u have McDonald's
> > fast food available at New York, Syracuse and Seattle rather than all
> > have to go to New York only whether u live in Syracuse or Seattle. I
> > hope u all r getting what I mean.
>
>But there's nothing like a NY Big Mac :)
>
> > So main point is whatever tech (Db, Scripting lang, Servers OS u use)
> > your software must have Strong RDBMS, Proper coding style, Robust
> > architecture maybe using SDDS tech. an other normal stuffs.
> > These concept can give u satisfactory solutions, otherwise there is
> > no such tech. in this world which can give u all at once without
> > having Distributed Database and/or multiprocessing. Also PHP guys
> > will say PHP is best, ASP will say ASP is the best bcoz it has these
> > facilities, same with DB and OS,
>
> > ok ok we need to think in diff
> > direction and develop something new using existing tech :) not just
> > adhering to existing tools.
>
>Couldn't agree more,
>
>H
>
>
>=====
>Hans Zaunere
>New York PHP
>http://nyphp.org
>hans at nyphp.org
>
>__________________________________________________
>Do you Yahoo!?
>Faith Hill - Exclusive Performances, Videos & More
>http://faith.yahoo.com
>
>
>--- Unsubscribe at http://nyphp.org/list ---
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
More information about the talk
mailing list