forked from perlorg/perlweb
/
perl-loadbalancer.html
52 lines (50 loc) · 1.8 KB
/
perl-loadbalancer.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
[%
page.import({
title => 'Perl load balancer and web server - Perlbal',
section => 'about',
description
=> 'Perl load balancer',
});
%]
<h2>
Perlbal - Perl Reverse-proxy load balancer and web server
</h2>
<p>
<em>Improving web performance and reliability</em>
</p>
<p>
<a href="http://search.cpan.org/dist/Perlbal/">Perlbal</a> functions as a load balancer
and web server, improving reliability and flexibility with the ability to add and remove
backend servers on the fly.
</p>
<p>
As a reverse-proxy server Perlbal sits in front of your application web servers, proxying
the inbound user request, enabling the application server to return content to Perlbal
and then get on with the next request, even if the user is still downloading the content.
</p>
<p>
A pool of backend servers can be easily configured (and reconfigured on the fly). Perlbal will
load balance across this pool and stop using any server which does not respond, allowing
transparent fail over and horizontally scalability for your web applications. Indeed Perlbal can
use different pools of servers for different URLs, though it's <a href="http://search.cpan.org/search?m=module&q=Perlbal::Plugin">Plugin</a> support.
</p>
<p>
A perfect partner for any web server. Even if you only have one physical server, running
Perlbal will provide performance benefits (including serving your static content directly)
and prepare you for future scaling.
</p>
<h4>
Resources:
</h4>
<ul>
<li>
<a href="http://search.cpan.org/dist/Perlbal/">Perlbal</a>
</li>
<li>
<a href="http://search.cpan.org/dist/Perlbal/lib/Perlbal/Manual.pod">Perlbal Manual</a>
</li>
</ul>
<h4>
Article Author
</h4>
<p><a href="http://leo.cuckoo.org/">Leo Lapworth</a></p>