Hot answers tagged

3

Varnish does not support SSL Running a site/service on SSL is a necessity for anything half serious, so thats one reason to use haproxy which will do SSL termination for you.


2

This is round robin DNS. This is a quite simple solution for load balancing. Usually DNS servers rotate/shuffle the DNS records for each incoming DNS request. Unfortunately it's not a real solution for fail-over. If one of the servers fail, some visitors will still be directed to this failed server.


1

You might find the mod_proxy module for ProFTPD useful for this; it supports forward and reverse proxying of FTP and FTPS, as well as load balancing (in multiple flavors). Full disclosure: I'm the author of mod_proxy and proftpd.


1

The bind and listen are not the same things nor things that can be done independently. They are consequent stages on the same port number. It is well described in this diagram from Wikipedia:


1

You can expose SSH on any port you desire. The clients must be aware of that, however. listen ssh-balanced bind <public-ip>:5022 mode tcp server term01 <internal-ip1>:22 check server term02 <internal-ip2>:22 check You need to use ssh -p5022 to connect, and scp -P5022 etc.


1

While both HAProxy and Varnish can load-balance, only one of them is built for it. You could just use Apache for your purposes as well since it can proxy and cache as well, but it's hardly an optimal solution. In my opinion, you're best to use each product for what it's best at. What I do is install both on the same box and configure Varnish to use ...


1

Multiple options / solutions come to my mind: NFS: Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems in 1984,[1] allowing a user on a client computer to access files over a computer network much like local storage is accessed. DRBD aka Distributed Replicated Block Device: DRBD® software is a ...


1

Having code and content managed, promoted, and deployed to all servers is a far better solution to setting up a 2-way-sync. Consider deploying server assets to all servers in your pool, rather than updating on one server, and counting on a sync/replication, or managing a sharing filesystem. This allows you to keep your content/code managed separately, so ...



Only top voted, non community-wiki answers of a minimum length are eligible