manAmplified

Version 0.7.0 of Cascading and 0.3.0 of Cascading.groovy is now available for download. For details check out the announcements.

Some people may have noticed already, but I've founded a new company with the goal of taking Cascading to the next logical level in the clustered computing space. Concurrent, Inc. currently only offers alternative licensing and support for Cascading, but watch that space for further announcements as things unfold.

I've been invited to speak at the next Hadoop User Group meeting on July 22 at the Yahoo! campus. The meetings are open to all interested parties, and there is always free beer and pizza. Plus you get to meet developers of other Hadoop related projects like ZooKeeper and Pig. Hope to see you there.

A recent thread on the Hadoop mailing list prompted me to throw out some quick comments on Cascading and how it compares to Apache PIG. I'm reposting those comments here with minor edits for clarity.

I'll be attending Structure 08 and CloudCamp this year. Feel free to ping me if your attending either.

Version 0.2.0 of Cascading.groovy is now available for download. For details check out the announcement. Cascading.grooy is our Groovy language interpreter extension to Cascading.

Version 0.6.0 of Cascading is now available for download. For details check out the announcement.

A couple interesting quotes from the Hadoop user list. Not indicative of anything in particular, but noteworthy.

Hadoop 0.17.0 is now generally available. This also means there are new scripts for managing EC2 clusters using the new EC2 features like 'availability zones', the new optimized kernels, 32 and 64 bit images, and Ganglia. Also looks like Tom has already packaged new public AMI's as well. You can read about the changes here on the Hadoop Wiki EC2 page. Here also is the JIRA issue with the patches.

Thought I would quickly post this link to the Hadoop wiki comparing GridGain to Hadoop. In summary, Hadoop was designed for large data applications. GridGain is simply a re-imagining of tuple-spaces with constraints on available JVM memory (as implied by the comparison). Hopefully I'll post my own opinions at a later date. [Update] A reaction to the comparison has been posted.