tag:blogger.com,1999:blog-3405523835306029463.post3934483742227494336..comments2010-10-29T13:46:07.562-07:00Comments on Building Java Apps on the Google App Engine: Google Cloud Vs Amazon Cloud - An architectural perspective - Part 2navaneethhttp://www.blogger.com/profile/13353327711519176349noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3405523835306029463.post-16550747517037727712010-10-29T13:46:07.562-07:002010-10-29T13:46:07.562-07:00Agreed. What I meant by pay-per-use was: "How...Agreed. What I meant by pay-per-use was: "How much you pay depends on how much you use". Yes, there are some fixed costs with AWS services like EC2.navaneethhttps://www.blogger.com/profile/13353327711519176349noreply@blogger.comtag:blogger.com,1999:blog-3405523835306029463.post-51564631147269726572010-10-26T19:35:35.735-07:002010-10-26T19:35:35.735-07:00"AWS is also pay-per-use, which means you onl..."AWS is also pay-per-use, which means you only pay as much as you use."<br /><br />This is not true in the same sense as it is on Google App Engine. With GAE, if your app is installed and available, you pay nothing if it's idle and doesn't receive any web requests. GAE will suspend your servlet container after a short period of idleness.<br /><br />With AWS you need to boot uplumpynosehttps://www.blogger.com/profile/10098634476010203590noreply@blogger.com