Re: web replication
- From: fusillo <fusillo@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 08 Aug 2006 04:12:01 +0200
ed ha scritto:
i'm thinking abount 3 tier architecture
have you some references/advise about?
I suggest using the NAT based solution because HTTP is session based,
unless you have FTP clients of course.
To replicate the file system use rsync, or a SAN/NAS.
Filesystem replication is the bane.
client -- load bilancer -- n web server + script engine -- db
to enable the http session information i think about using a network
filesystem placed on backend and setting the mount point as a session
directory path (using the php session's configuration directive)
the cookies should not be a problem, should it?
cookies resides in the client browser and forwarded to the server based
on domain name (the bilancer domain name).
to replicate the db i would use a simple master slave mysql configuration.
the unsolved problem is bilanced the https session, a session must use
the same server because there's an handshake for the simmetric key
exchange..
how do you recognize a single https session from another https session?
the actual idea is not shape this traffic and dedicate one server for
the ssl traffic using port for the nat prerouting rule.
rsync is a good idea to syncing the web content of the n middleware
server. thanks
every advise is really well appreciated
fusillo
.
- Follow-Ups:
- Re: web replication
- From: ed
- Re: web replication
- References:
- web replication
- From: fusillo
- Re: web replication
- From: ed
- web replication
- Prev by Date: Re: Linux to handle internet connection
- Next by Date: Re: web replication
- Previous by thread: Re: web replication
- Next by thread: Re: web replication
- Index(es):
Relevant Pages
|