running your apps. • Uses Google’s infrastructure • A *.appspot.com domain (customized domain name is fine) • Compromises Python or Java runtime • Provides APIs to access storage and services • Scales on demand • Pay as you need
of Key-Value database built on GFS. • Scalable • Access through Datastore API or GQL • Dynamically add/remove -ing properties is okay. Relational Database Datastore
transform, … an image • Mail Service • Send/Receive Emails • Task Queue Service • Put tasks in queue and execute them later (avoid exceeding quota limit) • User Service • Authentication user with Google account (or OpenID)
enabled • Types of quotas • CPU time • The capacity of data storages • The bandwidth of incoming/outgoing request/responses • The frequency of API calls • Limits • 1MB data entity (datastore, blobstore, memcache) • 30 sec. lifetime of a request • URL Fetch: 32MB data and 10 minutes • Image service: 1600px image • …
into the Google Apps. • If you want to use a custom domain name for the app, you should use that domain to register Google Apps. • Authenticate Google Apps’ users. • Sell your app on the Google Apps Marketplace.
contains 2 files: • app.yaml • main.py • Start the development server, it servers http://localhost:8080 Start the dev server Use this URL test your app
application. • Learn how to use Datastore API • Learn the webapp framework and template • Use User service for authentication • Access data offline • Attachments: • blank.zip: The blank project directory. • gbook-1.zip: The website flow and URL routings • gbook-2.zip: Design the data models • gbook-3.zip: Authenticate with Google account • gbook-4.zip: Use template for output