I have also heard good things about JDO but have not had the time to check it out (other than reading a couple of articles in "Java Pro." As far as picking the right database goes, you are spot on that one! Even the right database version matters. The old VoiceStream ecommerce site was on MS SQL Server 6.0 and performance SUCKED. When we created the new site for T-Mobile (good-bye Jamie Lee, heeeeellllllooooo Kathy!), we chose Oracle 8i (just upgraded to 9i) and performance improved by a factor of 2.
An additional comment on EJB performance. As is (regrettably) sometimes my style, I was a little harsh. EJBs, like any code in any language - even the Struts core classes, can be coded abysmally and badly design algorithms can slow execution of any routine/method to a crawl. Further, the efficiency of the container is also critical. For example, we started this project using JRun 3.1 and a documented memory leak kept forcing us to reboot the server every 24 hours (session beans were not being garbage collected; Allair says this has been fixed in 4.0). The ever-decreasing amount of available memory made the app run at a snail's pace towards the end of these cycles. We changed to BEA's WebLogic 6.1SP2 and the app flies again - we have only needed to reboot the server to accomodate new builds. Mark -----Original Message----- From: Peter A. J. Pilgrim [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 10:29 PM Galbreath, Mark wrote: > Check out http://shop.t-mobile.com dude - the entire site is a Struts + EJB > app. If your EJBs didn't scale, you did not know what you were doing. > > Mark > I would also say that you pick right database tables to make entity beans in the first place. This is where the performance probably failed. You can make SessionBeans pass back RowSet, or HashSet or DataTransferMaps of the rows of the database table instead. Especially in a shopping web app. Other people have advocate JDO as a replacement for EntityBeans and I think this technology also works, but I am not sure if it is distributed or supports the type of transactions that J2EE / JTA fully endorses. Couple of books "EJB Design Patterns" F.Marinescu and Mr Grand "Java Enterprise Patterns" spring to mind. > -----Original Message----- > From: V. Cekvenich [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 7:26 AM > > They are hype marketed as such. Most newer developers try them, as I did > when I was new, but in production they did not scale, so we removed > them. On new sites I skip the writing them part, since people would > only remove them in production. (some management that take EJB to > production are so upset that they go to the cached .NET ADO, so I steer > my client's clear). > -- Peter Pilgrim +-----\ +-++----++----+ Java Technologist | | | || || | 'n' Shine | O | | || --+| ---+ /\ | ._ / | | \ \ | | / \ | | \ \ | |+-- || ---+ A new day /_ _\ "Up" | | | | | || || | is coming || +-+ +-+ +-++----++----+ <home page="http://www.xenonsoft.demon.co.uk/"; /> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
