[ale] J2EE vs PHP

[Michael Mealling]

On Thu, 2004-03-11 at 16:30, Ronald Chmara wrote:
> On Mar 11, 2004, at 10:34 AM, Fletch wrote (and quoted):
> > You might want to check out this paper.  I've quoted the conclusion
> > paragraph below.  And I trust there's no confusion about what I'd
> > sugguest instead of either of your sugguestions. :) (mod_perl
> > underneath either HTML::Mason or Template Toolkit, of course)
> >
> > Experiences of Using PHP in Large Websites
> > http://www.ukuug.org/events/linux2002/papers/html/php/
> >

> PHP is quite 
> easily scalable, if one simply takes the time to learn *how*. Same as 
> most other languages....but trying to scale perl in the *same* way as 
> PHP in the *same* way as ASP in the *same* way as J2EE? That way 
> madness lies. Each environment scales differently.

Do you have any pointers for what the proper way to scale PHP is? And
scale doesn't just include TPS rates. Scale includes complexity as well.


> IMNSHO:
> When one needs highly rapid feature implementation and version 
> iteration.
> When one needs to keep hardware overhead down.
> When one's application is primarily web-and-db-centric.
> When one is not bound to using a specific programming style.
> When one is going to be using pre-existing PHP code bases to build from 
> (or with).
> When one doesn't want their job to be farmed to India. ;-)

Can you speak to other specific concern about the ability to have
multiple programmers developing modular systems with PHP? In most of the
situations I've seen the number of developers and the complexity of the
pageflows requires blackbox modularity. It would seem the single
namespace issue would create havoc if you had more than a small handful
of developers.

I actively use both J2EE and PHP on the same machine and any PHP system
just seems to me to be more 'fragile' the more complex the system gets,
especially when it comes to attempting to extend the application....
Just a personal impression, though...
-MM