Living in the Cloud: Hosting Data & Apps Using the Google Infrastructure
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Living in the Cloud: Hosting Data & Apps Using the Google Infrastructure

on

  • 3,485 views

In the modern web, the user rules. Nearly every successful web app has to worry about scaling to an exponentially growing user base and giving those users multiple ways of interacting with their data. ...

In the modern web, the user rules. Nearly every successful web app has to worry about scaling to an exponentially growing user base and giving those users multiple ways of interacting with their data. Pamela Fox, Maps API Support Engineer & Developer advocate, provides an overview of two technologies - Google App Engine and the Google Data APIs - that aim to make web development and data portability easier.

Statistics

Views

Total Views
3,485
Views on SlideShare
3,479
Embed Views
6

Actions

Likes
1
Downloads
39
Comments
0

1 Embed 6

http://www.slideshare.net 6

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Living in the Cloud: Hosting Data & Apps Using the Google Infrastructure Presentation Transcript

  • 1. Living In The Cloud
    • Hosting Data & Apps Using The Google Infrastructure
  • 2. Introductions
    • Pamela Fox USC/Google
    http://www.wordle.net/gallery/wrdl/710650/fkedupmonkey_tags
  • 3. The Cloud!
  • 4. Tonight’s Agenda
    • Google Data APIs
    App Engine
  • 5. Before the Cloud: Web Apps
  • 6. After the Cloud: Web Apps
  • 7.
    • Viral Spread + User Edits = Scaling Nightmare
    Mo’ Users, Mo’ Problems
  • 8. Old Architecture code/data
  • 9. Old Architecture
  • 10. Old Architecture
  • 11. Old Architecture
  • 12. Solution: App Engine
  • 13. What Is App Engine?
    • Lets you run your web application on top of Google’s infrastructure.
    • Servers
    • Network
    • Datastore
    • Backups
    • Pagers
    “ We wear pagers so you don’t have to.” — Guido van Rossum Scalable }
  • 14. App Engine Architecture code data
  • 15. Simple, Automatic Scaling
  • 16. App Engine Components code data
  • 17. Python
  • 18. Data Store
  • 19. Data Store db.GqlQuery(&quot;SELECT * FROM Shout &quot; &quot;WHERE who >= 'b ' AND who < ' c ' &quot; &quot;ORDER BY when DESC&quot;).fetch(100) query = Shout.all() query.order('-date') query.filter('who >=', 'b') query.filter('who <', ‘c') shouts = query.fetch(100)
  • 20. Memcache
  • 21. Users @gmail.com @myappsdomain.com
  • 22. Demo
    • Google App Engine
  • 23. Before the Cloud: User Apps
  • 24. After the Cloud: User Apps
  • 25.
    • Users demand ownership of their content.
    • Other sites want to access that content.
    Damn Needy Users
  • 26. Solution: Google data APIs
  • 27. How Do You Make Things Accessible?
    • An application programming interface (API) is a set of functions, procedures, methods or classes that an operating system , library or service provides to support requests made by computer programs .
    • Source: Wikipedia
    A pplication P rogramming I nterface ( )
  • 28. APIs
    • RPC || REST
    • * SOAP
  • 29. Remote Procedure Calls fooInstance->addNumbers(2, 3); <?xml version=&quot;1.0&quot;?><methodCall> <methodName>Foo.addNumbers</methodName> <params> <param> <value><int>2</int></value> <value><int>3</int></value> </param> </params></methodCall> fooInstance.addNumbers(2, 3); PHP XML (Network) C++
  • 30. REST [Fielding 2000] Re presentational S tate T ransfer ( )
  • 31. REST
    • Fundamentals of REST:
    Application state and functionality is abstracted into discrete resources .
  • 32. REST
    • Fundamentals of REST:
    Resources are accessible via URLs . /blog/posts/1234
  • 33. REST
    • Fundamentals of REST:
    Resources share a uniform interface for transferring state . HTTP:// } GET POST PUT DELETE
  • 34. RSS/ATOM Feed { Entries Example RSS feed.
  • 35. ATOMPub Feed { Entries GET POST PUT DELETE
  • 36. Google data APIs Protocol Feed Query { Entries GET POST PUT DELETE
  • 37. The Google Data Protocol REST Google Data Protocol RSS 2.0 Architecture Syndication Updates AtomPub Atom
  • 38. The Google Data Protocol RSS 2.0 Atom(Pub) Google Data Syndication Format ✓ ✓ ✓ Queries ✓ Updates ✓ ✓ Optimistic Concurrency ✓ Authentication ✓
  • 39. The Google Data Protocol Over 15 APIs, 1 Protocol Many Uses
  • 40. Case Study: CalGoo
  • 41. The Google Data Protocol
    • GET /myFeed
    • 200 OK
    • <?xml version=&quot;1.0&quot;?>
    • <feed xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <title>Foo</title>
    • <updated>2006-01-23T16:25:00-08:00</updated>
    • <id> http://www.example.com/myFeed </id>
    • <author>
    • <name>Jo March</name>
    • </author>
    • <link href=&quot;/myFeed&quot; rel=&quot;self&quot;/>
    • </feed>
    Requesting a feed or resource
  • 42. The Google Data Protocol
    • POST /myFeed
    • <?xml version=&quot;1.0&quot;?>
    • <entry xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <author>
    • <name>Elizabeth Bennet</name>
    • <email> [email_address] </email>
    • </author>
    • <title type=&quot;text&quot;>Entry 1</title>
    • <content type=&quot;text&quot;>This is my entry</content>
    • </entry>
    Creating a new resource
  • 43. The Google Data Protocol
    • 201 CREATED
    • <?xml version=&quot;1.0&quot;?>
    • <entry xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <id> http://www.example.com/id/1 </id>
    • <link rel=&quot;edit&quot; href=&quot; http://example.com/myFeed/1/1/ &quot;/>
    • <updated>2006-01-23T16:26:03-08:00</updated>
    • <author>
    • <name>Elizabeth Bennet</name>
    • <email> [email_address] </email>
    • </author>
    • <title type=&quot;text&quot;>Entry 1</title>
    • <content type=&quot;text&quot;>This is my entry</content>
    • </entry>
    Creating a new resource
  • 44. The Google Data Protocol
    • PUT /myFeed/1/1/
    • <?xml version=&quot;1.0&quot;?>
    • <entry xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <id> http://www.example.com/id/1 </id>
    • <link rel=&quot;edit&quot; href=&quot; http://example.com/myFeed/1/1/ &quot;/>
    • <updated>2006-01-23T16:28:05-08:00</updated>
    • <author>
    • <name>Elizabeth Bennet</name>
    • <email> [email_address] </email>
    • </author>
    • <title type=&quot;text&quot;>Entry 1</title>
    • <content type=&quot;text&quot;>This is my first entry.</content>
    • </entry>
    Updating an entry
  • 45. The Google Data Protocol
    • 200 OK
    • <?xml version=&quot;1.0&quot;?>
    • <entry xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <id> http://www.example.com/id/1 </id>
    • <link rel=&quot;edit&quot; href=&quot; http://example.com/myFeed/1/2/ &quot;/>
    • <updated>2006-01-23T16:28:05-08:00</updated>
    • <author>
    • <name>Elizabeth Bennet</name>
    • <email> [email_address] </email>
    • </author>
    • <title type=&quot;text&quot;>Entry 1</title>
    • <content type=&quot;text&quot;>This is my first entry.</content>
    • </entry>
    Updating an entry
  • 46. The Google Data Protocol
    • DELETE /myFeed/1/2/
    • 200 OK
    Updating an entry
  • 47. Demo
    • Google Data CRUD
  • 48. The Google Data Protocol
    • GET /myFeed?q=This
    • 200 OK
    • <?xml version=&quot;1.0&quot;?>
    • <feed xmlns=&quot; http://www.w3.org/2005/Atom &quot;>
    • <title>Foo</title>
    • <updated>2006-01-23T16:26:03-08:00</updated>
    • <id> http://www.example.com/myFeed </id>
    • <link href=&quot;/myFeed&quot; rel=&quot;self&quot;/>
    • <entry>
    • <id> http://www.example.com/id/1 </id>
    • <link rel=&quot;edit&quot; href=&quot; http://example.com/myFeed/1/1/ &quot;/>
    • <updated>2006-01-23T16:26:03-08:00</updated>
    • <title type=&quot;text&quot;>Entry 1</title>
    • <content type=&quot;text&quot;>This is my entry</content>
    • </entry>
    • </feed>
    Searching for a resource
  • 49. Demo
    • Youtube Searcher
  • 50. JSON and RSS
    • Other formats are also supported:
    ?alt=json ?alt=json-in-script ?alt=kml ?alt=rss
  • 51. Client Libraries
    • PHP
    .NET Java JavaScript Objective-C Python + Community Contributed
  • 52. Demo
    • Google Data Sample Applications
  • 53. My Secret Motivation For Giving This Talk
    • Google Data APIs
    • App Engine
  • 54. Demo
    • Google Data APIs + App Engine
  • 55. Conclusion
    • Google Data APIs
    App Engine Scalable Architecture (AtomPub) APIs
  • 56. Questions? Pamela Fox [email_address] @pamelafox More Info http://code.google.com ↶