RavenDB vNext? Just the same, a little bit better, all over the place
We pretty much completed all of the major work that was going to get into the next major RavenDB release. There is the indexing stuff that I already talked about in this blog, but most of the rest are a lot of seemingly minor things. Nothing that would blow you head in isolation.
Things like better aggressive caching invalidation, faster error in network timeout scenarios, better bucket selection algorithm for map/reduce, providing you with auto resolving conflicts, or even more improvements to the studio.
Hell, it is even things like this:
We output a lot of information that can help you figure out what is going on in your system. But now we are actually starting to take it up a notch and also provide good UX for handling that.
Comments
Pretty! It's great to have that kind of feedback on internal stuff.
So far, is moving 2.1 to 2.5 supposed to be seamless? Love all the 2.5 features but want to wait a bit until we use it as our main version.
Hi Oren,
I love your posts, but as I'm not a RavenDB user I would realy love to get the design/testing/architecture posts (not RavenDB relative) on a different rss feed :)
Thanks.
All the topics have their own RSS feed - you could very easily create a Yahoo pipe that says "the whole feed unless it contains the Raven tag" :-)
If Yahoo pipes still exists that is.
Vlad, 2.5 is 2.1 renamed, and moving from 2.0 to 2.5 is pretty seamless, yes. Note, however, that 2.5 is considered unstable.
I think it's very useful to have performance stats, but it would be even nicer if Raven exposed current performance numbers so they could be queried and stored by external monitoring tools (Cacti, for example) I thought about using NLog for sending out performance information over UDP, this way you could use NLog's configuration to decide which stats should be provided to your reporting tool.
Rafal, If you want the perf monitor values, you can get them using the standard methods. Windows provide many such options. And any monitoring tool can handle that.
Comment preview