- it should support transactions I love the word *should* :)
Question: Do you really need transactions? or is that you just need conflict resolution? I ask because many No-SQL datastores support the later which often is good enough (or even better in my opinion). For example look at the description for RIAKs model: "Riak’s approach ensures that the datastore is always write-available, and that writes always succeed, even in the face of a network split or hardware failure, so long as the client can reach at least one node in the cluster. The tradeoff is that the client performing the read must do a little extra work to resolve the conflict, or can optionally choose to take the latest version of the object (this is the default setting.)" Where... "take the latest version of the object (this is the default setting.)" is all I really ever need. MongoDB is similar, in that it supports conflict resolution, only I believe you only have the option for the last write wins. MongoDB is better suited to an embedded db model, that doesn't have to support large datasets... so if you're OK with the last write wins model - go for mongo. https://github.com/aboekhoff/congomongo Also there's a few other no-sql database connectors I list out in my blog (with links to the libraries): http://blackstag.com/blog.posting?id=23#subsection8 On Jul 15, 1:17 am, Marko Kocić <marko.ko...@gmail.com> wrote: > Hi all, > I would like to try out some of those "no-sql" datastores for my next > project, and need an advice which one, since I never used the one before. > It needs to fulfill at least some of those following criteria, in order of > importance: > > - is nicelly supported by Clojure (by this I mean idiomatic clojure > "driver", not java plain java wrapper") > - it should be schemaless > - it should support transactions > - it's good if it can be used as embedded db > - it doesn't have to support large datasets (in-memmory is ok) > - it has to run on both Windows and Linux > > My first choice would be FleetDB, since it was written in Clojure and > examples look nice, but I'm not sure if it is abandonware or not, and I > havent heard that people are actually using it in production. > > What are my other options? > > Regards, > Marko -- 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