> but if they are user initiated that is a lot harder. Then, don't do that. Personally, I prefer not to let users initiate background tasks/backends directly, but to launch it from a frontend instance. It's just safer that way (both security and load control). Plus, it's easier to change my underlying processing logic when there's something in between users and that data processing implementation of some kind.
On Fri, Nov 23, 2012 at 10:04 AM, Brandon Wirtz <[email protected]> wrote: >>There's also Mapreduce/Pipeline - you might wanna check that if backend > isn't solving your problem. > We use that some, but that doesn't help with things that take a long time. > If I manage them rather than choosing dynamic we can spin up and down > backends, but if they are user initiated that is a lot harder. > And there are weeks when backends will work as advertised. Then they won't. > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
