On Tue, 27 May 2003, Tin Pham wrote:
> Date: Tue, 27 May 2003 23:16:34 -0400 > From: Tin Pham <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Struts Performance - Any Benchmarks? > > Hi David, Craig, > > Thanks for your replies. I will forward them to my team. > > I made the same points about multi-threading verbally and following up with > research and references for the team. > > They seem to be itching for benchmarks though, so I'll give it to them by > building a single, then multi-servlet app and using Introscope with some > load test simulators. I was hoping somebody in a situation such as myself > already had done it. > That's pretty easy to deal with ... make THEM prove that single instances are worse. Where is THEIR evidence? After all, THEY are the ones that don't get it. :-) :-) > Now the next matter of opposition I'm getting is does struts work well in a > distributed environment for example load balancing. I will post this a > separate thread with what I have told them already. That is almost totally an issue of what your servlet container provides in terms of load balancing support. Struts (or any other app level framework) is going to be pretty much irrelevant to that kind of discussion, because the load balancing support is basically transparent to the application or to the framework. Overall, it sounds like your team is likely to succumb to "premature optimization" anti-patterns, and totally fail to understand what is really important about web application design. That's pretty tragic when it happens, because it's totally needless -- most of the things your team is stressing over are TOTALLY IRRELEVANT to the end user's perception of performance of your application. They are worried about the wrong things, at the wrong time in the development cycle. One possible approach would be to build a prototype using Struts, and exactly the same functionality using whatever design approach your team thinks will work better. It's pretty much a waste of effort, but some people won't be convinced any other way. As for evidence that the approach Struts encourages makes sense, you've got your pick of almost every J2EE-related design patterns book in existence. Any of them would be incredibly helpful to you, but one whose binding on my copy is always breaking (because I have it open all the time) is "Core J2EE Patterns" by Alur, Crupi, Malks et. al. (Prentice Hall, 2001). Besides finding out that Struts implements many of the recommended web tier patterns, you'll also learn a lot of good stuff about setting up the non-web-UI portions of your overall architecture. The other evidence is that Struts gets many thousands of downloads every single day ... and support for it is built in (or easily plugged in) to a wide variety of popular application development tools ... SOMEBODY must think it makes a pretty reasonable platform for building web applications. :-) Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
