We are gearing up to start work on the next release of RavenDB, following the 4.0 release. I thought this would be a great time to talk about what are the kind of things that we want to do there. This is going to be a minor point release, so we aren’t going to shake things up.
The current plan is to release 4.1 about 6 months after the 4.0 release, in the July 2018 timeframe.
Instead, we are planning to focus on the following areas:
- Moving to .NET Core 2.1 for the performance advantages this gives us.
- Start to take advantage of the new features such as Span<T>, etc in .NET Core 2.1.
- Wild card certificates via Let’s Encrypt, which can simplify cluster management when RavenDB generates the certificates.
- Restoring highlighting support
We are also going to introduce the notion of experimental features. That is, features that are ready from our perspective but still need some time out in the sun getting experience in production. For 4.1, we have the following features slated for experimental inclusion:
- Distributed counters
- SQL Migration wizard
I have a dedicated post to talk about each of these topics, because I cannot do them justice in just a few words.