Skip to Navigation
Released
RavenDB 5.4 released with exciting new features:
- ETL to Kafka
- ETL to RabbitMQ
- Grafana integration for data
- Corax (experimental search engine)
RavenDB 5.3 released with Intelligent RQL Coding Assistance
- Incremental Time Series
- Concurrent Data Subscriptions
- Power BI support
- TCP Compression
- ETL for Elasticsearch
- Terraform
- JSONPatch
RavenDB 5.2 released for OLAP Business Intelligence.
RavenDB 5.1 released with exciting new features:
- Filtered Replication
- ETL for Time-Series
- Counters and TimeSeries support in JavaScript Indexes
- Indexing Extensions from NuGet
- Attachment content indexing support
- Documents Compression
RavenDB 5.0 released with data compression, cutting cloud storage costs by 50% and overall cloud database cost by 10%. New time-series model enables ease of use for Internet of Things (IoT) applications.
RavenDB Cloud is launched on Google Cloud Platform.
The ribbon is cut on our permanent company headquarters in Hadera, Israel.
RavenDB Cloud is released, offering a Database as a Service in all regions of AWS and Azure.
RavenDB 4.2 is released offering a final slew of features:
RavenDB hires its 30th developer.
3 million developers download RavenDB.
Gartner Research highlights RavenDB 4 in their “Other Vendors to Consider” report.
RavenDB 4.1 is released, building on the success of RavenDB 4.0, this version includes:
- New SQL and NoSQL Migration tools
- Support for data ‘includes’
- Distributed Counters
- Cluster-Wide ACID
- JavaScript indexes
RavenDB 4.0 is released, the most comprehensive update in the history of RavenDB. This version offers a robust set of features making it easy as pie for a developer to integrate a document database into his application.
- Running on Windows, Linux, Raspberry Pi
- Performance for both reads and writes improved 10X
- Intelligent clustering with dynamic node distribution
- Automatic master-master setup between nodes
- Easy to configure Setup Wizard and Management Studio GUI
- Modernized security protocols to fortify your database
- A new and improved SQL-like Raven Query Language (RQL)
- Esent was replaced with Voron, our in-house storage engine
2 million developers download RavenDB.
RavenDB hires Iftah Ben Zaken, it’s 20th developer.
RavenDB 3.5 is released, taking database clustering to a whole new level. A multiple nodes database lets you replicate your database to several places, creating a fault tolerant application. If one node were to fall, the other nodes would stay in operation, keeping your database up at all times and maintaining high-availability. RavenDB also released support for Extract, Transform, and Load (ETL) features, enabling you to work seamlessly with other databases.
Construction teams break ground on RavenDBs new permanent headquarters.
RavenDBs new European Offices open up in Torun, Poland.
RavenDB is selected to be the point of sale database for a Fortune 100 client using 1.5 million instances throughout its 36,000 locations worldwide.
RavenDB hires Idan Shalom, it’s 10th developer.
1 million developers download RavenDB.
RavenDB 3.0 is released.
RavenDB appears in Forrester, its first major Industry Report.
RavenDB 2.5 is released.
RavenDB 2.0 is released.
Oren Eini hires his first full time developer, Fitzchak Yitzchaki.
RavenDB sets up offices in Hadera, Israel.
RavenDB 1.0 secures its first client, a Norwegian Institution for wildlife preservation.
RavenDB 1.0 becomes the pioneer Document Database to offer fully transactional ACID guarantees over multiple documents and throughout your entire database. It is the first Document Database on the .NET platform. As a document database, RavenDB enables developers to store objects, arrays, nested objects with efficiency and speed. As a pioneer Schema free database, developers were able to tap into a higher level of productivity, empowering greater flexibility for their applications.
Coding for RavenDB begins with the aim of creating a full project.
After years of consulting on multiple database projects, Oren Eini sees the same mistakes happening over and again plaguing all applications using a relational database and resulting in unstructured data. Looking for better ways to process information to power a robust 21st century application, Oren begins his work on designing a next gen document database.
