Friends, assuming a hypothetical application .. If I have a large multiuser and monolithic application .. with the growing of it (more clients, more concurrent accesses) .. I have some doubts ..
For example search and report screens: 1) If I ask to fetch records and fill a table with 200 records, this query takes too much time and enough server resources .. How to optimize this type of question? Make the application scalable and also support several accesses, queries, ultimately users using it .. Is it feasible to consider a REST application? Are there optimizations to be made when moving from the development environment to the production environment when using web2py? I wanted your opinions on these issues, because over time and growing from the database, returning 'full' html (we use this term for non-REST or monolithic applications) becomes cumbersome and slow .. Hugs and keep loving python! <3 -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
