I'm going to stop letting these through when it's my turn to moderate. Sorry for the noise.
Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Apr 15, 2011 at 10:16 AM, Calvin <[email protected]> wrote: > Okay, this time the question is worded slightly better (might want to look > at spelling though), but still doesn't really have an answer. > > I'm going to feel equally guilty for helping someone cheat, and for not > helping someone, so I'll be brief. > > The real reason to choose App Engine over a "normal 3 tier > web architecture" is that, depending on developer skill level, you will > initially have a lower cost per request. It's not that App Engine will be > more reliable (might be), or that it will be faster (probably won't be), > it's that you don't need an IT staff to maintain servers, you don't need to > plan how to scale front-end requests, or how to replicate back-end > databases. You can develop a robust application that can handle millions of > requests with a much smaller staff. Man hours are the important unit of > measurement here, not milliseconds. > > Good luck with your homework. > > -- > 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.
