Re: Distributed Clojure

2009-01-30 Thread Tom Ayerst
I think you have to decide what you are aiming for. Is this a "solution" or another tool in the toolkit. I think Rich noted a while back that Clojure can access many distribution technologies. So if you want a solution right now you can wrap one of those up and off you go. If you want a "distri

Re: Distributed Clojure

2009-01-30 Thread hank williams
On Thu, Jan 29, 2009 at 7:28 PM, Greg Harman wrote: > > Hank: > > I have looked at TC in the past, and took another look today at your > suggestion. Terracotta certainly seems to have promise feature-wise, > but I have to admit it's a "heavier" solution than I had been thinking > of, and there ar

Re: Distributed Clojure

2009-01-29 Thread Konrad Hinsen
On 30.01.2009, at 00:59, Greg Harman wrote: > Agreed; the communication layer needs to come first. Regarding > serialization, specifically, I think we get that for "free" with s- > exps (there may be some under-the-hood evaluation time necessary for > remoted expressions, but [de]serialization is

Re: Distributed Clojure

2009-01-29 Thread Raoul Duke
> Another thing to look at (there's always another thing to look at) this worries me... it is sorta like the discussions i see about how some new db engine is FAST, oh but it totally fails on occasion and trashes the data, oopsy, oh well. how do we know any given lib is not going to just end up

Re: Distributed Clojure

2009-01-29 Thread Mark Derricutt
How about Hazelcast? [1] Its much lighter weight than TC. [1] http://www.hazelcast.com On Fri, Jan 30, 2009 at 1:28 PM, Greg Harman wrote: > > Hank: > > I have looked at TC in the past, and took another look today at your > suggestion. Terracotta certainly seems to have promise feature-wise, >

Re: Distributed Clojure

2009-01-29 Thread Kevin O'Neill
Another thing to look at (there's always another thing to look at) might be grid gain (http://www.gridgain.com/). It's map/reduce centric and might suite clojure very well. -k. On Fri, Jan 30, 2009 at 11:28 AM, Greg Harman wrote: > > Hank: > > I have looked at TC in the past, and took another l

Re: Distributed Clojure

2009-01-29 Thread Greg Harman
Hank: I have looked at TC in the past, and took another look today at your suggestion. Terracotta certainly seems to have promise feature-wise, but I have to admit it's a "heavier" solution than I had been thinking of, and there are probably all sorts of gotchas (and reviewing old threads on the

Re: Distributed Clojure

2009-01-29 Thread Kevin Downey
have you looked at the available java frameworks like hadoop? there is also some kind of java interface to erlang instead of reinventing the wheel again... On Thu, Jan 29, 2009 at 6:15 AM, Greg Harman wrote: > > One of Clojure's big selling points (obviously) is the support for > concurrent prog

Re: Distributed Clojure

2009-01-29 Thread Greg Harman
Agreed; the communication layer needs to come first. Regarding serialization, specifically, I think we get that for "free" with s- exps (there may be some under-the-hood evaluation time necessary for remoted expressions, but [de]serialization is rarely a lightweight process). On Jan 29, 10:03 am,

Re: Distributed Clojure

2009-01-29 Thread hank williams
As has been discussed on this list before, it seems to me the basis for this should be terracotta, which handles much (most?) of the heavy lifiting required for this kind of task. Have you looked at it? On Thu, Jan 29, 2009 at 9:15 AM, Greg Harman wrote: > > One of Clojure's big selling points (

Re: Distributed Clojure

2009-01-29 Thread Konrad Hinsen
On Jan 29, 2009, at 15:15, Greg Harman wrote: > So, I've been mulling over the idea of putting together a framework > for distributed applications. I think it should deal with issues such > as: ... I think the very first step should be to implement the basics of distributed computing: - comm