I want to create a service where users could remotely manage some services 
on their computers which are behind the firewall. 

Users could register their account, under their account they could register 
one or more (let's say up to 20) client computers, for each of these they 
could download a script which they could install on their computers and 
that script would periodically contact the server (for instance every 5 
seconds) and do certain things based on the response from the server. It 
would be a json-based service where the server would answer something like 
{"startSomeService": "False"} or {"startSomeService": "True", "param1": 
"aaa", "param1" : "bbb"...}. Web interface would be just a simple list of 
registered computers and their status with a few buttons for service 
management. Web interface would be made using web2py and now comes the 
tricky part:

I've calculated that if I find some 200 paying customers that could earn me 
some basic income. Let's say those 200 users each have 20 registered 
computers that would be 200x20 = 4000 json service requests within 5 
seconds, so some 800 requests per second. Or let's say I somehow manage to 
get 1000 users, that would be 20000 requests within 5 seconds, so around 
4000 requests per second or more. These would only be json requests plus 
there would be normal html requests for web interface. I am worrying if 
web2py can handle this kind of traffic and what kind of hardware would I 
need? I plan this to work on nginx web server + postgresql database 
(properly configured and indexed). Is this a feasible solution or I need to 
rethink everything over?

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to