Depends on the site. If it is likely to hit the big time, GAE will repay the pain of redeveloping (getting used to the datastore, mainly) many times over. And if you aren't a sysadmin, GAE will let you sleep at night. If it does crash (and I'm sure it will, occasionally) you can sit back and let the best sysadmins on the planet handle it.
Another big issue is that currently you can switch hosting providers easily. Converting to GAE means putting your faith in Google, that they don't start being evil, and don't close down GAE on a whim. I've drunk the Kool-Aid, and like it a lot, but I have a contingency plan to migrate my app to another platform - migrating from GAE is easier than migrating to it, as long as your app isn/t popular enough to require clustered databases etc. One last thought - you'd learn a lot about GAE whilst you did the migration, which is valuable in itself. By the end, you'd be able to answer your own question... On Feb 26, 12:47 pm, Wiiboy <[email protected]> wrote: > Hi everyone, > I've got a site right now that I plan to have coded all in Python (and > Javascript, Css, etc.), hosted on a shared hosting account. It hasn't > been released yet (it's not even finished), so should I migrate it to > App Engine? > > As far as I know, I won't come close to the free quotas, so that's not > a problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
