However, this is far from a silver bullet to ML problems. It can be quite dangerous, for example, to send off a bunch of data to google and immediately trust their analysis without knowing the underlying application of their algorithm. As a researcher in this area, what I would LOVE is if I could create my own algorithm, send it to Google, upload enormous amounts of data, and get back a result. Because right now it's difficult to scale complex algorithms to datasets in the GB-TB-PB range. Mahout is taking a valid stab at this problem though.
You can have accuracy and scalability. It's just that normally you run these types of things in memory on one machine, not on tens to hundreds of thousands of machines. So these algorithms have to be decoupled and that isn't easily done (but I'm sure Google figured it out a long time ago).
It's quite a bit higher-level than what Google is offering here, with all the benefits and drawbacks that entails.
You can find the full documentation on our developer site at http://developer.directededge.com/, and we offer a free developer account for non-commercial purposes: http://www.directededge.com/signup-developer.html
If anybody is giving the Google Prediction API a whirl for recommendations, we'd love to hear about your findings!
Maybe I'm slow, but I don't see how google's prediction API is a good replacement for collaborative filtering type recommendation engines.
Off-the-shelf recommendation systems are a bit trickier though, yeah.