Thanks for your last reply about the development roadmap.
I wanted to ask from your perspective what are the missing items in
fleetdb that would hinder its usage in a production scenario ? Also if
this was to be a full time project then what features do you think
should be added?
Just asking the above because I would like to use it for production
but may be unaware of its weaknesses.
One cool idea could be combining fleetdb and couchdb. Let me explain.
With the advent of clojurescript, CouchDB views can now be written in
clojure. What this means is that clojure data can be persisted as
documents instead of JSON, and can then be manipulated by clojurescipt
map/reduce. The credit for the above idea goes to the clojurescriptone
project where they are using a simalr mechanism to send clojure data
structures back and forth between the server and client (remoting).