Thanks, I'll give Postgres a go. Quick semi-related question: have their been benchmark comparisons on recent versions on Django when compared with recent version on web2py?
E.g.: for requests per second, processing time &etc On Sun, May 13, 2012 at 10:47 PM, Michele Comitini <michele.comit...@gmail.com> wrote: > Alec, > > The database depends on what data you store and serve. It depends on your > model. Postgresql is pretty generic and scales (Skype use postgresql). > > web2py has all the required layers for your requirements and scales: just > put nginx in front of scgi, uwsgi, fcgi and use processes not threads. This > is true for any framework running on CPython. > > Flask is good also but you have a little more coding to do. > > mic > > Il giorno 12/mag/2012 10:59, "Alec Taylor" <alec.tayl...@gmail.com> ha > scritto: > >> Disclosure: I have posted this on stackoverflow and comp.lang.python. >> >> I am building a project requiring high performance and scalability, >> entailing: >> >> Role-based authentication with API-key licensing to access data of >> specific users >> API exposed with REST (XML, JSON), XMLRPC, JSONRPC and SOAP >> "Easily" configurable getters and setters to create APIs accessing the >> same data but with input/output in different schemas >> >> A conservative estimate of the number of tables—often whose queries >> require joins—is: 20. >> >> Which database type—e.g.: NoSQL or DBMS—key-value data store or >> object-relational database—e.g.: Redis or PostgreSQL—and web-framework—e.g. >> Django, Web2Py or Flask—would you recommend? >> >> Thanks for all suggestions
