Q: multiple backends

[Ivan Voras]

Poul-Henning Kamp wrote:

> Just saying "fault-tolerance" or "load-balancing" isn't saying much
> you see, we need to formulate strategies and algorithms...

What's wrong with the usual list:

- round-robin
- by load (measure response time from last x requests, send to the faster)
- by content (request .pngs from one server, .jpgs from the other)
- by address (request /dir1/* from one server, /dir2/* from the other)
- weighted (60% from one server, 40% from the other)

and the freaks:
- by hashing the incoming IP (so each IP gets bound to one server, 
useful for cookies)
- by size (learn object sizes, get smaller objects from one server, 
larger from the other)
- by cookie (learn cookies, hash/bin them to servers)

? :)

(this post is a half-joke, I agree there are so many options that it's 
hard to pick the best ones :) )

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20070706/69b05934/attachment-0002.pgp>