Fast CGI Vs Java Application Servers

Måns Rullgård mru at users.sourceforge.net
Sun Jun 29 13:14:13 CEST 2003


Irmen de Jong <irmen at -NOSPAM-REMOVETHIS-xs4all.nl> writes:

> > How does FastCGI compare against java Apps running in java app
> > servers like TomCat, Sun One, WebLogic and WebSphere?
> 
> 
> A (fast)CGI program compared to the actual Java program may not be
> much of a difference, depending on the program of course. What is
> a *huge* difference is that the Java app is running inside an
> *application server*. A (J2EE) Application Server provides a
> rich environment on which to base your scalable enterprise applications:
> - security
> - connectivity
> - scalability (performance, clustering)
> - maintainability / managability
> - error reporting/logging
> - component based (EJBs)
> - database connectivity and object persistence
> - transactions
> - ...

Someone mentioned buzzwords elsewhere in this thread.

> All of these are standardized in some way (as part of J2EE).
> In theory you can move your J2EE application to a different
> environment running on a different vendor's app server without
> much sweat.

That is, after you spent three weeks trying to figure out the correct
classpath, if one even exists.

> You don't have any of this readily available when writing (fast)CGI
> applications; you have to implement all of these yourself.

Hey, it could be fun.

-- 
Måns Rullgård
mru at users.sf.net




More information about the Python-list mailing list