A Comparison of Software Architectures for E-business Applications

Simple item page
dc.contributor.authorCecchet, Emmanuelen_US
dc.contributor.authorChanda, Anupamen_US
dc.contributor.authorElnikety, Samehen_US
dc.contributor.authorMarguerite, Julieen_US
dc.contributor.authorZwaenepoel, Willyen_US
dc.date.accessioned2017-08-02T22:02:55Zen_US
dc.date.available2017-08-02T22:02:55Zen_US
dc.date.issued2002-02-20en_US
dc.date.noteFebruary 20, 2002en_US
dc.description.abstractAs dynamic content has become more prevalent on the Web, a number of standard mechanisms have evolved to generate such dynamic content. We study three specific mechanisms in common use: PHP, Java servlets, and Enterprise Java Beans (EJB). PHP and Java servlets require a direct encoding of the database queries in the application logic. EJB provides a level of indirection, allowing the application logic to call bean methods that then perform database queries. Unlike PHP, which typically executes on the same machine as the Web server, Java servlets and EJB allow the application logic to execute on different machines, including the machine on which the database executes or a completely separate (set of) machine(s). We present a comparison of the performance of these three systems in different configurations for two application benchmarks: an auction site and an online bookstore. We choose these two applications because they impose vastly different loads on the sub-systems: the auction site stresses the Web server front-end while the online bookstore stresses the database. We use open-source software in common use in all of our experiments (the Apache Web server, Tomcat servlet server, Jonas EJB server, and MySQL relational database). The computational demands ofJava servlets are modestly higher than those of PHP. The ability, however, of locating the servlets on a machine different from the Web server results in better performance for Java servlets than for PHP in the case that the application imposes a significant load on the front-end Web server. The computational demands of EJB are much higher than those of PHP and Java servlets. As with Java servlets, we can alleviate EJB's performance problems by putting them on a separate machine, but the resulting overall performance remains inferior to that of the other two systems.en_US
dc.format.extent16 ppen_US
dc.identifier.citationCecchet, Emmanuel, Chanda, Anupam, Elnikety, Sameh, et al.. "A Comparison of Software Architectures for E-business Applications." (2002) https://hdl.handle.net/1911/96297.en_US
dc.identifier.digitalTR02-392en_US
dc.identifier.urihttps://hdl.handle.net/1911/96297en_US
dc.language.isoengen_US
dc.rightsYou are granted permission for the noncommercial reproduction, distribution, display, and performance of this technical report in any format, but this permission is only for a period of forty-five (45) days from the most recent time that you verified that this technical report is still available from the Computer Science Department of Rice University under terms that include this permission. All other rights are reserved by the author(s).en_US
dc.titleA Comparison of Software Architectures for E-business Applicationsen_US
dc.typeTechnical reporten_US
dc.type.dcmiTexten_US
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
TR02-392.pdf
Size:
783.69 KB
Format:
Adobe Portable Document Format
Download
Collections
Computer Science Technical Reports