1. Google AppEngine for Java enterprise applications Andrew Skiba Tikal

3. Hibernate, JPA or JDBC backend

5. What it takes to deploy to Google servers?

6. Welcome to Pet Clinic

8. Web application support

9. Other services

10. JVM programming languages

11. Development tools

12. Production tools

14. No sockets

15. No process or thread creation

16. No graphics

20. Big data with complicated structure

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

24. Google proprietary

28. Response time outs

30. Good old web.xml (with limitations)

31. HTTPS is supported

32. Security constraints supported with serious limitations

34. Debug a desktop application

35. Deploy an AJAX web application

36. Fully supported on AppEngine

40. Low-level API

43. Registered user

45. Handled by servlets

50. Scala

51. Jython (finally: Python on AppEngine :-)

53. BeanShell

54. CAL

56. Debug locally

57. Validate

61. Run development server

62. Deploy

64. Quota Details

65. Logs

66. Cron Jobs

68. Data Viewer

70. Developers

71. Versions

73. Billing History

74. Porting PetClinic to AppEngine

77. Java DataStore API much less effective than Python one

80. Not full Java spec support

81. Response timeouts

82. Authentication only by Google accounts

84. Backup

87. Unusual database

89. http://code.google.com/appengine/community.html

90. Project demos

91. http://code.google.com/p/googleappengine/source/browse/#svn/trunk/java/demos

92. Will it play in AppEngine?

93. http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine

94. JRE white list

95. http://code.google.com/appengine/docs/java/jrewhitelist.html

96. BigTable white paper

97. http://labs.google.com/papers/bigtable-osdi06.pdf

98. Questions?