On Wed, Sep 10, 2003 at 02:54:42PM +0530, Shuvam Misra wrote:
As what my
reading goes about this query is when to use LAMP and when
J2EE?? For this, many of the Gurus suggested that for mid/small size
projects, the best option available is LAMP over J2EE and for bigger
enterprise applications, go for J2EE.
I feel that there is no _intrinsic_ limitation or inefficiency if you
use one over the other.
I am not really sure about this, considering that PHP and Perl work
through Apache modules, while J2EE will require Tomcat or equivalent.
Not to mention that PHP is designed to be inserted inside HTML making
it ever so convenient to embed dynamic content into essentially simple
HTML. And if you still want real juice, you can always recompile
Apache with these modules built in, the way apache-perl is provided on
As a matter of personal taste, I would stay away from all things Java
as far as possible ...
Other non-technical and semi-technical issues
may become more important in deciding your choice (e.g. how comfortable
does your client feel about sourcing Perl programming resources?
I agree on that. But I would suggest that if you want your code to be
maintained and developed in the long run by purely enthusiastic
volunteers (which seems likely for a school) then go for PHP or Perl.
And also be sure to check out all the frameworks that people have
designed over the years to make project design and implementation in
Considering scalability, I am not sure designing for 9th and 10th and
then using it for all the standards constitutes "scalibility" at all!
And given that Slashdot runs on Slash, which is entirely made up of
), I don't think there is
any question about whether LAMP can handle scale. Remember this is the
code responsible for the slashdot effect that can bring down
enterprise websites due to exceedingly large amounts of traffic!
Research Scholar, KReSIT, IIT Bombay