I share your concern but Im sticking with it now, major issues for me
were smuggler being broken (lesson: always test your backups), flawed
transactions support - in terms of the semantics we'd expect, and many
issues near the start (datetime issues, index issues, boolean
issues, .net 3.5 client being fcked etc.. etc..). But I am a week or
two away from deployment and relatively happy with the stability now,
things are working smoothly finally.
Biggest lesson learnt in this - is not to jump on the bandwagon (as
often that's all it is), I reckon at the time I started using Raven
there were less than two dozen real users, however of course if you
looked at the
alt.net kids (and most of them are just sheep now) and
the twitter you'd easily conclude this had massive community adoption
- not the case, i think the
alt.net kids just want to twit #ravendb.
In hindsight, if I could roll back time I'd have started with
something more proven and reliable, rather then dogfeeding Raven, I'd
have gone with CouchDB. If Im upmost honest I was probably neglient in
my contractual obligations in selecting RavenDB (the perceived coolest
and .net adoption factor blinded me), and as a result I've absorbed
many days working around ravendb issues to get things back ontime.
Where things are now, I say we got around 50 users properly
dogfeeding this (ayende, might say more but unless they've been
reporting bugs or gripes here I doubt they doing anything but ScottGu
style examples), I'd like to see more delays between releases (or
certain releases being hailed as stable), the regressions we've
endured in the past releases are just not tolerable going forward (I
think ayende realises this)..