3 ms·
Besides pricing, be sure to keep in mind some of the technical limitations with Google AppEngine. Here are two serious ones: 1) Last I checked there was still
by malandrew 16y ago
Besides pricing, be sure to keep in mind some of the technical limitations with Google AppEngine. Here are two serious ones:
1) Last I checked there was still no naked domain support. So if you plan on defaulting to http://mystartup.com/ http://mystartup.com/ instead of http://www.mystartup.com/ http://www.mystartup.com/, you might want to check if this is possible yet.
2) HTTPS support is limited to https://mystartup.appspot.com/ https://mystartup.appspot.com/. You CANNOT use https://www.mystartup.com/ https://www.mystartup.com/ last time I check. This is due to a technical limitation in SSL certificates that I'm not sure was considered at the time that Google designed the AppEngine architecture. There are ways around this, but it's messy and inelegant.
One of the great benefits of AppEngine is using it as a cache server, because if I remember correctly this is either free or really cheap. I forget the exact details of how we worked this out at my last startup, but it's worth looking into because using Google's global datacenters for caching is much much cheaper than paying for AWS bandwidth and you also get much lower latency times.