What's Next for RavenDB
Join the DZone community and get the full member experience.Join For Free
after 2.0, what comes next? ravendb 2.0 is a massive release, close to 5 thousand commits, 6+ months of work, a team of close to 70 people working on it.
it also thought me a very good lesson about cutoffs. i don’t like them. in particular, someone who wanted to run on the stable version was stuck with 6 months with no features, and only hot fixes as needed.
instead, i would like to go to a more streamlined model of a stable release every 6 – 8 weeks. that gives us a proper time frame for doing changes, but doesn’t leave people “in the cold” in regards to stale versions.
so that is what we are planning in terms of process . but what about the actual features ? surprisingly enough, we have enough more lined up for you.
- robust sql replication (already implemented, and waiting for additional testing & goodies). to better support reporting.
- indexing snapshots and unlimited result set server side processing.
- multiple index batches and independent indexing. prevent a slow index from slowing down all indexing.
- restructuring of temporary / auto indexes.
- auto index merging. (even smarter behavior with regards to optimizing indexes, removing unused indexes, etc)
- write index output to documents. allow to do things like multi stage reduces.
- winrt & mono touch & mono for android client support.
- more comprehensive client side caching.
and those are just the things we have as high level items .
Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Effortlessly Streamlining Test-Driven Development and CI Testing for Kafka Developers
Auditing Tools for Kubernetes
The SPACE Framework for Developer Productivity
Microservices Decoded: Unraveling the Benefits, Challenges, and Best Practices for APIs