"Gianugo Rabellino" <[EMAIL PROTECTED]> wrote:
> Pier Fumagalli wrote:
>
>> Hm... I don't like squid that much... It doesn't allow you to do a bunch of
>> nifty stuff that Apache lets you do... It is a little bit faster, but speed
>> comes at a great price:
>>
>> For example, you can't direct people to a holding page when the servlet
>> container is down, and this is something that I definitely need in my
>> production environment,
>
> Good point.
Plus another bunch of gizmos that you can throw into your httpd.conf, once
you know your way around it... But it's more a "guruism" around a particular
piece of software than real knowledge...
> But when you say:
>
>> plus as the Java Virtual Machine, "squid" is a
>> single-process server, if the one process crashes, you'll have to wait for a
>> restart and basically unable to serve requests.
>
> and:
>
>> Performance is good, but you always have to see what you're going to loose.
>> As I said earlier, the main disadvantage of non-native solutions (or Squid,
>> for that matters), means that you are going to have ONE only process
>> listening to your port 80... That is not good.
>>
>> At least, it doesn't work for me, where hardware is not an issue, but
>> resilience is: I can throw in another E4500 to spread the load if I have
>> performance problems, but I cannot loose a hit (connection refused is not
>> acceptable in my workplace - although it still happens).
>
> I have somehow to disagree. There are other ways to achieve resilience,
> via redundancy and balancing (Foundry and Radware have both great
> solutions for that), and in every case where resilience was that
> important in my projects, I always resorted to external hardware doing
> the job for me (and much better than me, for that matter). And if you
> can throw another 4500 you can throw a WSD or a Server Iron for sure. :-)
At that point, it's I believe "preference"... I personally don't like
layer-3 switches and "intelligent" routers, as it'll be a nightmare when you
want to configure them... But hey, I'm old and an HTTPD fanatic :-)
I started doing this kind of stuff when no hardware up front was available
to handle proper load balancing and resilience, I might have to go back and
look back again at some possible alternative solutions...
Sure is that if I have a one-single-machine, either I use some multi-process
thinghy, or... Every single case, its solution I believe... You used to work
for an ISP, so you know your stuff around routers and switches, I always
worked with Apache, so I know my way inside HTTPd... :-) :-) :-)
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
