Also, I think at some point in the near future, GAE is supposed to be offering a MySQL option. Anthony
On Monday, May 16, 2011 7:29:47 PM UTC-4, howesc wrote: > Marek, > > did you see google's announcements last week? sometime this summer they > will offer app engine with SLA and all the real stuff that production > likes... > > i have interchanged in testing web2py code on GAE and RDBMS. though once i > get into it i do my database layout differently and write my code > differently to work with GAE. I am still confident that my code will run on > an RDBMS, though perhaps not as efficiently as if i had written for the > RDBMS. > > the updates to google's files API look to be quite nice - you can read, > manipulate, and write files to the blobstore now as if blobstore records > were files. i have not used this feature yet, but suspect i will soon. > > i have not built a RDBMS app and then deployed to GAE, but what i can tell > you is that i have *never* worked with a platform that has scaled as well as > GAE. even when my code was inefficient as long as we paid google they run > it so no customers experienced an outage while i fixed my code. > > 2 examples of GAE usage that i have worked on: www.elizabethscanvas.org is > all GAE, even the artwork images that are contributed by members are in the > GAE blobstore, and if you have an iOS device look for 'starmaker' the app > communicates via an API to a web2py/GAE database backend. the former has > low traffic so far, the latter has had spikes at various times since its > release. > > GAE is not the be-all-end-all, but if you are doing a web-based read > intensive application it's a strong option. > > christian >
