The concept of "simultaneous" in a web application does not mean much. You should be able to quantity the number of http request per second, the number of dynamic http requests per second, and the number of database queries per second (per category).
One web2py instance can handle ~50 dynamic https requests if the database is not too heavy. If you need more you clone the distance behind a load balancer. This is how all web applications scale. The real problem is usually the database bottleneck. Nothing web2py specific there. All web applications have a database bottleneck. You need to write your queries properly and use caching. The particular step of accepting credit card payments is usually outsource (Stripe.com, Paypal.com, or similar) and therefore it does not provide a particular burden to application workload. Massimo On Tuesday, 1 July 2014 04:40:15 UTC-5, kanchan wrote: > > I have to develop a ecommerce software with payment gateway also in > web2py. In this more than 500 users can use and hit it simulataneously . > My query is that will software speed decrease on multiple user hits or > web2py will not comfortable for this . > -- 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.
