so I've long wanted a nice clean REST API for working with databases; that hides as much as possible the physical storage details of the gazillion different kinds of DB/storage we have these days (SQL v NoSQL v ElasticSearch / Hadoop et al) never mind caching and replicating state to different storage engines etc. I'm surprised we still don't have a good standard thats widely adopted. So good luck on Staash, I wish it well!
App developers usually wanna just read/write blobs of (say) JSON and not worry too much about exactly how a particular database implementation denormalises (or not) or whether its column / key-value / SQL based etc.(e.g. like the ElasticSearch / Mongo APIs)
I wondered; particular since Netflix did host an OData source for its catalog a while back; if you had any particular reasons for making a new REST API or not just reusing OData? I wondered if a little FAQ on the wiki might be handy about why Staash is doing things differently? e.g. whats different or bad with OData; lessons learnt working with OData etc?
From a web app developers perspective breezejs looks pretty neat; I wondered if we could layer it on top of Staash some day? (Though it might be a bit too OData centric for Staash) - at least for the query & insert/update/delete parts it'd be handy.
Though I guess app developers often want a REST orchestration API for working with databases; which is probably a layer of abstraction over databases/tables/rows etc. (e.g. defining more like DTOs than entity beans to use JEE kinda jargon).
Anyway, keep up the good work!