InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Google Data API (GData)

Posted by Dave West on Apr 24, 2009

Sections
Operations & Infrastructure,
Enterprise Architecture,
Development,
Architecture & Design
Topics
SOA ,
Data Access ,
Architecture ,
Cloud Computing ,
REST
Tags
Data Services ,
Google Base ,
Google ,
QCon London 2008 ,
Atom ,
QCon

Frank Mantek Discusses the Google Data API (GDATA)

This presentation from QCon 2008 discusses the structure of GDATA, design choices behind the API, and its relationship to other Google API's. A very generic discussion of GDATA and the Cloud concludes the talk.

Mantek suggests that the vision behind GData is captured in a quote from Jeremy Zawodny of Yahoo:

"The benefit of [GData] is that you'd have a single API that could be used to query, update, and index structured data on the Web -- anywhere on the Web. It's a pretty powerful vision and something I didn't expect to see for a couple more years."

 

Google offers a lot of APIs and most of them incorporate some kind of data access capability: a situation that Frank describes as "freaking complicated." GData is intended to provide a more common, less complicated, and easier to use standard API. Adoption by the engineers responsible for the other APIs (at the time of the presentation) was not yet universal.

GData is grounded in the REST Protocol and not SOAP. Mantek discusses some of the reasons why, emphasizing the simplicity of REST over SOAP.

The Atom Publishing Protocol provides the foundation for GData and, in fact, GData might be seen as an extension of the Atom protocol, on that adds a Data Model, Query model, Concurrency model, and Authentication model. A significant part of the presentation is devoted to a discussion of both the Atom protocol structure and the Google extensions that comprise GData.

 

View The Google Data API (GData); a timely and informative presentation by Frank Mantek.

  • This article is part of a featured topic series on SOA
Presentation sharing by Shashidhar Adiga Posted
  1. Back to top

    Presentation sharing

    by Shashidhar Adiga

    Can you please share the presentation (ppt)?

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.