How Google Works
Posted on July 9, 2006 Comments (4)
How Google Works by David F. Carr
An interesting look at the technology system behind Google.
Google was driven from the beginning by engineers that sought to do what was best. Since those engineers were the founders of the company and still run the company Google has been able to keep the focus not on what is accepted as conventional wisdom but what actually works best. Google understands when you experiment things might not work out. Google’s solution is to experiement quickly and fail early (turn the pdsa cycle quickly). That is something every organization can apply.
The advantage will erode over time, and Google will eventually run up against the limits of how much homegrown technology it can manage, Valdes predicts: “The maintenance of their own system software will become more of a drag to them.”
But Google doesn’t buy this traditional argument for why enterprises should stick to application-level code and leave more fundamental technologies like file systems, operating systems and databases to specialized vendors. Google’s leaders clearly believe they are running a systems engineering company to compete with the best of them.
Google is a fascinating company to read about. But they are also significantly different. You can’t copy the methods they use. Very few companies are going to benefit by writing their own file systems and operating systems. However, in those instances where your organization should pursue customized solutions can you.
The scope of those customized solutions at Google are inspiring, in part because of their scope. What most can learn from Google is that those who claim certain things are not possible or practical are not always right. Of course, there are many examples of companies that fail trying to be different so those that urge caution are not always wrong either.
How much of what you spend time on could benefit from thinking in this way: “instead of making things easier for the computer, Google’s approach is to make things easier for the user”? In my experience a great deal. This is something most organizations would claim they would aim to do. The difference is in what they actually do, not what they aim to do.