-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 10 August 2004 21:28, Eric Lenio wrote:
> the reason I'm asking is because the client is really more attuned to the
> java hype/buzzwords that exists out there.  having done just a smattering
> of java, I am somewhat at a loss as to tell them exactly why a perl
> solution is better. this client does already have some investment in java,
> but no perl, so it is probably more palatable to management to continue to
> invest in java.
>
> the client is also quite concerned with scalability, but I am confident
> that mod_perl will scale extremely well.

A few years ago I was in a similar situation. I was working for a big company 
(~500.000 employees) and someone from the upper management had 'decided' that 
java was the best tool for all purposes. Then some department had startet a 
new project and of cource tried to implement it in java using jsp. After 6 
weeks of more or less resultless effort the lower management decided to try a 
competing approach. To my luck the manager had had some positive experience 
with perl. He hired me and a fellow programmer gave us 2 weeks time to create 
something to show. After that time the java project was canceled and after 
another 2 weeks we had created a working system where all the basic 
requirements were implemented.

As for scalability I am running mod_perl-enhanced apaches on a web server farm 
consisting of 5 machines making 500.000 visits, 2.000.000 page impressions or 
18.000.000 hits a day. Every request on these machines is touched by 
mod_perl. And the system would run without noticable performance degradation 
even with only 3 of the machines running.

Torsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBGTCrwicyCTir8T4RAqblAJ49mhPFKcXSlVdOxhmuqDafhac4lACeJ5Qw
xGBcPUBgpzG6Hxn3JRYdULI=
=5hEB
-----END PGP SIGNATURE-----

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to