I am building a project requiring high performance and scalability,
entailing:
- Role-based
authenticationhttp://en.wikipedia.org/wiki/Role-based_access_controlwith
API-keyhttp://en.wikipedia.org/wiki/Application_programming_interface_keylicensing
to access data of specific users
- API http://en.wikipedia.org/wiki/Application_programming_interfaceexposed
with
REST http://en.wikipedia.org/wiki/REST
(XMLhttp://en.wikipedia.org/wiki/XML,
JSON http://en.wikipedia.org/wiki/JSON),
XMLRPChttp://en.wikipedia.org/wiki/XMLRPC,
JSONRPC http://en.wikipedia.org/wiki/JSONRPC and
SOAPhttp://en.wikipedia.org/wiki/SOAP
- Easily configurable getters and
settershttp://en.wikipedia.org/wiki/Mutator_methodto create APIs
accessing the same data but with input/output in different
schemas http://en.wikipedia.org/wiki/Database_schema
A conservative estimate of the number of tables—often whose queries require
joins—is: 20.
Which database type—e.g.: NoSQL http://en.wikipedia.org/wiki/NoSQL
or DBMShttp://en.wikipedia.org/wiki/Database_management_system
—key-value data store
http://en.wikipedia.org/wiki/Key-value_data_storeor
object-relational
database http://en.wikipedia.org/wiki/Object-relational_database—e.g.:
Redis http://en.wikipedia.org/wiki/Redis or
PostgreSQLhttp://en.wikipedia.org/wiki/PostgreSQL—and
web-framework http://en.wikipedia.org/wiki/Web_application_framework—e.g.
Django http://en.wikipedia.org/wiki/Django_%28web_framework%29,
Web2Pyhttp://www.web2py.com/or
Flask http://flask.pocoo.org/—would you recommend?
--
http://mail.python.org/mailman/listinfo/python-list