Don Stewart <[EMAIL PROTECTED]> wrote: > jason.dusek: > > What does Haskell have to say about cloud computing? > > I'm not sure cloud computing is well-enough defined to say > anything yet.
That is fair -- having something to say about cloud computing is essentially having a grand vision. I only ask because it was touched on in the original message. > ...we're talking about JSON, online db services like Amazon > bindings, HAppS nodes, et al. For which Haskell's perfectly > able. Do HAppS nodes really function as nodes in a larger system? Does HAppS function as a "cluster application server"? > Now, maybe there's some nice abstractions waiting to be > found though... Conventionally, it is argued that the abstraction of choice is message passing; but that isn't going to take you anywhere near having a web page that people can see twice without some more abstraction. I would like to say that distributed version control is that abstraction -- that branches with a main trunk are a model for resources that is compatible with dirty-write as well as consistent read. However, as systems become more desirable from a maintenance point of view -- self-healing, easily expandable, fault tolerant -- it becomes ever more difficult to get the transactionality you need to have a main trunk. -- _jsn _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
