GAE is useless without being able to use MapReduce...without MapReduce you cannot do any relationships with tables of any significant size.
I get this opinion from ex-googlers. On May 6, 7:47 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > My experience is that GAE is fine if you need to store many chunks of > data (like wiki page) with very little relations to each other (no > complex references), retrieve them by key/id (no complex queries) and > are planning to have a lot of concurrent requests/second for that > data. > > GAE is slow but it scales. It scales as long as queries are simple. > You lose the ability to manipulate server-side an arbitrary large > number of records. You can only fetch 1000 records at the time. You > also risk data integrity because you have only single entity > transactions not real transactions as in a relational database. > > I use it and I like it but for web2py.com for example, with 50000 > requests/day I prefer to pay $20/month and run on a VPS. > > Massimo > > On May 6, 9:08 am, mike <michal...@gmail.com> wrote: > > > > > From my past experiences i have found GAE a little slow, is this just > > me? With web2py development what has the community found with > > deploying to GAE.
