Run your web applications on Google’s infrastructure.
Google App Engine enables you to build web applications on the same scalable systems that power Google applications.
No assembly required. Google App Engine provides a fully-integrated application environment. |
It’s easy to scale. Google App Engine makes it easy to build scalable applications that grow from one user to millions of users without infrastructure headaches. |
It’s free to get started. Every Google App Engine application can use up to 500MB of persistent storage and enough bandwidth and CPU for 5 million monthly page views. |
The Facebook JavaScript client library allows you to make Facebook API calls through JavaScript code from any Web site and makes it easy to create AJAX Facebook applications. Since the library does not require any server side code on your server, you can now create a Facebook application that can be hosted on any Web site that serves static HTML.
Applications that use this client library should be configured to load in an iframe, not be rendered with FBML. This applies to either iframe Facebook applications that users access through the Facebook Web site or applications that users access directly on the application’s own Web site. The library supports every Facebook API method, except:
Using this client library is easy. Just follow these two steps:
That’s all. Now you start to call the Facebook API through JavaScript…
We’ve set out some basic organizing principles to help frame the approach that we’re going to explore. We will:
Google Operating System Weblog, “Google Is All About Large Amounts of Data“: In a very interesting interview from October, Google’s VP Marissa Mayer confessed that having access to large amounts of data is in many instances more important than creating great algorithms.
Right now Google is really good with keywords, and that’s a limitation we think the search engine should be able to overcome with time. People should be able to ask questions, and we should understand their meaning, or they should be able to talk about things at a conceptual level. We see a lot of concept-based questions — not about what words will appear on the page but more like “what is this about?” A lot of people will turn to things like the semantic Web as a possible answer to that. But what we’re seeing actually is that with a lot of data, you ultimately see things that seem intelligent even though they’re done through brute force.
When you type in “GM” into Google, we know it’s “General Motors.” If you type in “GM foods” we answer with “genetically modified foods.” Because we’re processing so much data, we have a lot of context around things like acronyms. Suddenly, the search engine seems smart like it achieved that semantic understanding, but it hasn’t really. It has to do with brute force. That said, I think the best algorithm for search is a mix of both brute-force computation and sheer comprehensiveness and also the qualitative human component.
Marissa Mayer admitted that the main reason why Google launched the free 411 service is to get a lot of data necessary for training speech recognition algorithms. (more…)