No such thing as a small change | |
PerlMonks |
Re: Scalable application with perlby jasz (Initiate) |
on Apr 26, 2016 at 14:29 UTC ( [id://1161558]=note: print w/replies, xml ) | Need Help?? |
Here are the precise details.
well, to be precise, around 12k users connect to the website for 1.5 hrs just once in a day concurrently for taking the test. Consider it a event happening about 20 times in a year The, application framework is built with bootstrap...nothing much of aesthetic each user will be connected and the session is generated and used for the time line mentioned above the data for (multiple choice) questions retrieved from db and the user submit a choice that is stored in the users table (assuming around 12k rows and 120 columns as nothing much) with this requirement, like in uwsgi, the concurrency using threads vs process and how many r needed how db handlers in the script for each user should be implemented with threads or process? approximately what will be the system requirements on the back end to deal with the situation? if much of code is implemented on client side, the security checks in the code to be implemented are ? security rights is not a problem as the data out of this app is under trial
In Section
Seekers of Perl Wisdom
|
|