Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

RavenDB 4.0 Release Candidate Updates

DZone's Guide to

RavenDB 4.0 Release Candidate Updates

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.

· Database Zone ·
Free Resource

RavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.  

We are on the verge of releasing the 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 than 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 a 30% discount. In other words, you can do a bit of arbitrage and get a license now at the old pricing, abd 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-and-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 three node clusters with four cores each, you’ll purchase a cluster license for 12 cores. You could then deploy that cluster on up to 12 machines (with one core assigned for each machine, in this case). This simplifies things significantly and provides 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 three cores to Node A.

image

The community edition we’ll provide will have three cores and a maximum of three nodes in the cluster. This will allow you to have a single RavenDB node or a cluster of three nodes with one core each, giving 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 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.

Do you pay to use your database? What if your database paid you? Learn more with RavenDB.

Topics:
cluster ,node ,settings ,ravendb ,database ,release

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}