Google App Engine - Simple Introduction
2 likes748 views
This document summarizes Google App Engine, a platform-as-a-service offering from Google. It discusses how App Engine allows developers to build and host web applications on Google's infrastructure without having to manage servers. App Engine provides automatic scaling for applications and charges only for resources used. The document outlines the key services App Engine provides, including the scalable and schemaless Datastore, and demonstrates building a sample app using Python. It encourages developers to use App Engine to reduce time spent on infrastructure management and focus on their applications instead.
![Sample query
query = db.GqlQuery("SELECT * FROM FoursquareUser")
for user in query:
self.response.out.write("User name: %s" % user[“name”])
self.response.out.write("User email: %s" % user[“email”])](https://image.slidesharecdn.com/googleappengine-100608175635-phpapp02/85/Google-App-Engine-Simple-Introduction-25-320.jpg)
Google App Engine - Simple Introduction
- 1. Google App Engine An Intro, by Lenny Rachitsky
- 2. Questions
- 3. Agenda 1. Where App Engine fits 2. What is App Engine 3. How to use App Engine 4. How I’ve used App Engine 5. Q&A
- 4. “Run your web apps on Google's infrastructure. Easy to build, easy to maintain, easy to scale.”
- 5. What is “The Cloud”? “Cloud computing is a model for enabling convenient, on- demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.” -- National Institute of Standards and Technology
- 7. “The Cloud” Don’t have to build your own infrastructure Pay only for what you use Use as much as you need, whenever you need
- 8. “The Cloud” Don’t have to build your own infrastructure Pay only for what you use Use as much as you need, whenever you need Manage your infrastructure with code
- 11. Cloud Service Models IaaS (Infrastructure-as-a-Service)
- 12. Cloud Service Models PaaS (Platform-as-a-Service) IaaS (Infrastructure-as-a-Service)
- 13. Cloud Service Models SaaS (Software-as-a-Service) PaaS (Platform-as-a-Service) IaaS (Infrastructure-as-a-Service)
- 14. Cloud Service Models SaaS (Software-as-a-Service) PaaS (Platform-as-a-Service) IaaS (Infrastructure-as-a-Service)
- 15. Cloud Service Models PaaS (Platform-as-a-Service)
- 16. Overview of Google App Engine
- 17. The Pitch: You write the code, someone else worries about everything else
- 18. The Sandbox
- 19. The Sandbox Python or Java
- 20. The Sandbox Python or Java Limited access
- 21. The Sandbox Python or Java Limited access Limited run time
- 22. The Sandbox Python or Java Limited access Limited run time Datastore
- 23. The Datastore Based on “BigTable” Schemaless NoSQL, with SQL type queries Scales infinitely Means a lot less time spent on the database Maybe the best part of App Engine
- 24. Sample of Data Model “Kind” class FoursquareUser(db.Model): created = db.DateTimeProperty(auto_now_add=True) name = db.TextProperty() email = db.TextProperty()
- 25. Sample query query = db.GqlQuery("SELECT * FROM FoursquareUser") for user in query: self.response.out.write("User name: %s" % user[“name”]) self.response.out.write("User email: %s" % user[“email”])
- 26. Other services Google Accounts Mail URL Fetch Memcache Image manipulation Queues Cron jobs
- 27. Costs
- 28. Quota’s
- 30. Let’s create an app!
- 31. Demo my apps
- 32. Google I/O
- 34. Q&A
Editor's Notes
- #3: - Who here has heard of App Engine before this talk came up on the agenda? - Who here has used App Engine? - Who has something running on App Engine today? - Throw out things you’d like to get out of this talk today.
- #5: - The basic pitch - Sounds nice - How does it work? - Let’s step back and talk about the cloud in general
- #6: blah blah blah
- #7: - Basically lets you use computing resources like electricity
- #8: - The promise of the cloud, and we’re pretty much there, means...
- #9: instead of rack and stack, you click and drag
- #10: - A lot of different companies are offering cloud computing platforms. - What are the differences?
- #11: - The pundits have grouped the various cloud offerings into three service models
- #12: - Basically virtualized hardware somewhere out in the providers datacenter, where you are still dealing with servers, except you don’t have to actually deal with the hardware or support or management, and you can launch/kill servers at will
- #13: - Paas, where you don’t have to worry about servers or scaling, in exchange for being limited in what you can do in you code
- #14: - and our world of saas, which are basically web applications fully built that you don’t have to install locally
- #15: This is where each of the providers fit today...
- #16: And what we’re talking about today is Platform as a service. Google App Engine is the furthest along, but vmforce just launched and will probably be a strong offering. There are a few other popular paas services, such as Horuku and EngineYard that are Ruby on Rails based.
- #18: - Everything else = hardware, OS, scaling, databases, storage, parallelization, load balancing, queueing, account management, billing, etc.
- #19: - When you write you applications, you write them inside a sandbox environment - Means you are a bit limited in what you can theoretically do
- #20: - Can only use Python or Java, though you can run other languages that run on the JVM such as ruby, scala, and even javascript -- You can use the most common frameworks such as Django and Spring
- #21: - Limited access to underlying operating system -- can’t write to disk -- No sockets to connect to other machines. - Allows app engine to distribute your requests across multiple servers, and launch/kill servers as needed.
- #22: - Each process can take no longer than 30 seconds to run, at which point it is killed - Other limitations: -- can’t use SSL from a custom domain, database fields can’t get bigger then 1MB unless you’re using a new blob column
- #23: - basically forced to use google’s own datastore for your database
- #24: actually one of the bigger advantages of using app engine is the datastore
- #25: - equivalent of a sql style table - You create a class with each property getting mapped to the datastore automatically
- #26: Then you do a simple query very similar to how you would do it in SQL, and get back basically a hash for each table row.
- #28: - Costs are based on quota’s - There’s a quota on basically every piece of the architecture
- #29: - CPU time, bandwidth, storage, api calls, mail sent, url’s fetched, etc. - You get an amazingly generous amount free - They claim it can support 5 million page views a month at the free quota, if you use the platform the right way
- #30: - Based on the quota’s, and the sandbox, the app engine platform is tuned for “web applications”. Things like 30 second limits on processes, and inability to control your location, and pain in getting mass amounts of data in/out keep it from being great for other things. In exchange it’s really good for web apps. - Not: data mining, running a monitoring system, running exchange, managing other clouds - But that’s just today. Who knows where things will go?
- #31: enough theory, let’s create an app that queries the twitter search API and returns any tweet that matches a given search term
- #33: - Can use Speed Tracer with Google App Engine page stats - Can launch Spring powered apps to Google App Engine? - half a billion page views per day - They claim 60% of it costs are for keeping the lights on - Announced app engine for businesss -- Customers said they needed better reliability, support, key features, predictable pricing -- Domain console to help manage all app engine apps, with permissions/policies per employee -- professional support (soon) -- SLA's (soon) --- real sql, full sql, scales just as much as sql server would on its own -- SSL and SQL server (later) -- $8/user per month, up to $1000/month - Performance stats -- put is 50-100ms -- get is 10-20 ms -- index on put -- memcache is 5-10ms -- most time is spent in RPC calls waiting for traffic - audience complaints -- lack of focus on java and core issues, they think the team is being distracted focusing on the enterprise -- they want to know whether they should bet on amazon or google -- Google guy: "We're trying to take over the world" - lessons learned from lauching app engine -- keep everything configurable, you don't know how people will use your service, have knobs and dials -- "TRansparency is key, really important for developers to know whats happening"