This document provides an overview and summary of Google AppEngine for Java applications. It discusses the key features of AppEngine including supported programming languages and services, as well as limitations compared to a traditional Java environment. It also describes the process of porting an existing PetClinic application to AppEngine, including replacing Hibernate with the AppEngine datastore API and removing unsupported features. Considerations for porting to AppEngine include additional costs, vendor lock-in, and limitations of the platform compared to a traditional Java hosting environment.

1. Google AppEngine for Java enterprise applications Andrew Skiba Tikal

2. Introduction You have a typical Java web application JSP and Servlets frontend

3. Hibernate, JPA or JDBC backend

4. Spring configuration Created long before it was known about AppEngine

5. What it takes to deploy to Google servers?

6. Welcome to Pet Clinic

7. App Engine for Java Data storage

8. Web application support

9. Other services

10. JVM programming languages

11. Development tools

12. Production tools

13. It's not the same Java Not full JRE support No file system access

14. No sockets

15. No process or thread creation

16. No graphics

17. No JDBC Most of JavaEE features are not supported No EJB, JCA, JMS, JNDI Sun's COSO Simon Ph ipps slams App Engine's Java Support

18. Datastore Interface to BigTable

19. Motivation Google web indexing, Google Earth, Google Finance

20. Big data with complicated structure

21. Serialize? RDBMS don't like BLOBs BigTable! "sparse, distributed, persistent multi-dimensional sorted map"

22. Very different from RDBMS – no JOINs, no aggregations