This is an interesting question, but I wouldn't exactly call tasks free: When a task executes, your instance is invoked. Tasks are really just a way of offsetting cost until later.
Jeff On Thu, Jun 21, 2012 at 11:06 AM, Michael Hermus <[email protected]> wrote: > I know there cannot be a definitive answer to this question, but I am > looking for opinions (and perhaps some insight from a Googler). > > I currently make heavy use of the task queue, and every time I am faced with > a design choice, the task queue presents a very attractive pattern for a > number of reasons. One of those reasons is that it is effectively free, > currently. This is by no means the primary factor, but it certainly has an > impact on my decision process. The obvious question: what is the risk that > Google changes its pricing model at some point and starts charging for Task > Queue API calls? > > Were that to happen, I think it would be VERY painful for my app. I don't > think it makes sense to design around a possible future pricing change, but > it concerns me quite a bit. I would love to hear what the rest of the > community thinks. > > Regards, > Mike > > -- > 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/-/ZdihbUzynk4J. > 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.
