|
From: <ja...@op...> - 2001-06-15 02:37:25
|
"Harry Mangalam" <man...@ho...> writes:
> Your point is well taken, and in fact we were at one time going to do the
> whole thing as an 'application server'. That is, spawn the analytical
> process on another machine with a custom perl interface for doing so (the
> remains of that code can still be detected in older version fo the
> server), but it started to get to be more trouble than it was worth.
This was something like our original design:
------------
| WWW Server |
------------
|
|
------------ TCP/IP --------------------- TCP/IP -----------------
| DB server |--------| Application server |---------| Analysis Server |
------------ --------------------- -----------------
The idea being the WWW server would just handle HTTP requests, and
return data to the user. The 'Application Server' would farm out any
jobs to the DB server or the Analysis server, compile the data and
send it back to the WWW server. That way we could easily implement
queuing on the App server if we wanted. Also, you could make the
Analysis server be a big beefy SMP box, likewise the DB server. You
could also have the WWW on one side of a firewall and the others
behind the firewall.
jas.
|