In terms of scalability most framework, like web2py, all scale in the same using the same tricks. There is no scalability gain in replacing one framework for another. The bottle neck is always the database. When I optimize for production I always stick to web2py but make extensive uses of server side and client side caching. Also do not store everything in the same db and I try store nothing on files. I store user info and anything to do payments in postgres. I store some data in json using either postgres or mongo. I store sessions in redis.
On Monday, 19 September 2016 18:15:26 UTC-5, JorgeH wrote: > > Hello > > I am prototyping an app in web2py. > > My plan is to offer some software as saas. > > My question is , for the sake of having the more users (hundreds or > thousands) while in production, should I rewrite the app later in say > falcon.. and use a js framework for frontend.. or should I stick with > web2py while in production .. > > > -- 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.
