RavenDB Conf VideosTailored database solutions with Voron
In this talk, I’m creating, live on stage, a database for handling time series data with the goal of handling 100 billion events per year.
And it actually worked!
More posts in "RavenDB Conf Videos" series:
- (13 May 2014) The tale of RavenHQ - An Ops Story
- (12 May 2014) Lap around the new HTML5 Raven Studio
- (09 May 2014) Scalability and High Availability with RavenDB
- (08 May 2014) RavenDB 3.0
- (07 May 2014) Extending RavenDB with Bundles, Plugins, and Listeners
- (06 May 2014) Mastering Date and Time Data in RavenDB
- (05 May 2014) Abstracting RavenDB
- (02 May 2014) Document Based Messaging with RavenDB 3.0
- (01 May 2014) RavenDB, CQRS and EventSourcing
- (30 Apr 2014) Modeling Tricks my Relational Database Never Taught Me
- (29 Apr 2014) Tailored database solutions with Voron
- (28 Apr 2014) Panel Discussion - The good & ugly of working with RavenDB
- (25 Apr 2014) Diving into Voron
- (24 Apr 2014) Introduction to document database modeling with RavenDB
Comments
This is a really interesting presentation. You stated in the presentation that Voron itself will not be a product. I understand that you are going to use it as the underlying datastore for RavenDB, but will the Voron trees be completely abstracted away, or will you be augmenting the RavenDB API's so that there will be the possibility of using trees more directly (as you do in this presentation for time-series data)?
Dan, Voron really is too low level for most business apps needs. And there is a LOT more to building data stores than just knowing the API. There are a lot of additional concerns. We intend to use Voron as the building block for customized data solutions.
That doesn't mean we won't be licensing this out if people really want this, but it would likely be a very different model than RavenDB.
Comment preview