Win a copy of Kotlin in Action this week in the Kotlin forum!
    Bookmark Topic Watch Topic
  • New Topic

Application context persistence  RSS feed

 
Yo Japs
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Report post to moderator
A J2EE application processes requests from the users and performs certain task.

- Each request comprises of several sub-tasks which are invoked one after the other. The application context object is updated each time the sub-task is through with the job.
- At the end of processing the request, the application context object contains the overall result of the processing done.
- The context object is then processed further to extract the key details of the result and the record is stored in a database. The result is then sent back to the user.

As evident from the points mentioned above, the processing of the context object does not add much value as far as the processing the user request is concerned. The application performance should improve by good amount if the step of DB insertion is done later asynchronously.

Any views on which should be the most optimised way to achieve this (saving the application context object). Should writing to the disk be performant as compared to the DB insertion?

Thanks in advance for your views/suggestions/comments.

Cheers,
Yogesh

PS: The application is supposed to process approx 1,20,000 requests in a day & hence application response time is a prime requirement
 
Ulf Dittmer
Rancher
Posts: 42972
73
  • Mark post as helpful
  • send pies
  • Report post to moderator
Please don't post the same question to multiple forums: CarefullyChooseOneForum

Let's continue the discussion in this duplicate thread in the J2EE forum, where it is a better fit.
 
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!