|
Home > Archive > Perlbal > October 2007 > how does re-proxy work?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
how does re-proxy work?
|
|
|
| Hello,
I was reading about reverse proxy functionality, but still cant understan=
d how is the traffic redirected.=20
For eg. if I host static content in two datacenters and one perlbal repro=
xy server is hosted in third datacenter.
Then is all inbound traffic routed trough perlbal server, but is outbond =
traffic from each datacenter routed back=20
to client same way over perlbal server or the reproxy handles just direct=
connection between static content
server and client so the bandwidth hungry traffic goes directly from stat=
ic server to client?
Goodwill
| |
| Brett Hoerner 2007-10-23, 1:12 pm |
| On 10/23/07, dangalist@centrum.cz <dangalist@centrum.cz> wrote:
> Then is all inbound traffic routed trough perlbal server, but is outbond traffic from each datacenter routed back
> to client same way over perlbal server or the reproxy handles just direct connection between static content
> server and client so the bandwidth hungry traffic goes directly from static server to client?
No, the traffic always goes through Perlbal. To make a client
directly connect to a different resource you need to provide a
different URI, so I guess you could use redirects if this is totally
important, but I don't know your use case.
Brett
| |
|
| >No, the traffic always goes through Perlbal. To make a client
>directly connect to a different resource you need to provide a
>different URI, so I guess you could use redirects if this is totally
>important, but I don't know your use case.
>
>Brett
>
I would like to use perlbals x-reproxy-url feature to serve images or ot=
her multimedia data from mogilefs,=20
so if all traffic would go trough one datacenter/server it will have prob=
ably longer delivery times due to longer route=20
and also bandwidth in perlbals datacenter will be pretty high if every fi=
le will go trough proxy server back to client.=20
Is there any way how to set it up to keep advantages of mogilefs across d=
ifferent datacenters, but dont route all traffic=20
trough one proxy server?
| |
| Brett Hoerner 2007-10-23, 7:12 pm |
| On 10/23/07, dangalist@centrum.cz <dangalist@centrum.cz> wrote:
> Is there any way how to set it up to keep advantages of mogilefs across different datacenters, but dont route all traffic
> trough one proxy server?
Not that I can think of, that's just how the web works. I'm not sure
what sort of media you're serving but this is where people tend to
split it off into subdomains. media1.domain, media2.domain, etc... so
that you can refer the user's client directly to the resource (which
could be at any physical location). Your load balancer could send
people a redirect to those resources on the subdomains if you still
want domain.tld/my_resource to be 'valid'.
When it must be accessible through one specific URI people get into
DNS round robins [1] and other such intraweb mojo, so that you can
spread the load among multiple reverse proxies, but at the end of the
day if you want to ask a Perlbal instance to fetch a resource, it has
to fetch and respond with the resource itself (meaning the traffic
goes through it).
Brett
[1] http://en.wikipedia.org/wiki/Round_robin_DNS
|
|
|
|
|