4 ms·

I'd stay away from GAE, personally. The lockin is not worth the benefits, though you will certainly find lots of happy GAE customers. The big thing is that G

I'd stay away from GAE, personally. The lockin is not worth the benefits, though you will certainly find lots of happy GAE customers. The big thing is that GAE is only suitable for certain types of apps, so make sure your's is one of those before even starting. The one small, hobby app I wrote for GAE was unsuited and it was a painful process to port away. My company, with a real GAE app, has a cost threshold where we know it's cost effective to move from GAE; write heavy apps are expensive in the GAE environment. Each day we inch closer to that threshold. At this point the headaches of using GAE are more than the headaches of not using GAE, but I won't miss it when we pull the trigger on moving away.

rbanffy 13y ago
> The lockin is not worth the benefits, though you will certainly find lots of happy GAE customers. > My company, with a real GAE app, has a cost threshold where we know it's cost effective to move from GAE These guys may help: http://www.appscale.com/ http://www.appscale.com/
- pekk 13y ago
  If you can afford that deployment, otherwise you have to rewrite most of your code to get off the platform
  - rbanffy 13y ago
    I don't think the cost of deployment is that relevant when compared to the cost (and risks) of a rewrite. If your app is written in Java, I believe http://www.jboss.org/capedwarf http://www.jboss.org/capedwarf is another option.