D
Dave f
I'll be starting work on a web services interface to some internal
applications soon. They'll be implemented in WAS6 and could
potentially receive millions of hits per day. Authentication with each
request is required. The web service will essentially just turn the
XML into a Java object, authenticate, log the request, and dump it on
an MQ Series queue; and no, direct MQ-to-MQ is not an option -- a web
service is required for clients with no MQ.
As I have relatively little experience in high traffic web services, I
thought someone here might be able to suggest a place to start. Is it
cost-effective to expose a stateless EJB as a web service, should I use
a servlet, some other API? And will WAS6 clustering effectively handle
expansion as the number of requests grows? For authentication I was
considering a cached read only HashMap of users (or something similar)
to query rather than hitting the database each time; maybe updating the
cache every few minutes.
Comments, suggestions, etc. would be helpful.
Thanks.
Dave
applications soon. They'll be implemented in WAS6 and could
potentially receive millions of hits per day. Authentication with each
request is required. The web service will essentially just turn the
XML into a Java object, authenticate, log the request, and dump it on
an MQ Series queue; and no, direct MQ-to-MQ is not an option -- a web
service is required for clients with no MQ.
As I have relatively little experience in high traffic web services, I
thought someone here might be able to suggest a place to start. Is it
cost-effective to expose a stateless EJB as a web service, should I use
a servlet, some other API? And will WAS6 clustering effectively handle
expansion as the number of requests grows? For authentication I was
considering a cached read only HashMap of users (or something similar)
to query rather than hitting the database each time; maybe updating the
cache every few minutes.
Comments, suggestions, etc. would be helpful.
Thanks.
Dave