<Craig> As you can see, there's no such thing as a general answer to your question. The only true benchmark for your application is running your application :-). </Craig>
Thats the answer I was expecting, but you did give me some good meat to go off of.
The screens I would be building for this Order Entry app would have a decent amount of fields (10 to 30) on each page, and the typical round trip from client to server to client would probably produce 10 to 120 hits to the database.
Like you said, it all comes down to CPU cycles because the DB hits (in my case the way I see it) would be the same whether I have a thick client or browser based. I would really like JSF to come through in every way I hope it will, because my shop is fully embracing C#.NET (along with every other M$ technology) and I would rather keep our mission critical apps on the iSeries (now called i5). I am just not a big fan of Enterprise Microsoft products.
Thanks for your thoughts Craig, Aaron Bartell
Craig McClanahan wrote:
Before trying to evaluate JSF as a potential technology solution for your requirements, I would first try to figure out if the webapp paradigm (no matter what implementation technology you choose) is appropriate to the task. For order entry environments that are primarily form fill-in (with little server interaction until the order is complete), it is likely that this approach is appropriate. If you need *lots* of interactions during the process of filling out the form (i.e. making one choice dramatically affects the UI for subsequent choices), you need to think carefully about whether a thick client approach might be more appropriate.
If a web architecture looks suitable for your requirements, you'll find that JSF implementations in general are on the CPU-intensive side of the scale on the server side (but it's a *big* scale, with *lots* of application specific variations), but this is counter balanced by the fact that the client side interactions consume zero server side resources. If your primary constraints are database or network, it's not likely to matter at all. If your primary constraint is CPU speed on the app server (not common, but might occasionally be the case), this potentially matters.
As you can see, there's no such thing as a general answer to your question. The only true benchmark for your application is running your application :-).
Craig
On Thu, 13 Jan 2005 21:59:40 -0600, Aaron Bartell
<[EMAIL PROTECTED]> wrote:
Hi all,
I am curious to know the different scenarios people have implemented JSF and how intense the applications were. The reason I am asking is I am wondering if JSF could survive the replacement of a 5250 Order Entry application written in RPG on an iSeries. This particular application has 500+ users hitting it with many different database requests. Note that you cannot relate 500+ users using a standard website to the demands of an order entry app. There is just a lot more going on in order entry vs a shopping basket.
I understand that a lot has to do with the hardware you are running, how well you are load balanced, memory dedicated to your app server, etc. I am more wanting to know if JSF can perform with the best (the best being legacy systems that support thousands of users off of one server).
I am not necessarily skeptical, I just need positive reinforcement.
Thanks for any input, Aaron Bartell
