------------------
Honestly, the types of prices you are flagging here are pretty
concerning, even at the low end, and I can see it becoming
uneconomical very quickly once you add a few of these services on to
your account. I'd expect a substantial improvement in performance to
go along with these prices.
It moves well away from the metered billing approach that is used now.
At the very least I'd like to see some packaging of these advanced
capabilities at a discount instead of getting nickeled and dimed for
them individually.
As a GAE/J dev, it would lead me to seriously consider porting my app
to EC2/Beanstalk or other alternatives. When it is more cost effective
to run 4-5 instances 24/7 on EC2 (even if they are idle half the time)
than run my app on GAE then your doing it wrong.
------------------
-James
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
As much as possible I'd like google to continue to bill on usage
instead of flat fee because when starting a startup, it makes it
easier to manage finance.
What I love about app engine now as a bootstrapped company, is that my
infrastructure cost grow at the same pace as my income.
For exemple, the backup, instead of doing 100$ a month (or else) it
would be nice to be x.xx$ per backup Go.
Thanks,
Jeremi
3) For, HTTPS, Google is already charging extra for secure requests.
Why separate billing ?
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.