RavenDB 4.0 Release Candidate Updates

time to read 3 min | 509 words

We are on the verge of releasing RavenDB 4.0 release candidate, currently the release is set to mid next week but we’re close enough that I can smell it. Once the release pressure is off, I can start discussing more of the things that we bring to the table.

For the record, we are now standing on less then 30 remaining issues before we can ship RC, most of them relating to licensing. And speaking of this, we made a couple of decisions lately that you should probably know about.

First, we are switching to the RavenDB 4.0 pricing starting next week, for the period of the RC, we’ll even go with 30% discount. In other words, you can do a bit of arbitrage and get a license now at the old pricing, we’ll grandfather in all existing orders when we make the switch.

Second, regarding the free community edition. After a lot of deliberations, I decided that community edition as we wanted to offer it made no sense. RavenDB 4.0 is a distributed, robust database, and we want to encourage people to use us in real world settings. Because of that, we decided to scrap the limits on running the community edition as a cluster.  This means that you’ll be able to deploy a full blown RavenDB cluster for production using just the community edition.

Third, we decided to change the pricing model a bit. Instead of you purchasing a license per server, which caused a lot of back & forth between our sales people and customers, we decided to move to a flat per core model. In other words, if you need to deploy 3 node cluster with 4 cores each, you’ll purchase a cluster license for 12 cores. You could then deploy that cluster on up to 12 machines (with 1 core assigned for each machine in this case). This simplify things significantly and it gives a lot more flexibility to the operations team.

Here is a rough draft of what this would look like. You can see a 16 cores cluster license and that we assigned 3 cores to Node A.


The community edition we’ll provide will have 3 cores and a maximum of 3 nodes in the cluster. This will allow you to have a single RavenDB node, or a cluster of three nodes with one core each, given you high availability, automatic failover, etc. There are still things that aren’t in the free edition (ETL, cloud backups, monitoring, support, etc) but the idea is that you could run real things on the free edition and that you could upgrade when your needs actually require it.

I’m really excited about this because it means that features that are currently Enterprise only are now pushed all the way to the community edition. This gives you the chance to use a world class distributed database that was built with an explicit design goal of being correct, fast and easy to use.