I helped design and build a lot of the circles model and sharing UI for Google+. I was recruited to Google to work on "getting social right" in early 2010. Prior to that, I was CTO of Plaxo, and also its first employee (since March 2002). I've also spent many years working on open standards for the social web (OpenID, OAuth, Portable Contacts, WebFinger, etc.) Since I work for a big/public company (albeit a pretty cool one), I can't provide specific stats, dates for future features, or details of confidential code/algorithms. But I will do my best to be "refreshingly frank" about everything else. :)
What software technology stack does Google+ use?Our stack is pretty standard fare for Google apps these days: we use Java servlets for our server code and JavaScript for the browser-side of the UI, largely built with the (open-source) Closure framework, including Closure's JavaScript compiler and template system. A couple nifty tricks we do: we use the HTML5 History API to maintain pretty-looking URLs even though it's an AJAX app (falling back on hash-fragments for older browsers); and we often render our Closure templates server-side so the page renders before any JavaScript is loaded, then the JavaScript finds the right DOM nodes and hooks up event handlers, etc. to make it responsive (as a result, if you're on a slow connection and you click on stuff really fast, you may notice a lag before it does anything, but luckily most people don't run into this in practice). Our backends are built mostly on top of BigTable and Colossus/GFS, and we use a lot of other common Google technologies such as MapReduce (again, like many other Google apps do). Read more: AnyAsq
QR:
What software technology stack does Google+ use?Our stack is pretty standard fare for Google apps these days: we use Java servlets for our server code and JavaScript for the browser-side of the UI, largely built with the (open-source) Closure framework, including Closure's JavaScript compiler and template system. A couple nifty tricks we do: we use the HTML5 History API to maintain pretty-looking URLs even though it's an AJAX app (falling back on hash-fragments for older browsers); and we often render our Closure templates server-side so the page renders before any JavaScript is loaded, then the JavaScript finds the right DOM nodes and hooks up event handlers, etc. to make it responsive (as a result, if you're on a slow connection and you click on stuff really fast, you may notice a lag before it does anything, but luckily most people don't run into this in practice). Our backends are built mostly on top of BigTable and Colossus/GFS, and we use a lot of other common Google technologies such as MapReduce (again, like many other Google apps do). Read more: AnyAsq
QR:
Posts
0 comments:
Post a Comment