aspose file tools*
The moose likes Servlets and the fly likes servlet or ejb implementation Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Servlets
Bookmark "servlet or ejb implementation" Watch "servlet or ejb implementation" New topic
Author

servlet or ejb implementation

Binoj Viswanathan
Ranch Hand

Joined: Feb 25, 2003
Posts: 85
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


SCJP 1.4(98%)<br />SCBCD1.3 (100%)<br />SCWCD 1.4 (93%)(w/o prep..n)
R K Singh
Ranch Hand

Joined: Oct 15, 2001
Posts: 5371
If data is changing very frequently, then entity bean is not a good idea as it has to create OR update bean frquently which is heavy process in bean (quite new to EJB, but this is my opnion).
I think you should go for normal bean.
CMIW
HTH


"Thanks to Indian media who has over the period of time swiped out intellectual taste from mass Indian population." - Chetan Parekh
Binoj Viswanathan
Ranch Hand

Joined: Feb 25, 2003
Posts: 85
Hi,
The external system (a converter which reads data in XML format) is also part of the same application (i.e. in same application server cluster) but independent of main syatem. The converter reads the �dynamic data� from content source (XML format) and converts it and inserts into the database. Static data is not going to the system database. The converter sends directly to the XML repository. An application component reads it from XML repository and sends to the mobile users.
The clients (mobile phones/PDAs) request for the latest data. (There may be thousands of users at time). The main system reads the data from DB and sends to the client as per the request. The rate of change of dynamic data is so high in peak season. Millions of data inserted into the database.
thanx binoj
friso dejonge
Ranch Hand

Joined: Jul 11, 2002
Posts: 162
hi,
try a stateless session bean on the appserver.


swimming certificate (A & B), shoelaces diploma, and some useless java ones.
Asher Tarnopolski
Ranch Hand

Joined: Jul 28, 2001
Posts: 260
personally i think you can use servlets with a well made connection pooling of database...


Asher Tarnopolski
SCJP,SCWCD
friso dejonge
Ranch Hand

Joined: Jul 11, 2002
Posts: 162
i agree you can use servlets. However if you have an ejb container, you might as well use it.
Since your query will invoke a lot of work, you can devide the workload onto adifferent server, and reduce the workload on the servlet container.
praveen patil
Greenhorn

Joined: Mar 03, 2003
Posts: 9
hi,
u need to use only servlets which
will serve ur purpose. i think u
must be using some webserver rather
than app. server. if i m right, then
go ahead with servlets only. if u r
sending any dynamic data frm ur PDA/mobile
then u need to think of EJB, provided
appn. is distributed (MAN).
Praveen
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Originally posted by friso dejonge:
i agree you can use servlets. However if you have an ejb container, you might as well use it.
Since your query will invoke a lot of work, you can devide the workload onto adifferent server, and reduce the workload on the servlet container.

That's not a good reason to use EJB. You can get workload management by spraying HTTP requests across a number of web containers that would work just as well, if not better (less additional network traffic).
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: servlet or ejb implementation