Channels ▼
RSS

Tools

Inside The Google+ Engine Room


Reporting on UK-based developerFusion, Chris Alexander has uncovered some of the technologies behind Google+ to provide insight into the search giant's engine room.

Looking into the Google technology stack and development processes that went into the Google + social networking project, Alexander says that development work started out a little over a year ago as far back as the start of 2010.

Unsurprisingly perhaps, Google's in-house development team used what has been dubbed a "highly agile and flexible approach" to development, during a process which no doubt saw the team "dogfooding" on the product during its development.

"On the server side, as you may expect, Google+ is all Java. It uses a lot of libraries that Google developed and open sourced over the past few years, including many that were used in Google Wave, the now-defunct real-time app that nobody really knew what to do with," reports Alexander.

"These libraries include Guice, a code cleanup tool designed to make writing Java easier; and GWT (Google Web Toolkit), another tool to ease writing Java web apps again open-sourced by Google," he added.

developerFusion goes on to report that on the client side, the HTML 5 history API has been "exploited" — an undertaking carried out to give cleaner URLs when using AJAX page navigation. Alexander comments that this is, "A pleasing alternative to the dubious at best hash-bang approach commonly adopted."

You can read the original story in full here: http://t.co/VKjHBu8


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video