Mikera, Thank you for your reply, potentially it would include many machines. But the main motivation is to write less code, abstracting the actual implementation. I read that Storm is an implementation of Hadoop, I don't think I need to process that much data. But if I was I would like to be able to translate the same primitive operations to Storm or SQL (I'm leaving Datomic aside for a little bit..)
I have used SQL quite a bit and I think that a subset of Clojure may be almost directly translatable to SQL. By having a representation of all input data I could represent updates as functions that take the original data and produce a second database with a change of structure. On Monday, December 10, 2012 5:43:59 PM UTC-6, Mikera wrote: > > I think Clojure would be a great choice for this. When you say > "systemwide" though I assume you mean a lot of distributed processing > across many machines? > > In that case you should probably be looking at Storm, Aleph, Pallet, Ring > and the host of other Clojure libraries in that general area. What you want > to do can probably be achieved by orchestrating some combination of these > libraries in the right way. > > And on the data side Datomic of course might be a better choice than > SQL..... > > On Tuesday, 11 December 2012 06:02:44 UTC+8, ArturoH wrote: >> >> Everybody, >> >> I'd like to define a systemwide data structure with Clojure. I'd like it >> to represent input data, and derived data. Some specified derived data >> could be temporary for the calculation of other derived data. I also would >> like to use functions to specify the derivation of data. The idea would be >> to specify small derivations/transformations that would eventually produce >> the desired output. >> >> Once I have the system specified in such way, I'd like it to produce an >> SQL database. And generate code that would be 'practical' to run at the >> database level. And have the code that is best to run in Clojure to remain >> on Clojure. I understand that deciding where is best to execute the code >> may need to be a human activity. But I'd like the system to be flexible. >> >> I think that the current basic Clojure operations may not be best suited >> for this kind of specification. But I do think clojure may be the best >> language to do this kind specification. Any ideas/opinions? >> >> I would appreciate any feedback. >> >> Arturo Hernandez >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
