I'm using it to build REST services atop legacy data. So, it certainly can be used in a 'professional' way, whatever that means. I find that DAL is useful, and JSON and REST are easy to implement and as you say, can concentrate on the API rather than the nuts and bolts to a great extent.
If you know it and like it, why not use it? Of course you will stress test and measure, so you will have confidence that the solution will be okay with your workload. Updates you will test on a test system of course, so no risk to production. At least, no unknown risk at any rate. On Wednesday, 16 December 2015 15:02:38 UTC, 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.
