Google App Engine Reviews

The public cloud is a great solution to a wide selection of problems however there are times when its use is simply not appropriate. This is typical of organisations who have specific requirements around how their data is handled, usually due to data sovereignty or regulatory compliance. However whilst the public cloud is a great way to bolster your infrastructure on the cheap (although that’s debatable when you start ramping up your VM size) it doesn’t take advantage of the current investments in infrastructure that you’ve already made. For large, established organisations this is not insignificant and is why many of them were reluctant to transition fully to public cloud based services. This is why I believe the future of the cloud will be paved with hybrid solutions, something I’ve been saying for years now.

Microsoft has finally shown that they’ve understood this with the release of Windows Azure Pack for Server 2012R2. Sure there was beginnings of it with SCVMM 2012 allowing you to add in your Azure account and move VMs up there but that kind of thing has been available for ages through hosting partners. The Azure Pack on the other hand brings features that were hidden behind the public cloud wall down to the private level, allowing you to make full use of it without having to rely on Azure. If I’m honest I thought that Microsoft would probably be the only ones to try this given their presence in both the cloud and enterprise space but it seems other companies have begun to notice the hybrid trend.

Google has been working with the engineers at Red Hat to produce the Test Compatibility Kit for Google App Engine. Essentially this kit provides the framework for verifying the API level functionality of a private Google App Engine implementation, something which is achievable through an application called CapeDwarf. The vast majority of the App Engine functionality is contained within that application, enough so that current developers on the platform could conceivably use their code using on premises infrastructure if they so wished. There doesn’t appear to be a bridge between the two currently, like there is with Azure, as CapeDwarf utilizes its own administrative console.

They’ve done the right thing by partnering with RedHat as otherwise they’d lack the penetration in the enterprise market to make this a worthwhile endeavour. I don’t know how much presence JBoss/OpenShift has though so it might be less of using current infrastructure and more about getting Google’s platform into more places than it currently is. I can’t seem to find any solid¹ market share figures to see how Google currently rates compared to the other primary providers but I’d hazard a guess they’re similar to Azure, I.E. far behind Rackspace and Amazon. The argument could be made that such software would hurt their public cloud product but I feel these kinds of solutions are the foot in the door needed to get organisations thinking about using these services.

Whilst my preferred cloud is still Azure I’m still a firm believer that the more options we have to realise the hybrid dream the better. We’re still a long way from having truly portable applications that can move between freely between private and public platforms but the roots are starting to take hold. Given the rapid pace of IT innovation I’m confident that the next couple years will see the hybrid dream fully realised and then I’ll finally be able to stop pining for it.

¹This article (http://www.theregister.co.uk/2013/05/20/newvem_analytics_for_azure/) suggests that Microsoft has 20% of the market which, since Microsoft has raked in $1 billion, would peg the total market at some $5 billion total which is way out of line with what Gartner says (http://www.arnnet.com.au/article/455595/cloud_services_market_reach_us131bn_gartner/). If you know of some cloud platform figures I’d like to see them as apart from AWS being number 1 I can’t find much else.

Google Application Engine (GAE) is a cloud computing platform for developing and hosting web applications in Google-managed data centers.

-- Frameworks --

Google App Engine was written to be language independent, however it currently supports Google-friendly languages such as Python, Java, and JVM languages, as well as Go.

GAE supports most of the Python related frameworks (Python web frameworks) as well as Google-written webapp framework and some others.

-- Massive Scalability and Pricing --
The App Engine provides application scaling for computing platforms. I consider this to be its best feature because of ever increasing data processing demands. It automatically allocates both memory and power resources to meet the growing load, bandwidth or CPU demands.

Each Google Application Engine application can use a certain amount of computing resources for free, as defined by a set of quotas. With a low bandwidth for your application on the Google AppEngine platform, the cost is zero or close to zero. If your application grows to a point where it serves millions of requests a month, at that point you will probably generate enough money to afford the increased cloud framework demands. It’s free to start – very convenient for startups. The full GAE pricing info is available here - https://developers.google.com/appengine/docs/billing

-- High Replication Datastore configuration --

Since the beginning of 2011 Google Application Engine provides High Replication Datastore configuration under which to run applications in addition to the default Master/Slave configuration. This High Replication Datastore of the App Engine is for those developers who want the highest possible level of availability for their data and applications. Such an application in data centers configuration was made possible through writing increased latency and some changes in consistency guarantees in the API. The High Replication Datastore provides a high-level, 99.95% uptime Service Level Agreement. However for low cost or non-critical applications, one can use the initial Master/Slave App Engine configuration.
Developers’ Guide and downloads

The Developers’ Guides for both Python and Java can be found here. The SDK and AppEngine downloads can be found here. I started my first application with GAE within 5 minutes using the video as a guide.

-- GAE advantages over other application cloud hostings --

Google Application Engine’s noticeable advantage over AWS or Azure is that you are charged for only the time your application is handling requests (with minimum charged time span being 15 min). Compared to the competitors, GAE’s fees for application availability to handle requests are of lower degree. So if the traffic is low (like with a startup project or something similar), application owners do not have to pay much for it.

-- Summary --
Google Application Engine is a good cloud framework supporting JAVA and Python (Google’s favorite :-) ) web development languages. It’s a nice base for launching low bandwidth projects with no money upfront. The huge advantage of the Application Engine is the automatic resource scalability so that the application can grow. The projects are allowed to consume resources up to a limit quota for free; the additional resources are nonetheless chargeable.

The original post: http://extract-web-data.com/google-application-engine-review/

There are 3 reasons I would choose to use AppEngine
1. Software is super simple and working with servers in the future is a no go.
2. Software is going to have 100+ millions users overnight. Will still need to be tweaked and optimized to handle the traffic on AppEngine. I have never seen anyone with this crystal ball but who knows you may have one.
3. Google integration is at the core of the software. AppEngine is really easy to do things like authentication with a Google account. Using Google storage or say the Google SQL service would greatly benefit from the software running inside the Google network.