I have pretty much come to the same conclusion. For this I think I'll have
to go to AWS. I just wanted to make sure that I didn't miss any clever
little detail that would suddenly make it all possible and so much more
elegant on AppEngine. This has happened to me before several times,
especially when it came to transactions, queries, etc. in the datastore.

None-the-less, a limit of 6 concurrent requests on a back just seems
ridiculously little, no? Especially if you take into account the fact that
backends were specifically designed for long-running requests. Let's say
you only use the backend to quickly compile a report for the client by
spidering a whole bunch of pages, i.e. long time, but virtually no CPU use,
you could only service 6 of these requests simultaneously, unless you want
to somehow slice up the tasks and write your own scheduler to interleave
their execution...

Backends seem like they aren't fully thought through yet... At least not as
much as the rest of GAE.

--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/Z-6xX4RUFewJ.
To post to this group, send email to google-appengine@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
google-appengine+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.