I agree with Villas. The larger the development the more the database becomes the bottleneck and the framework irrelevant.
Massimo On Nov 13, 8:35 am, villas <[email protected]> wrote: > Hi Jason > > I guess you have to define 'large deployment' first of all. Number of > records and size of DB? Number of concurrent users? Large data model > or number of forms etc? Number of servers -- or replication? Global > coverage? > > In principle I don't think there's any reason why Web2py would be > worse than other frameworks. Usually it is much better! As an > example, I think deploying to the Google App Engine should be able to > scale sufficiently for everything but extreme cases :) > > If you specify more about what you wish to achieve this group may be > able to give more specific advice how best to organise your project. > > -D > > On Nov 13, 7:12 am, Jason Brower <[email protected]> wrote: > > > I love web2py and it's the only framework i feel i am fully capable to do > > or learn to do quickly. > > However, I remember see that this framework is intended for small to medium > > sized deployments. Is this true? What is it that stops us from larger > > deployment? Should i pickup django because i may need it? > > Regards, > > jb > >
