Google: Too Thin, Too Fat, or Just Right

September 25, 2008

As companies in the search and content processing business gird themselves for a tough 2009, I am on the look out for analyses that provide a suggestion of where big dogs will hunt. My eye was drawn to an essay with the fetching title “Is Google Spreading Itself Too Thin?” You can read the full post by Tim O’Reilly here. I agree with the key points in the write up. For me the most interesting statement was:

‘m happy to criticize Google for shallow attempts to capitalize on opportunities created by others, and am very concerned about an increasing tendency to favor Google’s own content sites rather than distributing attention to others. But Google is a long way from eating their own children, as Microsoft eventually did. Both Android and Chrome demonstrate true strategic thinking, focusing on how to grow the market for everyone rather than just finding advantage for Google.

I would add one point and, of course, invite comment. My research suggests that Google can roll out innovations with comparatively modest incremental investment and a velocity that makes some of its competitors look a bit like turtles on ice. The cost/speed factors translate to a certain luxury in experimentation. These factors translate to greater pressure on companies perceiving themselves to be in the Google headlights. Agree? Disagree?

Stephen Arnold, September 25, 2008

ESS West Endnote: Google the Winner for 2009

September 25, 2008

My end note for the Enterprise Search Summit West created a bit of a stir. I summarized three trends I perceived based on my walk arounds and attendance at sessions over the last two days. These were:

  1. Buzzwords that slid around some of the major issues confronting some vendors
  2. Concern about processes in numerous sessions
  3. A growing awareness of financial pressures.

What I concluded was that for 2009, Google has a dominant if not almost unassailable position in the search market. Google could, with luck and marketing, make significant gains in cloud services. Many in the audience took issue with my assessment. I listened, but in the end, I stood by my conclusions. What do you think? Will Google fizzle? Will legal procedures cripple the company? Help me learn.

Stephen Arnold, September 25, 2008

Googlezon: Tan, Ready, Rested

September 24, 2008

The avalanche of articles, commentary, and backlink bottom feeding kept me from commenting about the Google G1 mobile device. I am not that excited about a gizmo. What I am thinking about are the stories about the Google / TMobile G1 preloaded with a hook to the Amazon MP3 store. You can read about this feature here. A hook up between Amazon and Google, no matter how trivial, is interesting. For companies like Apple or eBay, the connection is more than a curiosity or a convenience for a 20 something who can’t drink coffee without a personal sound track echoing through their actions. Here’s why in my opinion this tiny deal merits scrutiny:

  1. Google has no footprint in music. Amazon has been eager to replace the lost revenue of traditional CD sales. Now the two also rans in the online music business seem to be taking a tiny step to address this issue. Will it work? I’m not sure, but it’s an interesting move.
  2. Google has sat on its haunches and watched Amazon–a company headed by the world’s smartest man–out Google Google in cloud computing. Maybe this deal is a tacit admission that the GOOG’s math and physics majors need Amazon’s market savvy. Amazon certainly could benefit from some of Google’s engineering expertise.
  3. Amazon could become the equivalent of a Roman siege tower in an escalating battle with Apple. Apple has outgunned both Google and Amazon in online music retailing. Google has an enternal beta in its now repositioned Froogle service, its junk filled Google Base, and its lawsuit attracting YouTube.com service. Amazon might find a way to tap into Google’s ad goodness. Apple lacks this tap dancing move.

In this tussle among Amazon, Apple, Google, an Microsoft–sorry, Yahoo, you are not in the game–a relationship between Amazon and Google might undermine Microsoft’s subtle, often behind the scenes cheerleading for Amazon. Apple might find itself in more direct competition with the GOOG. Consumers may see more disruption on the online retail market in certain sectors.

A real or virtual Google – Amazon deal would raise again the notion of Googlezon. I think this is something I will enjoy pondering. Agree? Disagree?

Stephen Arnold, September 24, 2008

IBM and Standards

September 24, 2008

The headline “IBM May Quit Technology Standards Body”, if true, marks an important change in direction at IBM. The article here references the Wall Street Journal asserting:

IBM has become frustrated by what it considers opaque processes and poor decision-making at some of the hundreds of bodies that set technical standards for everything from data-storage systems to programming languages…

In my opinion, IBM’s effort to support open source was a useful endorsement of open source. The Eclipse Foundation owes IBM a debt which it may not be able to repay. Now, IBM and other super platforms may be shifting back to the good, old, and lucrative days of walled gardens. In a world distorted by Google’s gravitational pull, companies like IBM have to protect their assets. Standards may be a problem, not a solution. The losers? I think it will be small fish like me.

Stephen Arnold, September 24, 2008

Google and Sparse Tables

September 24, 2008

Google received a patent for an invention crafted by some of the firm’s most wizardly wizards; for example, Jeff Dean, Sanjay Ghemawat, and Andrew Fikes, among others. US7,428,524 is a plumbing invention with the helpful title “Large Scale Data Storage in Sparse Tables”. The abstract said:

Each of a plurality of data items is stored in a table data structure. A row identifier and column identifier are associated with each respective data item, and each respective item is stored at a logical location in the table data structure specified by its row identifier and column identifier. A plurality of data items is stored in a cell of the table data structure, and a timestamp is associated with each of the plurality of data items stored in the cell. Each of the data items stored in the cell has the same row identifier, the same column identifier, and a distinct timestamp. In some embodiments, each row identifier is a string of arbitrary length and arbitrary value. Similarly, in some embodiments each column identifier is a string of arbitrary length and arbitrary value.

Don’t let the fuzzy legalese put you to sleep. This is a key infrastructure invention which adds one more paving stone to Google’s building a Roman road right to the heart of enterprise data management and high performance for consumer facing services. You can obtain a copy from the USPTO’s Web site here.

 

Stephen Arnold, September 24, 2008

SharePoint Thesaurus Joy

September 24, 2008

I4heard more about SharePoint than Google today at the Enterprise Search Summit. Like it or not, SharePoint plays a prominent role in the world of enterprise information management. The Microsoft Enterprise Search Web log added some joy to my otherwise dreary day. The article “How to Customize the Thesaurus in SharePoint Search and Search Server” is a useful read. You can access the essay published on September 23, 2008, here. The article includes an explanation, a code sample, and useful notes. Highly recommended.

Stephen Arnold, September 24, 2008

A Head in the Clouds

September 23, 2008

Disclaimer: this is a live on the fly post during a talk. I may edit it later.

I wormed my way into Werner Vogels’ keynote at the Streaming Media conference in San Jose, California. The title of this Web log post is not precisely what Dr. Vogels’ typed on his title slide. He offered “Ahead in the Clouds”, and the idea is that Amazon is leaving Google, Salesforce.com, and others like Apple behind. My version of the title makes clear my skepticism about some of the cloud initiatives for people my age. I know that those under 20 in body and mind see the era of clunky PCs, weird laptops, and other assorted access devices that promise unparalleled freedom. I don’t want to be free of my computing infrastructure but I want to learn. I’m perched on a metal chair with an open mind. I want to capture two or three ideas from Dr. Vogels and then offer my own comments. If you want a complete summary of his remarks, look for Web log postings from “real” journalists; I’m the addled goose, not a human tape recorder.

First, the subtitle of the talk is “The Power of Infrastructure as a Service”. I think I understand, but I wonder what happens if I have lousy bandwidth and the service crashes. Uptime and stability are often a work in progress even at Amazon as I await the lecture. In the back of my mind is the hunch that getting customers to rent infrastructure needed to deliver Amazon’s ecommerce services is a financial angle first and a substantive revenue generator second. I wonder how distant the Amazon Web services’ revenue is from Amazon’s retail revenue? If I remember I will try to find this number.

Second, looks to me as if this keynote is outpulling the other two going on at the same time. Amazon is a much bigger “name brand” than the consultants and software vendors competing for an audience. I estimate the crowd at about 150. You can buy an audio version of Dr. Vogels’ talk at www.streamingmedia.com. No information about the cost or who can buy the talks.

Third, a video is running with quite a few Microsoft centric folks in the images. Site referenced is Animoto. It is not clear if this is an Amazon-allied enterprise. Animoto is a music matching type site. Animoto is running on Amazon Web services. I wonder if Amazon is defraying some of the fees for a share in the company. Animoto is using all of Amazon’s Web services, so it’s a smart start up. Note: sound system is making it tough for me to parse Dr. Vogels’ speech. Animoto, if I heard correctly, delivers its users instant audio gratification.

Fourth, a slide of instance usage shows steady rise over time. I can’t make out the y axis or the x axis. The slide shows Animoto’s usage over time. The company can handle 35,000 customers per hour. Amazon made additoinal resources available. At start up 50 servers and now work is spread over 5,000 servers. The scaling is automatic and Animoto is happy. The pay off is that Animoto’s capital expense is minimized.

Fifth, most of the people in the room are Amazon customers. Now the meat of the talk–the technology side of Amazon. Amazon is a technology company. Technology is at the heart of Amazon. “We just happen to do retail,” says Dr. Vogels. Another graph showing the bandwidth demand over time. This is a hockey stick graph. Amazon Web services is sucking more bandwidth that “regular retail” Amazon. I wonder how the telecommunjications costs work out. The current slide shows the growth in Amazon developers. Now the company has 400,000 developers. The next graph shows a diagram that looks like a picture of an atom exploding. I am not sure what the graph depicts. There are no data and no labels on the chart. “It took us 10 to 12 years to get this Amazon architecture right.” My recollection is that Dr. Vogels joined the company more recently. I will have to look up his date of joining.

Sixth, Dr. Vogels is showing a list of the cost “heavy lifting” that Amazon has done. The idea is that AWS is a “shared services platform”. The infrastructure services scale up and down and are “highly reliable.” I wonder if uptime data will be available in this talk or on the Amazon Web site. The last time I looked, I could not find hard data to support these assertions about uptime as I recall.

Seventh, the services are now available as a content delivery network. This will be a “pay as you go” service. One benefit is scaling up and scaling down. The down scaling takes place in a matter of minutes. Amazon has “spent billions of dollars over ten years to create the infrastructure.” No data provided on total investment.

Eighth, the AWS story is the core of this presentation because it holds down production costs and it is a distribution medium. Companies in the media business want to hold down costs and get distribution. New services can be enabled. The idea is that it is easier and cheaper to build a successful business using AWS.

Ninth, the four stages — produce, encode, distribute, and archive — of a business and AWS can play a role in each stage. Dr. Vogels is going through companies using AWS to deliver their media services. The Web site names are unfamiliar to me and there is no labeling of the sites on the PowerPoint slides. These AWS customers get “extremely high reliability services”. One site is RenderRocket.com. AWS provides capacity to this company. Vimeo.com uses AWS; the site is a social video site. The Indy Racing League uses AWS. IRL shows videos, delivers commentary, and community services. IRL reported a 50 percent savings using AWS. No figures provided. Another video example. This site allows the user to view the scene by selecting different camera’s. Panda Video is an open source community video service. The video sites are hard for me to differentiate. The message is clear: lots of buyers, reliable service, and more economical than using other options. No data on the specific charges for services and bandwidth.

Tenth, the “billions of objects in Amazon S3”. This slide shows growth but there is not definition of an object, so the slide is floating without concrete back up. I now want more substance, not just a run through of small sites using the AWS. I guess I am showing my age.

Stephen Arnold, September 23, 2008

Information Overload Is a Filter Problem

September 23, 2008

I just clicked through some of the hundreds of posts about the Google Android phone. I was startled by the redundancy in the posts. There were some useful items buried in the flood of messages, but none of these added to my understanding of this Google initiative.

Bored and underwhelmed, I turned my attention to other information snagged by my newsreader. My eye was hooded by the video of Clay Shirky’s keynote at Web 2.0 Expo during the week of September 15. You can watch the talk here. The snippet that caught my attention was this remark:

Privacy is a way of managing information flow. The inefficiency of information flow wasn’t a bug, it was a feature.

I found this comment somewhat disturbing even though I agree with most of Mr. Shirky’s comments. Here’s what troubled me:

  1. Information flow in today’s volumes are largely unexpected and not fully understood. As a result, most organizations and experts don’t know how to address the issues of data flow scale in a helpful manner. Social “voting”, old fashioned key word filters, and zingy visualizations of hot spots can help as well as give users a sense of false confidence. That’s risky.
  2. Enterprise and consumer systems are mostly toys in that only a handful of services can operate at petabyte scale. Even mid sized businesses are struggling with terabyte flows and most tools are not very good, economical, or easy to use. I am concerned about the assumption that these systems deliver good enough solutions. I don’t think these systems do. Example: the financial crashes caused by flawed models’ ability to pinpoint significant data fed into them. A trillion dollar mistake strikes me as a relatively big problem.
  3. Social media is one tool, and it is [a] not understood, [b] immature, and [c] chock full of potential weaknesses. Many of these issues–such as security–will be addressed over time. For now, I think the risks in regulated companies may outweigh the benefits. Another silver bullet shifts the focus from problem solving to a quick fix.

The final issue I have is that I don’t have an answer to this question: “When I don’t know what I need to answer my question, what do I filter in and out?” Information does not behave like some other human constructs. For example a doctor who misdiagnoses a problem, prescribes the wrong treatment, and assumes her solution is the right one can injure, maybe kill, a patient. The doctor filtered information, but the decision was not optimal.

I am not yet convinced that this “social” trends in information will do much to alleviate the severe information problems that face most organizations. I am certainly not trendy, and I need to see fungible evidence that the payoffs are substantive, not just another wagon load of baloney sold to pump cash into vendors’ threadbare pockets.

Stephen Arnold, September 23, 2008

Knol Understanding

September 23, 2008

Slate’s Farhad Manjoo’s “Why Google’s Online Encyclopedia Will Never Be as Good as Wikipedia” takes a somewhat frosty stance toward Knol. You can read his interesting essay here. For me the most significant point was this one:

Knol is a wasteland of such articles: text copied from elsewhere, outdated entries abandoned by their creators, self-promotion, spam, and a great many old college papers that people have dug up from their files. Part of Knol’s problem is its novelty. Google opened the system for public contribution just a couple months ago, so it’s unreasonable to expect too much of it at the moment; Wikipedia took years to attract the sort of contributors and editors who’ve made it the amazing resource it is now.

Knol is one of those Google products that appear and seem to have little or no overt support. I agree. I would like to make three comments:

  1. Knol may be a way for Google to get content for itself first and then secondarily for its users. Google wants information, and Knol is a different mechanism for information acquisition. Assuming that it is a Wikipedia may only be partially correct.
  2. Knol, like many other Google services, does not appear to have a champion. As a result, Knol evolves slowly or not at all. Knol may be another way for Google to determine interest, learn about authors who are alleged experts, and determine if submitted content validates or invalidates other data known to Google.
  3. Knol may be part of a larger grid or data ecosystem. As a result, looking at it out of context and comparing it to a product with which it may not be designed to compete might be a partially informed approach.

Based on my analysis of the Google JotSpot acquisition and the still youthful Knol service, I’m not prepared to label Knol or describe it as either a success or failure. In my 10pinion, Knol is a multi purpose beta. Its principal value may be in the enterprise, not the consumer space. But for me, I have too little data and an incomplete understanding of how the JotSpot “plumbing” is implemented; therefore, I am neutral. What’s your view?

Stephen Arnold, September 23, 2008

Amazon Oracle in Cloud Services Play

September 23, 2008

Amazon, the company run by the world’s smartest man, has aced Google again. Amazon’s information technology budget is a fraction of Google’s. Over the last three years, Amazon has beaten Google to the punch when it comes to cloud computing. Based on this article on the Amazon Web services Web log, Amazon is now offering Oracle database services on the AWS platform. Jeff Bezos has had a sixth sense or a heck of a Google technology watching operation in place. Amazon has moved more quickly than Google to deliver cloud services that Google * could * have delivered but did not. For example, the work to worker service called MT or Mechanical Turk aced the GOOG. The Amazon storage service beat the GOOG to the market. The elastic cloud service was first out of the gate. Now, Amazon with a fraction of Google’s technical horsepower and information technology budget must watch and learn from Amazon’s Oracle deal. I recall reading somewhere that at the core of Amazon beats the aging but reliable Oracle database. I don’t know if this is true any longer, but I was not expecting this type of deal. Amazon has been making noise with Linux and open source plus some stealth graduate students from European universities. Oracle was a bolt from the blue for me.

Will Oracle prove to be cloudable? Probably, but I anticipate some latency issues. Developers who assume that Oracle’s tricks can be learned on the fly are likely to create some problems. Most of these will be worked out in time.

The larger question is, “What will Google do?” My research provided some data, not definitive data unfortunately, that Google could offer a cloud based enterprise data management service. Google has the plumbing. Its patent documents reveal nifty technology to allow an enterprise to “hook” into the Google infrastructure to use Google services to crunch data. Google has the next generation data management tools that many organizations need at a time when data volume threatens to choke existing database systems. Frankly, I’m not sure.

Here are my thoughts about this surprising Amazon move:

  1. Google either has to take action to position itself against Amazon, a company defining the cloud service space for some developers, or be content to be a follower. Google, in fact, may be acquiring some of Microsoft’s market methods, which may be both good and bad.
  2. Amazon has to make the Oracle service work. Cooking up an S3 or EC2 is one thing. Delivering Oracle services is another. Amazon has a spotty record with regard to stability and uptime. A flop might open the door for a competitor to supplant Amazon. Google could exploit such an Amazon stumble, but the company seems to have a fuzzier view of the enterprise market and may not be able to act quickly with regard to Amazon.
  3. The Amazon aggressiveness might force Google to buy Salesforce.com, deal with the programming issues, and use Salesforce.com’s marketing position as a launch pad in an attempt to wrest momentum from Amazon.

You can read a different take on this Amazon development in Larry Dignan’s “Amazon Adds Oracle Support to EC2” here.

What’s clear to me is that Amazon has raised the stakes for Google in cloud computing services.

Stephen Arnold, September 23, 2008

« Previous PageNext Page »

  • Archives

  • Recent Posts

  • Meta