It's interesting that the comments so far have latched on to JavaSpaces (and its alleged limitations), since ComputeFarm's API is actually independent of JavaSpaces. One of ComputeFarm's goals is to create a very simple API that facilitates running Java programs in parallel, without caring about the underlying implementation.
Now, of course the underlying implementation cannot be totally ignored - it has to be reliable and performant at least. There are other implementation choices here: ActiveSpaces, Green Tea, Coherence etc., however the only implementation at the moment is the JavaSpaces one. I think that the replicated worker pattern hits JavaSpaces sweet spot - people are always moaning that there are no applications for JavaSpaces - but I believe this is a good one! JavaSpaces is a healthy technology, with at least three implementations in active development. So I'm a bit wary of general statements that "JavaSpaces does not scale" - more detail please. Equally, I'm sure there are projects that have shown JavaSpaces scaling successes - anyone from the jini.org community care to comment?
Thanks,
Tom |
java.net RSS Feeds
