Firstly, I am curious...
Why was Berkeley DB chosen for caching when a RDBMS (mysql in this case)
was already being used?
Secondly, I've worked on a good-sized commerce site with
mod_perl+HTML::Mason. One of the more dirty secrets is that the back-end
of the site involves several standalone perl programs running as
daemons. What's even worse is; most of them have to sit in poll/wait
loops waiting on message from external systems (such as pop3 servers,
ccvs etc.)
For comparions, a nice aspect of j2ee applications IMHO is the
"application server" tends to be more general. ie. the application
server is not just the web server (as it is with mod_perl). I've found
j2ee features such as message beans, queues and such especially useful
for back-end work. For these reasons, I personally don't buy the
argument that mod_perl makes an effective application server for a good
sized task (your mileage will vary no doubt ;).
So again, I'm curious, what does the eToys.com site back-end stuff look
like?
Great article BTW, Bill & Perrin,
Matt
On Thu, 2001-10-18 at 21:11, Andrew Ho wrote:
> Hello,
>
> I checked the list archives and it didn't look like this had been posted yet.
> For those of you who haven't seen it yet... a great read on perl.com about
> the Apache/mod_perl setup at eToys, co-authored by our own mod_perl
> regular contributer Perrin Harkins.
>
> http://www.perl.com/pub/a/2001/10/17/etoys.html
>
> Humbly,
>
> Andrew
>
> ----------------------------------------------------------------------
> Andrew Ho http://www.tellme.com/ [EMAIL PROTECTED]
> Engineer [EMAIL PROTECTED] Voice 650-930-9062
> Tellme Networks, Inc. 1-800-555-TELL Fax 650-930-9101
> ----------------------------------------------------------------------
>
>
>
--
pgp: http://www.geocities.com/matthewbk/pubkeyw.txt
PGP signature
