Design on handling servlet request

Question

Hi,
I have a servlet which will get request to execute a service.
What is the best way to design this component to cater for high transactions?
Once the servlet gets request, it needs to store the data to the database first and then execute the service.
Shall I create a new thread for each of the request? Beside this way, what other better ways which I can follow?
If I do everthing in that particular servlet, will it be a bad design?
Are there any design pattern which I can apply?
Thank you.
Any sharing will be appreciated.

Answer 1

Hi,
I have a servlet which will get request to execute a
service.
What is the best way to design this component to cater
for high transactions?IMHO it's difficult to say, but for instance you should use object pooling, in your case connection pooling. Depending on your business classes, for persistence I would have a look at O/R tools like Hibernate. Hibernate does internal caching as well.
>
Once the servlet gets request, it needs to store the
data to the database first and then execute the
service.
Shall I create a new thread for each of the request?
Beside this way, what other better ways which I can
follow?As far as I know and I do it, each request is handled by its own thread, so there is no need to start a thread on each request. The only problem is if you have class member variables or static variables because different requests change those variables depending on your business logic. So either make those variables synchronized (which makes each access to those variables even slower) or better do not use member variables whenever possible. Handle the business within a method.
>
If I do everthing in that particular servlet, will it
be a bad design?Yes, I'd say so.
>
Are there any design pattern which I can apply?Have a look at the FrontController Pattern for the servlet. And the Facade Pattern for the business logic. You'll find these patterns online too, google for "J2EE patterns FrontController". You should end up at a SUN Site.
Other relevant patterns are explained too.
>
Thank you.
Any sharing will be appreciated.