Win a copy of Java EE 8 High Performance this week in the Java/Jakarta EE forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

servlet load  RSS feed

Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello there , can you please help me with this:
my application is multitier application .
applets run at end user and all the execution report data is
appended in one string buffer , whenever applet is destroyed - all
this data is sent to "MYServlet" on the server , "MYServlet" parse
this data and according to given logic inserts figures in the
database. now can you please tell me that how should my servlet
be designed and what webserver and java application server should
i use to achive maximum scalability that it handles the report
parsing coming from massive number of end users at the same time running jdbc queires as well , i have implementd entire code of
my applets and the servlet "MYServlet" but i am worried about
whether this single servlet can handle big big number of end user
at any given time , is tomcat is fine for this (what is limitation of tomcat)
waiting for your reply.
thanks in advance.
Saloon Keeper
Posts: 19098
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's an awful lot of variables to resolve for a imrecise goal at one time!
I think that you'll probably have to do some prototyping and test cases to see what works for you.
Tomcat is highly regarded for performance and is my favorite price (free), but an expensive commercial package such as WebLogic has the advantage that it's a unified server (does EJB's etc. as well as servlet/JSP) and has the ability to cluster servers.
I think that the most important thing you can do is not "solve" any problems before you have to. Try a simple approach, and if the results are unacceptible, MEASURE the system. DON'T DEDUCE. I've seen a lot of systems - including my own - where the programmer "knew" where the performance bottleneck was. And was totally wrong. Once you know the true weak spots, you can tune and/or modify code to get the most throughput for the least effort.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!