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

servlet help  RSS feed

 
Binoj Viswanathan
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i am confused whether i shud go for servlet implementation or ejb implementaion for my application.it only has to access data(diplaying in mobile phones).there may thousands of users at a time.there is no update or insert of data by the users.but some other external systems are changing the the data (rapidly changing)every second/millisecond!!!.here is my problem.pls guide me
 
Michael Arndt
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The infos you provide are not really enough to give you an advise that might fit your needs. I guess you know this.
But there is one thing that would keep me from using an EntityBean-based solution. You said the external systems are updating the data. It sounds like they will have their own way to access the data and will not use the application server that runs your application. So you can not use the caching mechanism provided by the app-server (the underlying data of an entity bean might be modified externally) and so you will have an quite big overhead to create the EntityBeans each time you collect data.
But there is no argument against using a session bean (stateless sounds good) and data access per JDBC using the connection pool and declarative transaction and maybe clustering facilities provided by the app server.
Conclusion: As a fan I would prefer the EJB based solution.
Hope it helps.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!