EOF - The Google Exposure
Advertising is a bubble. If that's a true statement, Google is a bubble too. And if that's true, many of the goods we take for granted on the Web are at risk. Let's run down some evidence.
Google has more than a million servers. The company is notoriously silent on the exact number, but I was told by a Google official that it was headed toward a million in the next couple years—and that was seven years ago. For a peek at the future, Jeff Dean of Google gave a presentation at an ACM workshop in October 2009, outlining “Spanner”, a “storage and computation system that spans all our data centers”. His “design goals” slide described a “future scale” with “~106 to 107 machines, ~1013 directories, ~1018 bytes of storage, spread at 100s to 1000s of locations around the world....”
Google's data centers are already public utilities on the scale of coal-fired power plants. Google is silent about the number and size of these as well. In March 2008, Rich Miller of Data Center Knowledge wrote, “The conventional wisdom is that Google has dozens of data centers. We're aware of at least 12 significant Google data center installations in the United States, with another three under construction.”
Those data centers serve enormous sums of traffic. According to the ATLAS Internet Observatory 2009 Annual Report, Google has reached #3 among the top ten “Tier 1” Internet backbone providers last year. Just two years earlier, Google wasn't on the list. As a Tier 1 player, Google “peers” with others on the list. That means they pay nothing to each other for data transit. Tier 1 status is more a matter of traffic rather than physical fiber backbone. Google has plenty of backbone, but where it rules is with traffic.
The greatest source of inbound traffic for most Web sites has long been search engines, where Google has a near monopoly. Consider the case of StackOverflow.com. Last year it reported, “83% of our total traffic is from search engines, or rather, one particular search engine”. Google was first with 3,417,919. Yahoo was second with 9,779.
To some big-old business categories, Google's threat is apocalyptic. Take geographic data. For many years, NAVTEQ and Tele-Atlas have enjoyed something of a duopoly in the geo-business, providing data to GPS companies, car companies, avionics manufacturers and so on. When you looked at Google Maps, you saw NAVTEQ's or Tele-Atlas' logo. That ended last October, when Google dumped Tele-Atlas, just like it had dumped NAVTEQ earlier, as a source of US map data. As it does in so many other business categories, Google is now giving its US geo data away for free—or less. Bill Gurley reports, “Google will pay you to use its mobile OS. I like to call this the 'less than free' business model. This is a remarkable card to play. Because of its dominance in search, Google has ad rates that blow away the competition.” Sound familiar? It's roughly the same thing Microsoft did to the browser business. It eliminated that business by offering Internet Explorer for free. Back then, however, the browser business was new and small. Google goes for bigger game, such as the phone business.
Android might be the most apocalyptic move ever laid on a standing industry. First, Google creates an open phone design on a Linux platform, lines up a pile of handset makers behind it and then works deals with carriers as well. I've done a lot of consulting work in the telco world over the last few years, and here's the most graphic way I've heard Google's approach to the industry explained: “Google feeds a dock rope down the gullet of the monster, waits for the rope to come out the back end, and then yanks it straight.”
Of course, the phone business needs some straightening. We're long overdue for white-box phones and data paths that look and feel like the real Internet, rather than billed phone connections. I've got no problem with Google hastening history there.
I'm just worried about the way Google makes money. Nearly all of it comes from advertising. That's what pays for all the infrastructure Google is giving to the rest of us. As our dependency on Google verges on the absolute, this should be a concern.
Think of advertising as oil and Google as one big emirate. What happens when the oil runs out?
Maybe it already is. Citing a “Natural Born Clickers” study by ComScore and Starcoma, Ad Age last year reported that “the number of people online who click display ads has dropped 50% in less than two years, and only 8% of Internet users account for 85% of all clicks...What's more, the 8% of Internet users that compose a majority of clicks is also down by half from the last study, which found 16% are responsible for 80% of clicks. The 2008 study found half of all clicks come from lower-income young adults.”
The free rides won't go on forever. There are better ways than advertising for demand and supply to find each other (including search, which is free), and more will be found. Google will be in the middle of that discovery process, no doubt. But it's an open question whether Google will make the same kind of money in a post-advertising marketplace. I'm betting they won't.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Keeping track of IP address
7 min 39 sec ago
- Roll your own dynamic dns
5 hours 21 min ago
- Please correct the URL for Salt Stack's web site
8 hours 32 min ago
- Android is Linux -- why no better inter-operation
10 hours 47 min ago
- Connecting Android device to desktop Linux via USB
11 hours 16 min ago
- Find new cell phone and tablet pc
12 hours 14 min ago
13 hours 43 min ago
- Automatically updating Guest Additions
14 hours 51 min ago
- I like your topic on android
15 hours 38 min ago
- This is the easiest tutorial
22 hours 14 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?