Overview of GAE
Google App Engine or GAE or App Engine is a public platform as a service (PaaS), one of the service models of cloud computing as described by the NIST definition of Cloud computing. GAE was developed by Google and was made available for public usage in 2008. Its stable release is 1.8.2 in July 2013. GAE is written in Python, Java, Go, and PHP. GAE provides facility to develop and host applications in resources managed by Google. Entry level usage has certain restriction with free tier. App Engine provides free tier to get started. All applications can use up to one GB of storage and sufficient CPU and bandwidth to support a resourceful application serving around five million page views a month.
GAE supports Java, Python, Go, and PHP. It also supports other JVM languages such as Clojure and PHP via a special version of Quercus, JRuby, Groovy, and Scala by extension. GO and PHP are not in full fledged mode, they are in experimental phase. GAE makes it simple to build an application that is highly available and reliable even under huge demand with vast amounts of data requests. It provides automatic scaling and load balancing, persistent storage, full support for common web technologies, APIs for authenticating users and sending email using Google Accounts, full featured simulation of Google App Engine on your local development environment, scheduled tasks, and task queues.
In GAE, applications run in a secure environment that provides limited access to the core resources. This sandbox isolates applications in its own highly available, reliable, secure environment that is independent of the compute resources.
- Only HTTP request execution is allowed
- Only pure-Python can be uploaded
- Does not support session affinity
- Access to virtual file systems only and read-only access available to the filesystem on App Engine
- Does not support domains without www such as http://clean-clouds.com
- Java applications may only use a subset of the classes from the JRE standard edition
- In-equality filters on two or more entity properties per query is not allowed in datastore
- Minimum request processing time is 60 seconds
Spring Framework, Apache Struts 1, Struts 2 with some changes, Servlet 2.5 technology using the open-source Jetty Web Server, JavaServer Faces with some changes. Java runtime environment uses Java 7. The limits of the sandbox environment are implemented in the JVM.
Framework that supports the WSGI using the CGI adapter can be used to create an application on GAE. Django, GAE framework, CherryPy, web2py and webapp2, Flask, Pyramid, etc. It includes the Python standard library with limitations imposed by sandbox environment. webapp2 Python web application framework is available for creating applications with ease.
Data Storage in GAE
· Distributed NoSQL service
· Entities have a set of properties that support retrieval of Entities with specific requirements
· Schemaless Entities
· Python datastore and Java JDO/JPA interfaces interface are used for applying and enforcing datastore structure within application
· Supports query engine and transactions
· ACID transactions and efficient concurrency control
Google Cloud SQL
· Fully managed relational database service in Google’s cloud
· Capabilities of a popular MySQL database
· Administration, Management, and Monitoring of Database
· Built in backup, recovery and patch management as it is managed by Gogle and not users
· Built in replication across multiple geographic regions
· GUI to create, manage, configure, and monitor your DB instance
· Many options for configuration are available
Google Cloud Storage
· RESTful service for storing, managing and accessing data with web-based interface
· Reliable, Highly Available, Scalable Object Store
· Data replicated across multiple data centers.
· Read-your-writes data consistency
· Support to objects can be terabytes in size, resumable uploads and downloads
· OAuth 2.0 Authentication
· Efficient access controls for individuals, projects and group-level
· Authenticated uploads and downloads
· Project, Buckets-Containers, and Objects-Data are basic building blocks of data
Setup Eclipse and Configure Google Plug-in for Eclipse
Download Eclipse IDE for Java EE Developers from http://www.eclipse.org/downloads/
Install Google Plug-in for Eclipse and follow instructions given at: http://code.google.com/eclipse/docs/install-eclipse-3.6.html
Figure 1– GAE Plugin Installation in Eclipse
Next -> Review Items to be installed
Next -> Review Licenses – Select the radio button – I accept the terms of License Agreement – Click Finish
It will take some time to install GAE environment in your local system.
Click New-> Select Google -> Select Web Application Project
Figure 2– Google Web Application Project
Deselect Google Web Toolkit from Google SDKs Section
Figure 3– Google SDK settings for Web Application
Figure 4– Web Application Structure for GAE
It is a normal web application structure and the only difference is appengine-web.xml
Table 1– appengine-web.xml Structure
<?xml version=”1.0″ encoding=”utf-8″?>
Allows Google App Engine to send multiple requests to one instance in parallel:
<!– Configure java.util.logging –>
<property name=”java.util.logging.config.file” value=”WEB-INF/logging.properties”/>
Now just open http://localhost:8888in browser
Figure 5– Local Environment of GAE
Click on GAETest to run it in local environment
Figure 6– Execution of GAE Application in Local Environment
Deploy Sample Hello, Open Source For You web application on GAE
Figure 7– Deploy Application to GAE from Eclipse
To deploy it on GAE, Authentication is required.
Provide username and Password in a new window.
Accept the terms of service and privacy policies.
If Application ID is not set then Deployment process will give error: “GAETest does not have an application ID”
To create an application Id -> Open https://appengine.google.com Login and Create New Application ID
Figure 8– Create Application Identifier for GAE Application
Click on Create Application. It will give message “Application Registered Successfully” if all goes well.
To proceed further, Click on the project settings link in the same dialog box.
Figure 9– Provide Application Identifier in Eclipse Properties
Click ok and Application ID error will be solved. Now Click on Deploy.
Figure 10– Deploy Project to GAE
Once the deployment Process will complete, Console output will be like:
Table 2– Deployment Output from Eclipse
———— Deploying frontend ————
Preparing to deploy:
Created staging directory at: ‘C:UsersadminAppDataLocalTempappcfg1977774409461224969.tmp’
Scanning for jsp files.
Scanning files on local disk.
Cloning 2 static files.
Cloning 23 application files.
Uploading 3 files.
Uploaded 1 files.
Uploaded 2 files.
Uploaded 3 files.
Sending batch containing 3 file(s) totaling 4KB.
Deploying new version.
Closing update: new version is ready to start serving.
Uploading index definitions.
Deployment completed successfully
Now let’s verify the GAE dashboard and verify the status of newly deployed application:
Figure 11– Application Status in GAE Dashboard
Let’s run the application:
Figure 12 – Available Servlets for an App in GAE
Figure 13 – Web Application in GAE Environment
GAE vs AWS
Yes (Extra Charge)
Programming Language Supported
Free of cost for limited usage, and trial
Free Tier for 1 Year. User needs to provide Credit Card details
Less considering PaaS
More considering IaaS
Published in OSFY.