The PHP Scalability Myth
Subject:   Performance NOT EQUALS to Scalable
Date:   2003-10-16 02:08:13
From:   anonymous2

Performance: time to finalize an user action

Scalable: time to finalize thousands of concurrent user actions not very different than serving one.

PHP-JSP : similar performance.

JSP only performs better than JSP-J2EE, obvious.


JSP-J2EE scale => thanks to distributed and parallel programming.

Please rewrite the article.

Main Topics Oldest First

Showing messages 1 through 4 of 4.

  • Jack Herrington photo Performance NOT EQUALS to Scalable
    2003-10-16 08:11:45  Jack Herrington | O'Reilly Author [View]

    What is your definition of J2EE, because if your definition of J2EE includes a JSP/POJO configuration then you have a logical three tier architecture which is exactly the same as PHP. How is it then that JSP-J2EE scale and PHP not scale?

    Without more concise information I cannot 'rewrite article'. I appreciate the please though.
  • Performance NOT EQUALS to Scalable
    2003-10-16 06:35:09  anonymous2 [View]

    In other words, with a thousand users accessing a single server, PHP may work as well as Java.

    For a million users, 10 servers using J2EE architecture can perform well.

    What do you do with PHP?
  • Performance NOT EQUALS to Scalable
    2003-10-16 05:20:56  anonymous2 [View]

    I think the previous commenter is observing that
    *real* scalability is architectural, and explicitly
    provides for distribution and parallelization.

    That's apt, of course. Without providing details
    I can't afford (in time) just now, I'll counter-assert
    that, while Java certainly has plenty of distribution
    stories told about it, PHP and other scripting alternatives
    should feel no shame. I applaud author Jack Herrington
    for at least opening the debate with a proper focus on architecture.
    His is an article that needed to be written, and I
    hope it will be widely read.

  • Performance NOT EQUALS to Scalable
    2003-10-16 04:38:39  anonymous2 [View]

    scalability is achieved either by having a "read-only" application, which can be easily deployed on multiple servers, or by having a way to distribute the changes on multiple copies of the database. It has a lot more to do with _how_ you write the application rather than which particular language, libraries or platform you choose.