>From the general gist of comments here and at I/O, plus lingering major issues (http://code.google.com/p/googleappengine/issues/detail?id=965), I wouldn't plan to switch away from Amazon SES anytime soon.
I wouldn't interpret this as a major strike against appengine - after all, if you were developing on EC2, you'd still be using... SES. Nothing really wrong with that. I'd rather the GAE team concentrate on issues that can't be trivially solved by outside services. Jeff On Wed, May 25, 2011 at 3:38 PM, JH <[email protected]> wrote: > I'm wondering if the reduction in mail.api quota + app engine leaving > preview means that the mail service will get an upgrade, and we will > have higher deliverability, or if I should continue using Amazon SES > for my email needs. > > On May 12, 2:14 am, Kenneth <[email protected]> wrote: >> Greg mentioned he was putting together an FAQ so let's help him out! >> >> If you're going to answer this just put in your question into a single line, >> let's not try and answer them here or give opinions, there's plenty of other >> threads for that. I do understand that Google doesn't have answers to some >> these. >> >> Here's my list: >> >> 1) What is the time granularity of the instance pricing? ie if I have an >> instance up for 5 minutes, what am I charged, $0.08 / 60*5? >> 2) Will I be able to tune the scheduler myself, ie set it to performance or >> low cost, Will I be able to limit the min or max number of instances >> created (with the obvious impact on user experience)? >> 3) Python concurrency, will this require any code changes, do you have any >> estimates based on your testing of the number of well behaved requests per >> second a single instance will be able to handle for a given framework? >> 4) Database charges, when can you give us more details over what Max gave in >> the other thread, are you charging for deletes, what do you expect the ratio >> to be between the new pricing metric and the Datastore API calls metric we >> have today? >> 5) Will you be charging differently for instances that use different amounts >> of memory, since this seems to be the cost that you're going after that >> isn't charged for in the current model. >> >> Thanks, >> Kenneth > > -- > 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.
