Laxmikant Kumbhare wrote:I mean if multiple users (lets assume 100 users) use it simultaneously, will it work properly?
If it is written properly. The idea of a framework is to make it easier for you to do the right thing (and provide features so you can develop faster.)
Laxmikant Kumbhare wrote:I am just using JSP servlets and JDBC but declaring all variables local in JSP and Servlets too.
This is not the right thing. JSPs should not have variables/Java code (although they are thread safe). For Servlets, local variables are threadsafe; instance variables are not.
I once wrote a web-app that about 200 odd user had to log in with - using access as a back end database (it was just a fun app - for our office-group). Access wasn't able to scale and broke soon as the load got more than 40-50 user. I had to switch to oracle.
but for someone who has
I'd say look out with those 100 users for sure! (By the way I'm not sure what local means here - I assumed 'instance-variables')
I am just using JSP servlets and JDBC but declaring all variables local in JSP and Servlets too.
- X 3
Frameworks can help with many of the common tasks, but are by no means necessary
Whether or not it will work properly depends more upon your code than a framework.
Only way is to really try load testing it and see.
A tool like JMeter might help you with that.