Bonjour
I am d'accord with ernie ..
I don't know if my site is little, medium or big but with my servlets I have
on my NT ( 64 Meg and Pro 200 Mhz ) machine about 6000 hits between 8h and
20h per days, and I stop-start the service ( IIS4 + Websphere 2.02 + JDBC
DB2 OS390 ) every 100000 calls of my servlets ...
Tell me an other way to do that, faster and more efficiency ...I wait the
answer very tranquillement !!
Thank You Sun for Java and Servlets ....
CH
________________________________
-----Message d'origine-----
De : Ernie V <[EMAIL PROTECTED]>
� : [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date : dimanche 21 novembre 1999 15:15
Objet : Re: 300 Cocurrent Users
>Servlets are not the limiting factor to scalability. Architecture and the
way
>servlets are integrated into that architecture is. There is no reason why,
if
>the hardware is big enough and the load distribution schema is robust
enough,
>that you couldn't have infinite scalability using servlets.
>
>When you consider 300 concurrent users, are you referring to stateless
>sessions? Because I know of very few sites that receive 300 simultaneous
>stateless connections. If this were peak usage, this would translate to
>somewhere between 6-8 million hits per day. With volume like that it would
be
>necessary to employ multiple load balanced servers, most likely with
geographic
>dispersion with connections to multiple NAPs.
>
>Servlets are only part of the equation when it comes to constructing and
>deploying a high volume site. In large sites based on java technologies,
>servlets are used in conjunction with JSPs, they employ architectural
patterns
>such as MVC or the command pattern, where the servlet provides no business
>logic, but rather acts as the controller to the presentation --JSPs provide
the
>presentation. Back end services are typically provided by some app server,
>services are accessed using perhaps any number of technologies, including;
>JavaBeans, EJBs, CORBA, DCE, mainframe, etc.
>
>The app server is where the real heavy duty work is done. This is where you
>need facilities that can load balance, provide transaction monitoring, and
>connectivity to other high availability services.
>
>-ernie
>
>Rizwan Quadri wrote:
>
>> Hi All,
>>
>> I have read that servlets are used for small and medium size solutions,
>> and also that they cannot handle more than 300 concurrent users, though
>> i havenot used it in such large application.
>>
>> What do you think about using servlets at this level?
>> Which technology would you suggest ? why ?
>>
>> Thankyou,
>> Rizwan Quadri
>> Web Developer
>> PieNet Global
>>
>>
___________________________________________________________________________
>> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
>> of the message "signoff SERVLET-INTEREST".
>>
>> Archives: http://archives.java.sun.com/archives/servlet-interest.html
>> Resources: http://java.sun.com/products/servlet/external-resources.html
>> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
