Re: [web2py] Web-framework+db with the widest scalability?

[Keith Edmunds]

On Sun, 13 May 2012 06:21:17 -0700 (PDT), abasta...@gmail.com said:

> I suspect there wouldn't be much difference in performance 
> between the two frameworks (similarly and properly configured).

So long as this is broadly true (which I suspect it is), there are other
considerations to take into account. Suppose (unlikely) that Django is 20%
faster to run code. You also need to consider which is easier to develop
and maintain code. Any web platform, very broadly speaking, can improve
its performance by using faster hardware. That's a one-off cost. If you
determine that web2py is more efficient to develop and maintain code with,
that's a win every time anyone does any development.
-- 
"You can have everything in life you want if you help enough other people
get what they want" - Zig Ziglar. 

Who did you help today?

Re: [web2py] Web-framework+db with the widest scalability?

[Anthony]

>
> Quick semi-related question: have their been benchmark comparisons on 
> recent versions on Django when compared with recent version on web2py?
>

I'm not aware of any benchmarks directly comparing Django and web2py. If 
you were to make a comparison, you would have to be careful to make sure 
the two frameworks are doing the same work, as they do not both do all the 
same things by default (for example, in web2py, you would want to turn off 
database migrations, which are on by default, in order to get a proper 
comparison).

Specifically regarding database operations, you might expect web2py to be a 
bit faster, as the web2py DAL tends to be faster than ORMs (Django uses an 
ORM). I haven't seen direct comparison's to the Django ORM, but a couple of 
benchmarks have shown the web2py DAL to be faster than the SQLAlchemy ORM (
http://web2py.com/AlterEgo/default/show/76, 
http://static.thadeusb.com/total_time.jpg).

Aside from that, I suspect there wouldn't be much difference in performance 
between the two frameworks (similarly and properly configured). Performance 
will probably depend more on your application and server architecture and 
the database.

Anthony 

Re: [web2py] Web-framework+db with the widest scalability?

[Alec Taylor]

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
 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"  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

Re: [web2py] Web-framework+db with the widest scalability?

[Michele Comitini]

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"  ha
scritto:

> Disclosure: I have posted this on 
> stackoverflowand
> comp.lang.python
> .
>
> I am building a project requiring high performance and scalability,
> entailing:
>
>- Role-based 
> authenticationwith
>
> API-keylicensing
>  to access data of specific users
>- API 
> exposed with
>REST  
> (XML,
>JSON ), 
> XMLRPC,
>JSONRPC  and 
> SOAP
>- "Easily" configurable getters and 
> settersto 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 , 
> Web2Pyor
> Flask —would you recommend?
>
> Thanks for all suggestions
>

[web2py] Web-framework+db with the widest scalability?

[Alec Taylor]

 

Disclosure: I have posted this on 
stackoverflowand 
comp.lang.python
.

I am building a project requiring high performance and scalability, 
entailing:

   - Role-based 
authenticationwith 
   
API-keylicensing
 to access data of specific users
   - API 
exposed with 
   REST  
(XML, 
   JSON ), 
XMLRPC, 
   JSONRPC  and 
SOAP
   - "Easily" configurable getters and 
settersto 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 , 
Web2Pyor 
Flask —would you recommend?

Thanks for all suggestions