Tornado is mostly a web server. You can use tornado with web2py. In fact we use tornado in web2py in the
gluon/contrib/websocket_messaging.py. Of course web2py adds overhead because it parses the header, handles language preferences, sessions, database connections, templates. Etc. You would get the same overhead in tornado if you add those functionality. If you build a minimalist webapp that does lots of caching and no (or rare) db connections, than tornado is faster. Massimo On Wednesday, 16 December 2015 09:02:38 UTC-6, desta wrote: > > I am thinking of using web2py to build a REST API project. I believe that > features like authentication and authorization will save me a lot of > development time and I will be able to focus on building the API. I already > know that web2py is a great and reliable platform but I would like to hear > your opinion whether web2py is suitable for a professional level API. > > I am wondering whether the overhead of using web2py as compared to using > Tornado for example will cause me problems in terms of performance. Another > thing that I consider is the updating. In one of my previous projects, a > web2py update 'broke' the application and if it was live it would have > caused me a long downtime. > > Thank you for reading and I am looking forward for your comments. > -- 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.
