Slashdot Mirror

← Back to Stories (view on slashdot.org)

Java EE & Streaming Architectures

Posted by Hemos on from the a-better-cornerstone-for-a-better-building dept.

Amin Ahmad writes "Implementing a streaming architecture on a Java EE application server provides asymptotically better memory performance, and, hence, scalability, than current, widely-implemented, Java EE patterns endorsed by Sun. This article provides a concrete implementation of a streaming architecture and compares its scalability to two other, standard implementations: Remote EJB and Local EJB-based solutions. The implementation based on a streaming architecture comes out the hands-down winner: for example, when sending back 300 rows of data to the client, the Local EJB solution fails beyond 16 concurrent users whereas the streaming solution is still running at 128 concurrent users! The article includes complete source code and the entire results database for the stress test. I would be interested in hearing your feedback."

1 of 40 comments (clear)

  1. Java is great for learning by Anonymous Coward · · Score: -1, Troll

    But you have to get the hell away from it when it you want to run something fast(!) and productive on a server.

    JSP is a nice try to eat into the PHP market.

    But it's so slow and far away from the reality of productive systems that the Apache crew rather forked their server to a Java-only server (Tomcat) to keep their httpd codebase clean and free of anything that is Java.

    EVen if Java is open source now. There is a reason why Java applets have become almost distinct. Even Flash evidently performs better than an Java applet.

    And why the hell would anyone still need this "Compile once, run anywhere." nonsense?

    We have 2006. Not 1995.