![]() This isn’t hard in practice, but may put some people off. ![]() Because GAE treats your site as an app, you need to create a skeleton configuration file even for sites that are purely static. Although a benefit a lot of the time, there is no alternative, so if you just want to make a change to a css file and upload it, you have to deploy the whole site again. This can put of non-developers, or people who want to be able to manage their site from any machine with an FTP client. To get the tools to deploy you need to download one of the backend SDK’s as a starter. So if it’s so good, why isn’t everyone using it? Well here are some cons when considering GAE for static sites. Users will see either the previous version as a whole, or the new version, but won’t end up with a mix between the two which is common when manually updating sites. ![]() Whenever you’ve made changes to your site, 1-click, and the whole site is deployed as an atomic action. When you need to, it’s easy to add a backend (Python, Java, and GO supported), as the deployment and management is identical to your static site. If you need it, GAE has inbuilt version control so you can test new versions before making them the default, and rollback to previous versions. So even without billing enabled you always get a fast response. But this isn’t an issue for a static site as the static files are hosted efficiently on other servers and delivered direct to the client. GAE usually puts your app to sleep when its not used, so a rarely hit app may need to enable billing to keep a server alive, or use other workarounds. But for a static site that causes no app containers to spin up, these limits are usually enough. ProsĪpart from the obvious benefits such as being able to scale via Google’s infrastructure, probably not the first concern for a simple static site, here are some benefits applicable to simple hosting. I often hear it mentioned when discussing JavaScript heavy single paged web apps, such as Gmail, but it’s less likely to be considered as a place to host static, or traditional multi-page sites. It seems that Google App Engine has a bit of an image problem. This provides the ability to get the availability of multiple users.Why and how to use Google App Engine to host static / multi-page sites. The XMPP API now has multi-JID get_presence.Projection queries are now a fully supported GA feature.This UI update is meant to align with this functionality. In an upcoming release applications will have multiple logical sub components, each of which will have a default version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |