high_scalability high_scalability-2011 high_scalability-2011-1143 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: In Google+ Is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround we glimpsed inside Google's technology stack for building Google+. Mark Knichel, an engineer on the Google+ infrastructure team, has helped us look a little deeper on how Javascript is handled in Google+. Here's a quick look: They love Closure for its library, templates, compiler, and strict type checking. Compilation is now required for good performance. I've wondered if GWT will be killed off as have other Google properties, but I've been told GWT is being used heavily inside Google, so thankfully that probably won't happen. Closure templates are used both Java and JavaScript to render pages server-side and in the browser. Just-in-time JavaScript. Code is split into modules so the minimum amount of JavaScript is loaded asynchronously in the background as necessary. Navigation happens without loading the page. Page navigation happens without pag
sentIndex sentText sentNum sentScore
1 In Google+ Is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround we glimpsed inside Google's technology stack for building Google+. [sent-1, score-0.104]
2 Mark Knichel, an engineer on the Google+ infrastructure team, has helped us look a little deeper on how Javascript is handled in Google+. [sent-2, score-0.072]
3 Here's a quick look: They love Closure for its library, templates, compiler, and strict type checking. [sent-3, score-0.204]
4 I've wondered if GWT will be killed off as have other Google properties, but I've been told GWT is being used heavily inside Google, so thankfully that probably won't happen. [sent-5, score-0.575]
5 Closure templates are used both Java and JavaScript to render pages server-side and in the browser. [sent-6, score-0.176]
6 Code is split into modules so the minimum amount of JavaScript is loaded asynchronously in the background as necessary. [sent-8, score-0.239]
7 Asynchronous data from the server is rendered in the browser immediately so the whole page doesn't need to be loaded. [sent-12, score-0.17]
8 There's conjecture that making a fast responsive UI means the API can't come first because it may not take the shape required to make the UI fast. [sent-15, score-0.647]
9 So the approach is: make the UI first, make it fast, and then wrap an API around whatever evolved. [sent-16, score-0.104]
10 A controversial methodology, but given the imperative for making a responsive UI, it makes sense. [sent-17, score-0.48]
11 However good this approach is for creating fast UIs, it's death for feature development and fast responsive innovation. [sent-19, score-0.584]
12 With an API you can develop in parallel and release stuff faster and iterate faster. [sent-20, score-0.083]
13 Which is more important: innovative features that differentiate Google+ from competitors or a fast UI? [sent-21, score-0.329]
wordName wordTfidf (topN-words)
[('ui', 0.335), ('google', 0.298), ('javascript', 0.28), ('responsive', 0.249), ('gwt', 0.224), ('navigation', 0.188), ('api', 0.157), ('closure', 0.133), ('alittle', 0.133), ('fast', 0.127), ('controversial', 0.127), ('turnaround', 0.127), ('thankfully', 0.122), ('colossus', 0.122), ('uis', 0.118), ('conjecture', 0.115), ('compilation', 0.112), ('quick', 0.109), ('differentiate', 0.107), ('inside', 0.104), ('servlets', 0.104), ('wrap', 0.104), ('imperative', 0.104), ('killed', 0.104), ('methodology', 0.102), ('happens', 0.102), ('iframes', 0.096), ('rendered', 0.095), ('competitors', 0.095), ('wondered', 0.095), ('juicy', 0.095), ('strict', 0.095), ('templates', 0.093), ('asynchronously', 0.087), ('compiler', 0.084), ('render', 0.083), ('iterate', 0.083), ('required', 0.082), ('death', 0.081), ('minimum', 0.08), ('told', 0.078), ('loading', 0.076), ('mark', 0.075), ('page', 0.075), ('bigtable', 0.074), ('shape', 0.074), ('html', 0.073), ('heavily', 0.072), ('deeper', 0.072), ('loaded', 0.072)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000001 1143 high scalability-2011-11-16-Google+ Infrastructure Update - the JavaScript Story
Introduction: In Google+ Is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround we glimpsed inside Google's technology stack for building Google+. Mark Knichel, an engineer on the Google+ infrastructure team, has helped us look a little deeper on how Javascript is handled in Google+. Here's a quick look: They love Closure for its library, templates, compiler, and strict type checking. Compilation is now required for good performance. I've wondered if GWT will be killed off as have other Google properties, but I've been told GWT is being used heavily inside Google, so thankfully that probably won't happen. Closure templates are used both Java and JavaScript to render pages server-side and in the browser. Just-in-time JavaScript. Code is split into modules so the minimum amount of JavaScript is loaded asynchronously in the background as necessary. Navigation happens without loading the page. Page navigation happens without pag
Introduction: Joseph Smarr, former CTO of Plaxo (which explains why I recognized his picture), in I'm a technical lead on the Google+ team. Ask me anything , reveals the stack used for building Google+: 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
3 0.16234069 665 high scalability-2009-07-29-Strategy: Let Google and Yahoo Host Your Ajax Library - For Free
Introduction: Update: Offloading ALL JS Files To Google . Now you can let Google serve all your javascript files. This article tells you how to do it (upload to Google Code Project) and why it's a big win (cheap, fast, caching, parallel downloads, save bandwidth). Don't have a CDN? Why not let Google and Yahoo be your CDN? At least for Ajax libraries. No charge. Google runs a content distribution network and loading architecture for the most popular open source JavaScript libraries , which include: jQuery, prototype, script.aculo.us, MooTools, and dojo. The idea is web pages directly include your library of choice from Google's global, fast, and highly available network. Some have found much better performance and others experienced slower performance. My guess is the performance may be slower if your data center is close to you, but far away users will be much happier. Some negatives: not all libraries are included, you'll load more than you need because all functionality is included. Yahoo
4 0.16218035 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
Introduction: Hi, We are using AJAX and see a lot of opportunity to keep session state on client browser with javascript objects. Is there any benchmark about how much data you can generally keep in javascript objects in browser? Thanks, Unmesh
5 0.12982869 299 high scalability-2008-04-07-Rumors of Signs and Portents Concerning Freeish Google Cloud
Introduction: Update 2: Rumor no more. Google Jumps Head First Into Web Services With Google App Engine . The quick and dirty of it: developers simply upload their Python code to Google, launch the application, and can monitor usage and other metrics via a multi-platform desktop application. There were 10,000 developer slots open and of course I was too late. More as the cobra strikes. Update: TechCrunch reports Google To Launch BigTable As Web Service next week. It competes with Amazon's SimpleDB. Though it won't be truly comparable until they also release an EC2 and S3 equivalent. An internet hit for each data access is a little painful. As Jimmy says in Goodfellas, "That's the way. You don't take no sh*t from nobody. " First Dave Winer hallucinates a pig on the mean streets of Walnut Creek that told him Google's long foretold cloud offering will be free for bloggers of "modest needs." GigaOM then says a free cloud service is how Google could eat Amazon's bacon for lunch .
6 0.12558573 517 high scalability-2009-02-21-Google AppEngine - A Second Look
7 0.12103223 75 high scalability-2007-08-28-Google Utilities : An online google guide,tools and Utilities.
8 0.11616936 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)
9 0.10924403 301 high scalability-2008-04-08-Google AppEngine - A First Look
10 0.10708454 1427 high scalability-2013-03-20-Dart - Is it the Future of the Web?
11 0.10067487 124 high scalability-2007-10-16-How Scalable are Single Page Ajax Apps?
12 0.099065334 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant
13 0.096960351 211 high scalability-2008-01-13-Google Reveals New MapReduce Stats
14 0.09614829 1014 high scalability-2011-03-31-8 Lessons We Can Learn from the MySpace Incident - Balance, Vision, Fearlessness
15 0.093960688 640 high scalability-2009-06-28-Google Voice Architecture
16 0.093697004 1328 high scalability-2012-09-24-Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
17 0.093634605 1055 high scalability-2011-06-08-Stuff to Watch from Google IO 2011
18 0.093492456 82 high scalability-2007-09-06-Why doesn't anyone use j2ee?
19 0.091762058 1502 high scalability-2013-08-16-Stuff The Internet Says On Scalability For August 16, 2013
20 0.089554697 900 high scalability-2010-09-11-Google's Colossus Makes Search Real-time by Dumping MapReduce
topicId topicWeight
[(0, 0.139), (1, 0.056), (2, 0.005), (3, 0.017), (4, 0.022), (5, -0.032), (6, -0.022), (7, 0.085), (8, 0.03), (9, 0.039), (10, -0.051), (11, -0.058), (12, 0.003), (13, -0.059), (14, -0.0), (15, -0.076), (16, -0.114), (17, -0.049), (18, 0.151), (19, -0.095), (20, 0.087), (21, -0.027), (22, 0.03), (23, -0.123), (24, -0.011), (25, 0.081), (26, -0.013), (27, -0.008), (28, -0.083), (29, 0.011), (30, -0.044), (31, -0.048), (32, 0.027), (33, -0.081), (34, -0.005), (35, -0.038), (36, -0.001), (37, -0.018), (38, -0.018), (39, 0.02), (40, 0.006), (41, -0.051), (42, 0.044), (43, -0.004), (44, -0.038), (45, -0.058), (46, 0.077), (47, -0.097), (48, -0.012), (49, 0.037)]
simIndex simValue blogId blogTitle
same-blog 1 0.98766685 1143 high scalability-2011-11-16-Google+ Infrastructure Update - the JavaScript Story
Introduction: In Google+ Is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround we glimpsed inside Google's technology stack for building Google+. Mark Knichel, an engineer on the Google+ infrastructure team, has helped us look a little deeper on how Javascript is handled in Google+. Here's a quick look: They love Closure for its library, templates, compiler, and strict type checking. Compilation is now required for good performance. I've wondered if GWT will be killed off as have other Google properties, but I've been told GWT is being used heavily inside Google, so thankfully that probably won't happen. Closure templates are used both Java and JavaScript to render pages server-side and in the browser. Just-in-time JavaScript. Code is split into modules so the minimum amount of JavaScript is loaded asynchronously in the background as necessary. Navigation happens without loading the page. Page navigation happens without pag
Introduction: Joseph Smarr, former CTO of Plaxo (which explains why I recognized his picture), in I'm a technical lead on the Google+ team. Ask me anything , reveals the stack used for building Google+: 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
3 0.82491255 75 high scalability-2007-08-28-Google Utilities : An online google guide,tools and Utilities.
Introduction: An online google guide,tools and Utilities to use with the Google search engine.Free google tools and utilities.
4 0.82315147 665 high scalability-2009-07-29-Strategy: Let Google and Yahoo Host Your Ajax Library - For Free
Introduction: Update: Offloading ALL JS Files To Google . Now you can let Google serve all your javascript files. This article tells you how to do it (upload to Google Code Project) and why it's a big win (cheap, fast, caching, parallel downloads, save bandwidth). Don't have a CDN? Why not let Google and Yahoo be your CDN? At least for Ajax libraries. No charge. Google runs a content distribution network and loading architecture for the most popular open source JavaScript libraries , which include: jQuery, prototype, script.aculo.us, MooTools, and dojo. The idea is web pages directly include your library of choice from Google's global, fast, and highly available network. Some have found much better performance and others experienced slower performance. My guess is the performance may be slower if your data center is close to you, but far away users will be much happier. Some negatives: not all libraries are included, you'll load more than you need because all functionality is included. Yahoo
5 0.75981528 1427 high scalability-2013-03-20-Dart - Is it the Future of the Web?
Introduction: John McCutchan , after a long career spent working on the Linux kernel and being hired out as a code optimization guru, joined Google's Dart team. A curious hire until you watch Bringing SIMD to the Web via Dart , where John makes a programmer accessible explanation of why he likes Dart: performance, performance, performance. Dart is an open-source Web programming language developed by Google . The motivation for Dart is twofold: provide a language capable of scaling up to the complex web applications that are becoming the norm. Think Gmail. And provide a single language capable of working on both the client and server. Towards those ends Dart is a complete language, full tool environment, and provides an advanced Web UI framework for building web applications at a high level of abstraction. Why isn't JavaScript good enough? The fear is for large web apps the nature of JavaScript puts crippling limits on potential performance improvements, which will cause web app
6 0.75430721 1535 high scalability-2013-10-21-Google's Sanjay Ghemawat on What Made Google Google and Great Big Data Career Advice
7 0.7461949 618 high scalability-2009-06-05-Google Wave Architecture
8 0.74384457 1328 high scalability-2012-09-24-Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
9 0.72963029 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant
10 0.71905369 640 high scalability-2009-06-28-Google Voice Architecture
11 0.67597264 301 high scalability-2008-04-08-Google AppEngine - A First Look
12 0.65896022 642 high scalability-2009-06-29-HighScalability Rated #3 Blog for Developers
13 0.65555829 394 high scalability-2008-09-25-HighScalability.com Rated 16th Best Blog for Development Managers
14 0.65157592 899 high scalability-2010-09-09-How did Google Instant become Faster with 5-7X More Results Pages?
15 0.65095901 242 high scalability-2008-02-07-Looking for good business examples of compaines using Hadoop
16 0.64525408 1010 high scalability-2011-03-24-Strategy: Disk Backup for Speed, Tape Backup to Save Your Bacon, Just Ask Google
17 0.64374799 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)
18 0.64338481 299 high scalability-2008-04-07-Rumors of Signs and Portents Concerning Freeish Google Cloud
19 0.63304931 409 high scalability-2008-10-13-Challenges from large scale computing at Google
20 0.62720251 941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests
topicId topicWeight
[(1, 0.083), (2, 0.23), (10, 0.039), (12, 0.045), (17, 0.029), (22, 0.123), (27, 0.013), (30, 0.038), (41, 0.037), (49, 0.021), (61, 0.054), (77, 0.016), (79, 0.128), (94, 0.055)]
simIndex simValue blogId blogTitle
Introduction: The story of driving the golden spike to symbolize the completion of the transcontinental railroad is famous in the US. What is not so well known is the story of how it also foreshadowed changes to come as an early version of both the Internet and the Internet of Things. But that was 1869, how can that possibly be? Telegraph as Internet First, let's establish the telegraph and cable systems was an early version of an Internet. As railroad tracks were being laid a transcontental telegraph system was also being constructed. Telegraph lines were installed parallel to the tracks making instant communication available across the continent, faster than any horse could ride. With the transalantic cable system information could quickly span continents in minutes: The miles of American telegraph grew from 40 in 1846 to 12,000 in 1850 to 23,000 in 1852. In Europe it increased from 2,000 in 1849 to 110,000 in 1869. The cost of sending 10 words was $1.55 in 1850, $1 in 1870, 40
2 0.94408131 491 high scalability-2009-01-13-Product: Gearman - Open Source Message Queuing System
Introduction: Update: New Gearman Server & Library in C, MySQL UDFs . Gearman is an open source message queuing system that makes it easy to do distributed job processing using multiple languages. With Gearman you: farm out work to other machines, dispatching function calls to machines that are better suited to do work, to do work in parallel, to load balance lots of function calls, to call functions between languages, spread CPU usage around your network . Gearman is used by companies like LiveJournal, Yahoo!, and Digg. Digg, for example, runs 300,000 jobs a day through Gearman without any issues. Most large sites use something similar. Why would anyone ever even need a message queuing system? Message queuing is a handy way to move work off your web servers (like image manipulation), to generate thousands of documents in the background, to run the multiple requests in parallel needed to build a web page, or to perform tasks that can comfortably be run in the background and not part
same-blog 3 0.93039078 1143 high scalability-2011-11-16-Google+ Infrastructure Update - the JavaScript Story
Introduction: In Google+ Is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround we glimpsed inside Google's technology stack for building Google+. Mark Knichel, an engineer on the Google+ infrastructure team, has helped us look a little deeper on how Javascript is handled in Google+. Here's a quick look: They love Closure for its library, templates, compiler, and strict type checking. Compilation is now required for good performance. I've wondered if GWT will be killed off as have other Google properties, but I've been told GWT is being used heavily inside Google, so thankfully that probably won't happen. Closure templates are used both Java and JavaScript to render pages server-side and in the browser. Just-in-time JavaScript. Code is split into modules so the minimum amount of JavaScript is loaded asynchronously in the background as necessary. Navigation happens without loading the page. Page navigation happens without pag
4 0.92789996 1621 high scalability-2014-03-28-Stuff The Internet Says On Scalability For March 28th, 2014
Introduction: Hey, it's HighScalability time: Looks like a multiverse , if you can keep it. Quotable Quotes: @abt_programming : "I am a Unix Creationist. I believe the world was created on January 1, 1970 and as prophesized, will end on January 19, 2038" - @teropa @demisbellot : Cloud prices are hitting attractive price points, one more 40-50% drop and there'd be little reason to go it alone. @scott4arrows : Dentist "Do you floss regularly?" Me "Do you back up your computer data regularly?" @avestal : "I Kickstarted the Oculus Rift, what do I get?" You get a lesson in how capitalism works. @mtabini : “$20 charger that cost $2 to make.” Not pictured here: the $14 you pay for the 10,000 charger iterations that never made it to production. @strlen : "I built the original assembler in JS, because it's what I prefer to use when I need to get down to bare metal." - Adm. Grace Hopper tedchs : I'd like to propose a new rule for Hacker News: only if you have b
5 0.89869016 946 high scalability-2010-11-22-Strategy: Google Sends Canary Requests into the Data Mine
Introduction: Google runs queries against thousands of in-memory index nodes in parallel and then merges the results. One of the interesting problems with this approach, explains Google's Jeff Dean in this lecture at Stanford , is the Query of Death . A query can cause a program to fail because of bugs or various other issues. This means that a single query can take down an entire cluster of machines, which is not good for availability and response times, as it takes quite a while for thousands of machines to recover. Thus the Query of Death. New queries are always coming into the system and when you are always rolling out new software, it's impossible to completely get rid of the problem. Two solutions: Test against logs . Google replays a month's worth of logs to see if any of those queries kill anything. That helps, but Queries of Death may still happen. Send a canary request . A request is sent to one machine. If the request succeeds then it will probably succeed on all machines, s
6 0.89803928 301 high scalability-2008-04-08-Google AppEngine - A First Look
7 0.89369291 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers
8 0.88894874 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
9 0.8883999 1645 high scalability-2014-05-09-Stuff The Internet Says On Scalability For May 9th, 2014
10 0.88822597 823 high scalability-2010-05-05-How will memristors change everything?
11 0.88530684 780 high scalability-2010-02-19-Twitter’s Plan to Analyze 100 Billion Tweets
12 0.88527602 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
13 0.88524479 1090 high scalability-2011-08-01-Peecho Architecture - scalability on a shoestring
14 0.88473278 1612 high scalability-2014-03-14-Stuff The Internet Says On Scalability For March 14th, 2014
15 0.88396156 709 high scalability-2009-09-19-Space Based Programming in .NET
16 0.88385618 76 high scalability-2007-08-29-Skype Failed the Boot Scalability Test: Is P2P fundamentally flawed?
17 0.88382918 1545 high scalability-2013-11-08-Stuff The Internet Says On Scalability For November 8th, 2013
18 0.88328159 1439 high scalability-2013-04-12-Stuff The Internet Says On Scalability For April 12, 2013
19 0.88315135 183 high scalability-2007-12-12-Report from OpenSocial Meetup at Google
20 0.88255918 533 high scalability-2009-03-11-The Implications of Punctuated Scalabilium for Website Architecture