﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>David commented on On Hadoop</title><description>I haven't played around with hadoop yet, but it looks like
  
Amazon has added hadoop as a option to their offers in the cloud.
  
See link: 
[aws.amazon.com/.../announcing-amazon-elastic-ma...](http://aws.amazon.com/about-aws/whats-new/2009/04/02/announcing-amazon-elastic-mapreduce/)</description><link>http://ayende.com/3875/on-hadoop#comment5</link><guid>http://ayende.com/3875/on-hadoop#comment5</guid><pubDate>Fri, 03 Apr 2009 13:03:01 GMT</pubDate></item><item><title>Ayende Rahien commented on On Hadoop</title><description>pb,
  
My point was, I want to see the reasons for why you would do that.
  
Not how you do it, but what you are doing.
</description><link>http://ayende.com/3875/on-hadoop#comment4</link><guid>http://ayende.com/3875/on-hadoop#comment4</guid><pubDate>Mon, 16 Feb 2009 01:40:59 GMT</pubDate></item><item><title>pb commented on On Hadoop</title><description>I think most order to cash scenarios don't involve a cluster of processing (though they may be load balanced to some degree) which is why you don't see too many examples like that. The kind of problems google has to solve are very different than most business problems. Unless the business scenario involves huge amounts of data that can't be represented in the normal ways I think you're unlikely to really need all that and the standard stuff will work fine.
</description><link>http://ayende.com/3875/on-hadoop#comment3</link><guid>http://ayende.com/3875/on-hadoop#comment3</guid><pubDate>Sun, 15 Feb 2009 18:40:14 GMT</pubDate></item><item><title>Chris Patterson commented on On Hadoop</title><description>Hadoop, to me at least, is more than just a MR implementation.
  
  
Hadoop includes a number of useful subsystems, including HDFS (the Hadoop File System). HDFS is a distributed, replicated storage that feeds the splitting/grouping parts of the MR process.
  
  
I've been looking at HDFS from a purely low-tech way of long term document storage. Since all of the documents are identified by a key, quick retrieval is easy and the data is replicated across cheap machines. Since I could then build access methods on top using MR to get at the data and filter/query the contents, the infrequent projections of data into some sort of document list/report would be easy to build.
  
  
I've been spending more time in Java the past few weeks, and it has been nice to just pull down an OS project and use it instead of constantly thinking "Okay, now this is how they did it in Java, maybe I should port it to .NET"
  
  
Mind you, I'm not a convert away from .NET, I just a thriving ecosystem of Java open source projects that are helping us get things done without a lot of pain.
  
  
</description><link>http://ayende.com/3875/on-hadoop#comment2</link><guid>http://ayende.com/3875/on-hadoop#comment2</guid><pubDate>Sun, 15 Feb 2009 14:46:50 GMT</pubDate></item><item><title>Sasha Goldshtein commented on On Hadoop</title><description>You might want to take a look at DryadLINQ (
[research.microsoft.com/en-us/projects/DryadLINQ/](http://research.microsoft.com/en-us/projects/DryadLINQ/)).  It is a framework that extends LINQ to the Dryad distributed execution environment.  Basically you write LINQ queries (including action queries) and they are automatically distributed to a cluster.
</description><link>http://ayende.com/3875/on-hadoop#comment1</link><guid>http://ayende.com/3875/on-hadoop#comment1</guid><pubDate>Sun, 15 Feb 2009 11:03:15 GMT</pubDate></item></channel></rss>