Download as PDF, PPTX
More Related Content
Similar to App Engine overview (Android meetup 06-10)
App Engine overview (Android meetup 06-10)
- 1. Using App Engineto power your native Android applications Jason Cooper Developer Programs Engineer jasonacooper@google.com
- 2. What is AppEngine?
- 3. Spectrum of cloud-basedservices IaaS Infrastructure as a Service
- 4. Spectrum of cloud-basedservices SaaS Software as a Service IaaS Infrastructure as a Service
- 5. Spectrum of cloud-basedservices SaaS Software as a Service PaaS Platform as a Service IaaS Infrastructure as a Service
- 6. Spectrum of cloud-basedservices SaaS Software as a Service PaaS Platform as a Service IaaS Infrastructure as a Service
- 7. Sandbox restrictions Applications cannotcurrently: open a socket or access another host directly spawn a sub-process or thread make other system calls write to the filesystem Python applications cannot include C extensions or other code that must be compiled. Java applications cannot use unapproved JRE classes.
- 8.
- 9.
- 10. Components Python, JVM Runtimes Local Admin SDK Console Scalable Infrastructure Linux, GFS, Bigtable, custom hardware
- 11. Components Local Admin SDK Console
- 12. Google Plugin forEclipse
- 13. Admin Console http://appengine.google.com
- 14. System Status http://code.google.com/status/appengine
- 15.
- 16. Setting up a(scalable) app is hard!
- 17. Setting up a(scalable) app is hard! Initial setup servers networking load balancers software licenses Maintenance patches upgrades Forecasting traffic utilization TIME! MONEY!
- 19. "Run your appson Google's scalable infrastructure"
- 20. Easy to use,scale, and manage
- 21. Scale dynamically andautomatically App App’s Use Engine Runtime r Frontend
- 22. Scale dynamically andautomatically App App’s Use Engine Runtime r Frontend
- 23. Scale dynamically andautomatically Use Use r r App App’s Use Engine Runtime r Frontend Use r Use r
- 24. Scale dynamically andautomatically Use App’s Use r Runtime r App App’s Use Engine Runtime r Frontend App’s Runtime Use r Use r
- 25. Scale dynamically andautomatically Incoming requests App Engine App Engine App Engine Front End Front End Front End Load Balancer AppServer AppServer AppServer
- 26. Free quota Every AppEngine application receives the following at no cost: 6.5 CPU hours per day 1.0 GB incoming bandwidth per day 1.0 GB outgoing bandwidth per day 1.0 GB storage (data + indexes) 2,000 emails sent per day
- 27. Purchase resources asneeded
- 28.
- 29.
- 30.
- 31. Datastore design Distributed Bigtable + entity groups ACID transactions Optimistic concurrency Entities + indexes Protobuf encoded entities
- 32. Datastore properties Core value types string integer floating point datetime boolean Composite value types users.User db.Email ... Lists (multi-valued) Text and binary blobs References (keys)
- 33. Datastore - what'sfamiliar? Indexes ACID transactions GQL (SQL-like syntax): db.GqlQuery(''' SELECT * FROM Story WHERE title = 'App Engine Launch' AND rating >= 10 ORDER BY rating, created DESC ''')
- 34. Datastore - what'sdifferent? No inner, outer, or natural joins Dense index scans Per-entity metadata Soft schema (no DDL!) Queries as object syntax: q = Story.all() q.filter("title =", 'App Engine Launch') q.filter("rating >=", 10) q.order("-rating") q.order("-created")
- 35. Bigtable queries 1. Scanrows 2. Pre-generate index tables 3. Each index row "points" to entity
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. Querying geospatial data Latitudesand longitudes can't be queried separately in ranges. More and more solutions use geohashes or geocells to do geospatial queries. Examples: GeoModel http://code.google.com/p/geomodel/ http://code.google.com/p/javageomodel Supports both bounding-box and proximity queries mutiny http://code.google.com/p/mutiny/ Sample: http://mutiny.appspot.com geodatastore http://code.google.com/p/geodatastore/
- 43. Thanks! Jason Cooper Developer Programs Engineer jasonacooper@google.com