Google open-sources XML alternative



Email    print   
July 16, 2008 —  (Page 1 of 2)
Google’s servers are awash with thousands of different data formats—so much so that the company claims XML is not efficient enough to encode it all. Instead, it has created a new interface description language (IDL) and binary format for data interchange that it is now sharing as an open-source project.

Google made code and documentation for the Protocol Buffers format available on July 7, under the Apache 2.0 open-source license.

Google is using Protocol Buffers for communicating among its internal systems that use Remote Procedure Calls systems and accessing persistent data storage. Developers can define data structures using its definition language and then compile them, producing classes that represent those structures in a particular programming language, explained Google engineer Kenton Varda in a post to the company’s software engineering team blog.

The classes, which are designated as .proto files, can read and write structured data from data streams. At this time, language support is limited to C++, Java and Python.

Varda noted that Protocol Buffers is an IDL that was designed for simplicity. IDLs are used to create a communications bridge between programs that are written in different languages or reside on different operating systems.

The framework compiles the IDL code—an intermediary format—into a binary format, which is used as a transmission protocol, explained Forrester senior analyst Jeffrey Hammond.

“By sticking to a simple lists-and-records model that solves the majority of problems and resisting the desire to chase diminishing returns,” Varda wrote, “we believe we have created something that is powerful without being bloated. And, yes, it is very fast—at least an order of magnitude faster than XML.”

Google’s documentation claims that structured data can be represented in a third to a 10th of the space required, and transmission times cut to a 20th or even a 100th of the time, compared to XML.

According to Varda, Google rejected XML because it is not efficient at the scale at which it operates and is an expensive proposition when servers and networks are running at full capacity. Also, writing code to work with the DOM tree can potentially become unwieldy.



Related Search Term(s): Open source, XML, Google

Pages 1 2 


Share this link: http://sdt.bz/32555
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Git changes how developers manage source code versions
At this year's Git Together, developers praise the platform's convenience and its ability to make source control easier. Changes for the future will focus on making it more Web 2.0-compatible by offering more on-demand repositories on GitHub Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb