The Engine: Google Enters the Cloud

On Thursday, the company that runs the largest computer systems in the world has opened the doors of its machine room, and the doors are the story. Google launched App Engine on Monday, a platform that lets any developer build a web application and run it on Google's own infrastructure, with the scaling, the storage, and the maintenance handled by the company. The launch is the April 2008 story, and the story is the lesson: the companies that own the biggest machines are the companies that will rent them out, and the renting is the future.

The Engine is the subject of this article: what Google App Engine is, how it works, why it matters, and what it says about the shift from the computer on the desk to the computer in the network. The launch came at an event the company called Campfire One, on Monday, April 7. This is the story of the engine, and the story is about the moment the web's biggest landlord started renting out the building.

1. The Announcement

The announcement came at Campfire One, the casual gathering where Google talks to its developer community, and the announcement was the surprise of the evening. The product manager Paul McDonald introduced Google App Engine, a preview release of a platform for developing and hosting web applications on Google's infrastructure. The message was simple: the developer writes the code, and Google runs the servers. The announcement was the beginning, and the beginning was the offer.

The announcement was also the demonstration, and the demonstration was the promise. The developers in the room saw applications being built and launched in minutes, with no servers to buy, no software to install, and no operations team to hire. The platform handled the traffic, the storage, and the growth automatically. The announcement was the pitch, and the pitch was the new way of building.

2. The Platform

The platform was the substance of the announcement, and the substance was the design. The developer wrote the application in Python, the language of the web's rapid builders, and uploaded it to Google. The application ran on Google's servers, scaled automatically with the traffic, and stored its data in a datastore built on Google's own Bigtable technology. The developer paid nothing to start, with free quotas, and paid only when the usage grew. The platform was the product, and the product was the simplicity.

The platform was also the architecture, and the architecture was the ambition. The applications were sandboxed, isolated from each other and from the underlying machines, and the isolation was the safety. Google would handle the backups, the failovers, the patches, and the capacity, and the handling was the value. The platform was the machine room made invisible, and the invisible was the product.

3. The Machine

The machine was the secret, and the secret was the scale. Google ran the largest computing infrastructure in the world: the data centers, the servers, the networks, the storage, the custom hardware that powered the search engine and the mail and the maps. The infrastructure was the moat that no competitor could cross, and the moat was about to become a product. The machine was the asset, and the asset was the offer.

The machine was also the proof, and the proof was the trust. The developer who ran an application on Google was running it on the same infrastructure that handled billions of searches a day, and the same infrastructure was the guarantee of the reliability. The machine was the answer to the startup's nightmare of the server that crashes at the worst moment, and the answer was the promise.

4. The Cloud

The cloud was the context, and the context was the wave. The idea of computing as a service, rented by the hour instead of bought as a box, had been building for years: the bookseller's computing service had opened in 2006, and the startups had begun building their businesses on rented machines. The cloud was the shift, and the shift was the platform: the web as the operating system, the data center as the computer, the application as the service.

The cloud was also the race, and the race was the competition. The bookseller had the infrastructure, and the search giant had the infrastructure, and the software giant was still deciding what to do about it all. The developer who chose the platform was the developer who chose the future, and the choosing was the battle. The cloud was the field, and the field was the prize.

5. The Developers

The developers were the audience, and the audience was the point. Google was not selling to the enterprises first; it was selling to the startups, the students, the builders of the next big thing, the people who would rather write code than manage servers. The platform was the gift to the builders: the free quotas, the simple tools, the instant launch, and the gift was the hook. The developers were the customers, and the customers were the future.

The developers were also the bet, and the bet was the ecosystem. The applications that the developers built would run on Google, would use Google's storage, would grow on Google's network, and the growth was the business. The company that won the developers would win the applications, and the applications were the value of the web. The developers were the audience, and the audience was the strategy.

6. The Business

The business was the quiet part of the story, and the quiet was the design. Google made its money from the advertising, and the advertising depended on the web, and the web depended on the applications, and the applications needed the platforms. The platform was not the end of the business; it was the means, the way to make the web faster, richer, and more valuable, and the value was the ad revenue.

The business was also the long game, and the long game was the pattern. Google had given away the search, the mail, the maps, and the storage, and the giving had built the greatest advertising business in history. The platform was the same pattern: give the developers the machines, and the machines would build the web, and the web would build the revenue. The business was the strategy, and the strategy was the giving.

7. The Lesson

The lesson of the launch was about the ownership of the infrastructure, and the ownership was the power. The companies that ran the biggest machines were the companies that could rent them out, and the renting was the new model of the industry. The lesson was that the computer was no longer the box on the desk; it was the network, the data center, the service, and the companies that owned the network owned the future.

The lesson was also about the opening of the doors. Google could have kept its infrastructure to itself, and the keeping would have been the old way, and the old way was the dying way. The company that opened its machine room was the company that understood the shift, and the understanding was the strategy. The lesson was the opening, and the opening was the future. The lesson was the engine, and the engine was the economy.

8. The Future

The future of the platform was the future of the cloud, and the future was the test. The developers would build, the applications would grow, and the platform would prove itself or not, and the proving would take years. The bookseller would keep building its own cloud, and the software giant would eventually answer, and the competition would define the decade. The future was the race, and the race was the beginning.

The future was also the lesson in the making. The announcement was a preview, and the preview was the promise, and the promise was the direction of the industry. The web was becoming the platform, and the platform was becoming the economy, and the economy was being built in front of the developers' eyes. The Engine is the April 2008 story, and the story is the lesson: the companies that own the biggest machines are the companies that will rent them out, and the renting is the future. The doors opened on Monday, and the machine room is the future. The lesson for every technology leader is to look at the biggest asset and ask the question: what if we rented it out? The companies that turn their infrastructure into a service, that open their machine rooms to the builders, that make their scale available to everyone, are the companies that multiply their value. Google opened the doors on Monday, and the opening was the strategy, and the strategy was the future. The developers who build on the platform are the partners, and the partners are the ecosystem, and the ecosystem is the moat that the competitors cannot cross. The machine room is open, and the open machine room is the new economy of the web. The first applications are already being built, and the first builders are the ones who will write the story of the platform. The free quotas, the simple upload, the instant launch, the absence of the server room, all of it is the offer that the builders cannot refuse. The companies that make the hard things easy are the companies that win the builders, and the builders are the ones who build the future of the web.

Tags

#technology #engineering